content: minor updates to interals

Author: debel

src/content/lessons/bash-scripting.md

@@ -354,6 +354,35 @@ done
 
 ---
 
+## Associative arrays
+
+These act as dictionaries or hashmaps in other languages allowing you to store key - value pairs.
+
+```bash
+# define an associative array
+declare -A PETS
+
+PETS["Norwegian"]="cat"
+PETS["Dane"]="horse"
+PETS["Brit"]="bird"
+PETS["German"]="?"
+```
+
+---
+
+```bash
+# Read the value for a given key
+echo ${PETS['Brit']}
+
+# Adding new values
+PETS["Swede"]="dog"
+
+# Alternative syntax for adding elements
+PETS+=(["Bulgarian"]="goat")
+```
+
+---
+
 ## Handling inputs
 
 There are special variable that allow you to handle script arguments.

src/content/lessons/git-internals.md

@@ -48,6 +48,19 @@ The `.git` directory is where git stores all its internal state:
 
 ---
 
+## What commit is my branch pointing to?
+
+```bash
+git rev-parse branch-name
+# prints the sha of the commit that
+# the given branch is pointing to
+
+git rev-parse --short branch-name
+# prints a short commit sha
+```
+
+---
+
 <class-work>
 
 ### Create a branch by hand
@@ -129,6 +142,10 @@ git cat-file -p HEAD^{commit}
 
 ---
 
+![sharing objects between commits](https://git-scm.com/book/en/v2/images/data-model-3.png)
+
+<bonus-content>
+
 ### Optimized for efficiency
 
 Git splits the SHA of objects to allow large repositories
@@ -137,6 +154,8 @@ to work on file systems with small limits
 
 > This also increases efficiency under any file system
 
+</bonus-content>
+
 ---
 
 <class-work>
@@ -220,19 +239,6 @@ echo 'commit message' | git commit-tree \
 
 ---
 
-## What commit is my branch pointing to?
-
-```bash
-git rev-parse branch-name
-# prints the sha of the commit that
-# the given branch is pointing to
-
-git rev-parse --short branch-name
-# prints a short commit sha
-```
-
----
-
 <bonus-content>
 
 ## Other meta refs

src/content/lessons/git-workflows.md

@@ -61,6 +61,7 @@ the same parts of the project
 New features are developed on their own branch.
 
 - **PRO**: keeps development isolated, conflicts only happen after a big merge
+
 - **CON**: stacking feature branches can lead to complex merge trains
 
 > **GOOD PRACTICE**: update feature branches often by merging main into them
@@ -118,9 +119,9 @@ You can merge into main locally and push the resulting commits manually.
 
 ---
 
-However pull requests provide an explicit way for review, discussion and approval.
+However pull requests provide an **explicit** mechanism for review, discussion and approval.
 
-Most git hosting providers have additional tools and controls to make reviews mandatory.
+Most git hosting providers have additional tools and controls to make these processes easier and mandatory.
 
 ---