cleaned slide layout

source/content/elements/index_stage.md

@@ -5,7 +5,7 @@
 :::{card} <i class="far fa-rectangle-list"></i>  Index/Staging Area
 {% endif %}
 
-> In <i class="fab fa-git"></i> the _Staging Area_ or _Index_ refers to a set of modified files that are flagged to be include in a commit
+> In <i class="fab fa-git"></i> the _Staging Area_ or _Index_ refers to a **set of modified files that are flagged to be included in a commit**.
 
 The Staging Area:
 

source/content/elements/working_dir.md

@@ -5,7 +5,7 @@
 :::{card} <i class="fas fa-folder-open"></i> Working Directory
 {% endif %}
 
-> In <i class="fab fa-git"></i> the Working Directory refers to the **local folder you are viewing and editing** the content of the currently checked out branch
+> In <i class="fab fa-git"></i>, the Working Directory refers to the **local folder you are viewing and editing** the content of the currently checked out branch.
 
 The Working Directory:
 

source/content/history/example.md

@@ -2,12 +2,14 @@
 ### A Simple Example
 {% endif %}
 
+{% if page %}
 ```{admonition} <i class="fab fa-git"></i> <strong style="color:black">log</strong>: explore the history
 :class: note, margin
 
-- <i class="fas fa-code-commit"></i> commits are indicated with `* <hash...>` followed by the commit message
+- <i class="fas fa-code-commit"></i> commits are indicated with `* <hash>` followed by the commit message
 - <i class="fas fa-code-branch"></i> Branches, <i class="fas fa-tag"></i> Tags and <i class="fas fa-hat-wizard"></i> HEAD are indicated in `(...)` after the commit hash
 ```
+{% endif %}
 
 :::{card} `git log --all --decorate --oneline --graph`
 :class: smaller

source/content/intro/limitations/consistency.md

@@ -1,14 +1,13 @@
 ### Functional Consistency
-
 ```{admonition} <i class="fab fa-git"></i> tracks only the content of files
 :class: warning
-It does not track the functionality of whatever the content implements.
+Git tracks only the content of files, not the functionality of the code within them.
 ```
 
 There is **no** guarantee that:
 
 - Git will identify breaking changes as a conflict{% if page %}[^sn3]{% endif %}
-- Two functioning versions do not lead to a dysfunctional combination
+- Two functioning versions combined will not result in a dysfunctional version
 
 {% if page %}
 [^sn3]: This is rather obvious, if you think about it. But is something that might not be thought about if <i class="fab fa-git"></i> is not reporting any conflicts when merging changes from different sources.

source/content/intro/limitations/sync.md

@@ -3,10 +3,12 @@
 ```{admonition} No coupling between changes and distribution
 :class: warning
 Synchronization is not coupled to change events in a repository. 
+{% if page %}
 This means that just because a change (like a commit) happens in the repository, it doesn't automatically trigger synchronization across all copies (clones) of the repository.
+{% endif %}
 ```
 
 Therefore:
-- collaboration mediated by <i class="fab fa-git"></i> happens asynchronously, i.e., changes are propagated when explicitly requested (e.g., by pushing or pulling).
-- simultaneous editing is not supported. If two users edit the same file at the same time, the changes must be merged manually.
-- synchronizing the state of a repository is part of the <i class="fab fa-git"></i> workflow
+- collaboration mediated by <i class="fab fa-git"></i> happens asynchronously{% if page %}, i.e., changes are propagated when explicitly requested (e.g., by pushing or pulling).{% endif %}
+- simultaneous editing is not supported.{% if page %} If two users edit the same file at the same time, the changes must be merged manually.{% endif %}
+- synchronizing the state of a repository is part of the <i class="fab fa-git"></i> workflow.

source/content/intro/limitations/tracking.md

@@ -11,6 +11,9 @@ This leads to limited support for:
 - Filetypes that include metadata (e.g. `.docx`)
 - Large files (<i class="fab fa-git"></i>'s size limit for a single file is 2 GB){% if page %}[^sn4]{% endif %}
 
+{% if slides %}
+How to deal with these limitations will be discussed later.
+{% endif %}
 
 {% if page %}
 [^sn4]: Git LFS (Large File Storage) is a solution to this problem. It allows to store binary files outside of the repository and only track their location and version.

source/content/principles/healthy_reference.md

@@ -1,6 +1,6 @@
 ## Healthy Reference
 
-> A pre-requirement to successfully develop any change, or new feature, is **to be able to depart from a functional state**.
+> A pre-requirement to successfully develop any change, or new feature, is **to be able to start-off from a functional state**.
 
 In the <i class="fab fa-git"></i>-context this translates to:
 

source/content/principles/healthy_reference_best.md

@@ -1,6 +1,6 @@
 ### Best Practice (1/4)
 
-{% if build == "slides" %}
+{% if build == "slide" %}
 ```{admonition} Best Practices
 :class: tip, margin
 

source/content/principles/separate_best.md

@@ -1,6 +1,6 @@
 ### Best Practice (2/4)
 
-{% if build == "slides" %}
+{% if build == "slide" %}
 ```{admonition} Best Practices
 :class: tip, margin
 

source/content/principles/states_best.md

@@ -1,6 +1,6 @@
 ### Best Practice (4/4)
 
-{% if build == "slides" %}
+{% if build == "slide" %}
 ```{admonition} Best Practices
 :class: tip, margin
 

source/content/principles/steps_best.md

@@ -1,6 +1,6 @@
 ### Best Practice (3/4)
 
-{% if build == "slides" %}
+{% if build == "slide" %}
 ```{admonition} Best Practices
 :class: tip, margin