fix: add blank lines in exercises for proper list rendering

MkDocs requires a blank line between a paragraph and a numbered list.
Without it, Steps and Verify sections rendered as a single paragraph.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: braboj

docs/01-Introduction/07-exercises.md

@@ -8,11 +8,14 @@ in this chapter if you get stuck. Do not skip the verification steps.
 **Task:** Confirm that Git is installed and check which version you are running.
 
 **Steps:**
+
 1. Open a terminal (PowerShell on Windows, a shell on Linux/macOS)
 2. Run the command to display the installed Git version
 3. Run the command to display the built-in help overview
 
-**Verify:** The version command prints a line starting with `git version` followed by
+**Verify:**
+
+The version command prints a line starting with `git version` followed by
 a version number. The help command prints a list of common Git commands grouped
 by category.
 
@@ -24,12 +27,15 @@ by category.
 you make.
 
 **Steps:**
+
 1. Set your global user name using `git config`
 2. Set your global email address using `git config`
 3. Read back both values to confirm they are stored correctly
 4. Display the full list of configuration settings with `git config --list`
 
-**Verify:** The read-back commands print exactly the name and email you entered.
+**Verify:**
+
+The read-back commands print exactly the name and email you entered.
 Both entries also appear in the `--list` output.
 
 ---
@@ -39,6 +45,7 @@ Both entries also appear in the `--list` output.
 **Task:** Initialise a brand-new local Git repository and make your first commit.
 
 **Steps:**
+
 1. Create a new directory called `git-exercises` and enter it
 2. Initialise a Git repository inside the directory
 3. Create a file called `hello.txt` with some text in it
@@ -47,7 +54,9 @@ Both entries also appear in the `--list` output.
 6. Check the status again to see the file is staged
 7. Commit the staged file with the message `Add hello.txt`
 
-**Verify:** Running `git log` shows one commit with the message `Add hello.txt`.
+**Verify:**
+
+Running `git log` shows one commit with the message `Add hello.txt`.
 Running `git status` reports a clean working tree with nothing to commit.
 
 ---
@@ -59,6 +68,7 @@ index, and local repository — by making a change and moving it through
 the pipeline.
 
 **Steps:**
+
 1. Inside the `git-exercises` repository, edit `hello.txt` and add a second line
 2. Run `git status` to see the file listed as modified (workspace)
 3. Run `git diff` to see the exact change
@@ -68,7 +78,9 @@ the pipeline.
 7. Commit the change with a descriptive message
 8. Run `git log` to confirm the new commit appears in the local repository
 
-**Verify:** `git status` reports a clean working tree. `git log` shows two commits
+**Verify:**
+
+`git status` reports a clean working tree. `git log` shows two commits
 in chronological order.
 
 ---
@@ -79,6 +91,7 @@ in chronological order.
 object contents, and repository status.
 
 **Steps:**
+
 1. Run `git log` to see the full commit history
 2. Run `git log --oneline` to see a compact view
 3. Copy the short hash of the first commit from the oneline output
@@ -87,7 +100,9 @@ object contents, and repository status.
 6. Note the tree hash printed in the output, then run `git cat-file -p <tree-hash>`
    to list the files recorded in that commit
 
-**Verify:** The `-t` command prints `commit`. The `-p` command on the commit shows
+**Verify:**
+
+The `-t` command prints `commit`. The `-p` command on the commit shows
 author, committer, tree hash, and the commit message. The `-p` command on the tree
 lists the `hello.txt` blob.
 
@@ -99,6 +114,7 @@ lists the `hello.txt` blob.
 repository, and push your commits.
 
 **Steps:**
+
 1. Sign in to GitHub (or another hosting service from the reference page)
 2. Create a new empty repository named `git-exercises` — do not add a README
    or any other files
@@ -109,6 +125,8 @@ repository, and push your commits.
 6. Push the local commits to the remote with `git push -u origin main`
 7. Refresh the repository page in the browser
 
-**Verify:** The hosting service shows all committed files and the full commit
+**Verify:**
+
+The hosting service shows all committed files and the full commit
 history matches what `git log` displays locally. Running `git branch -av`
 shows both the local and remote branch pointing to the same commit.

docs/02-Concepts/17-exercises.md

@@ -10,6 +10,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Initialize a new Git repository and explore its internal structure.
 
 **Steps:**
+
 1. Create a new directory called `concepts-lab` and navigate into it
 2. Run `git init` to create a repository
 3. List the contents of the `.git` directory
@@ -18,7 +19,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 6. Create a bare repository called `concepts-lab.git` in a sibling directory using `git init --bare`
 7. Compare the directory structure of the bare repository with the `.git` folder
 
-**Verify:** The `.git` directory exists and contains `objects`, `refs`, `HEAD`, and `config`. The bare repository has the same internal structure but no working tree.
+**Verify:**
+
+The `.git` directory exists and contains `objects`, `refs`, `HEAD`, and `config`. The bare repository has the same internal structure but no working tree.
 
 ---
 
@@ -27,6 +30,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Set user name and email at the local and global levels and observe which one takes precedence.
 
 **Steps:**
+
 1. Inside `concepts-lab`, set a global user name and email using `git config --global`
 2. Set a different local user name and email using `git config --local`
 3. Run `git config --list --show-origin` to see all active settings and their sources
@@ -35,7 +39,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 6. Remove the local overrides using `git config --local --unset user.name` and `git config --local --unset user.email`
 7. Make another commit and verify the global identity is now used
 
-**Verify:** The first commit shows the local identity. The second commit shows the global identity. `git config --list --show-origin` displays both levels and marks which file each setting comes from.
+**Verify:**
+
+The first commit shows the local identity. The second commit shows the global identity. `git config --list --show-origin` displays both levels and marks which file each setting comes from.
 
 ---
 
@@ -44,6 +50,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Create blobs, trees, and commits, then inspect them with plumbing commands.
 
 **Steps:**
+
 1. In `concepts-lab`, create a file called `hello.txt` with the content `Hello, Git!`
 2. Stage the file with `git add hello.txt`
 3. Run `git ls-files --stage` and note the blob hash next to the file name
@@ -55,7 +62,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 9. Verify that the tree references the same blob hash from step 3
 10. Browse the `.git/objects` directory and locate the two-character subdirectory matching the first two characters of the blob hash
 
-**Verify:** `git cat-file -p` on the blob prints `Hello, Git!`. The tree object lists the blob hash with mode `100644` and file name `hello.txt`. The corresponding object file exists on disk under `.git/objects`.
+**Verify:**
+
+`git cat-file -p` on the blob prints `Hello, Git!`. The tree object lists the blob hash with mode `100644` and file name `hello.txt`. The corresponding object file exists on disk under `.git/objects`.
 
 ---
 
@@ -64,6 +73,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Create both tag types and compare how Git stores them internally.
 
 **Steps:**
+
 1. In `concepts-lab`, make sure you have at least one commit
 2. Create a lightweight tag called `v0.1` using `git tag v0.1`
 3. Create an annotated tag called `v1.0` with the message `First release` using `git tag -a v1.0 -m "First release"`
@@ -73,7 +83,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 7. Run `git cat-file -t` on both hashes and compare the object types
 8. Run `git cat-file -p` on the annotated tag hash and inspect the tagger, date, message, and target reference
 
-**Verify:** The lightweight tag hash points directly to a commit object (`git cat-file -t` prints `commit`). The annotated tag hash points to a tag object (`git cat-file -t` prints `tag`), which in turn references the commit.
+**Verify:**
+
+The lightweight tag hash points directly to a commit object (`git cat-file -t` prints `commit`). The annotated tag hash points to a tag object (`git cat-file -t` prints `tag`), which in turn references the commit.
 
 ---
 
@@ -82,6 +94,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Use the index to selectively stage changes and observe its contents.
 
 **Steps:**
+
 1. In `concepts-lab`, create two files: `tracked.txt` and `experimental.txt`
 2. Stage only `tracked.txt` with `git add tracked.txt`
 3. Run `git ls-files --stage` to see what is in the index
@@ -92,7 +105,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 8. Run `git ls-files --stage` a final time and confirm only `tracked.txt` remains
 9. Commit the staged file
 
-**Verify:** After step 7, `git ls-files --stage` shows only `tracked.txt`. After the commit, `git status` shows `experimental.txt` as untracked and the working tree is otherwise clean.
+**Verify:**
+
+After step 7, `git ls-files --stage` shows only `tracked.txt`. After the commit, `git status` shows `experimental.txt` as untracked and the working tree is otherwise clean.
 
 ---
 
@@ -101,6 +116,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Practice the full branch lifecycle and observe how references change.
 
 **Steps:**
+
 1. In `concepts-lab`, confirm you are on the `main` branch with `git branch`
 2. Read `.git/refs/heads/main` and note the commit hash
 3. Create a new branch called `feature/greeting` using `git branch feature/greeting`
@@ -112,7 +128,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 9. Read `.git/refs/heads/main` and confirm it still points to the original commit
 10. Switch back to `main` and delete the branch with `git branch -d feature/greeting`
 
-**Verify:** After deletion, the file `.git/refs/heads/feature/greeting` no longer exists. `git branch` lists only `main`. The commit created on the feature branch becomes unreachable.
+**Verify:**
+
+After deletion, the file `.git/refs/heads/feature/greeting` no longer exists. `git branch` lists only `main`. The commit created on the feature branch becomes unreachable.
 
 ---
 
@@ -121,6 +139,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Create a merge conflict, inspect the conflict markers, and resolve it manually.
 
 **Steps:**
+
 1. In `concepts-lab`, create a file `config.txt` with the line `mode=production` and commit it on `main`
 2. Create and switch to a branch `feature/debug` using `git switch -c feature/debug`
 3. Change the line in `config.txt` to `mode=debug` and commit
@@ -132,7 +151,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 9. Edit `config.txt` to resolve the conflict by choosing one value or combining them
 10. Stage the resolved file with `git add config.txt` and complete the merge with `git commit`
 
-**Verify:** After the merge commit, `git log --oneline --graph` shows the two branches converging. `git ls-files --stage` shows a single stage-0 entry for `config.txt`. The file contains the resolved content with no conflict markers.
+**Verify:**
+
+After the merge commit, `git log --oneline --graph` shows the two branches converging. `git ls-files --stage` shows a single stage-0 entry for `config.txt`. The file contains the resolved content with no conflict markers.
 
 ---
 
@@ -141,6 +162,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Use the stash to save uncommitted changes, switch branches, then restore them.
 
 **Steps:**
+
 1. In `concepts-lab`, make sure you are on `main` with a clean working tree
 2. Create a file `notes.txt` with the content `Work in progress`
 3. Stage the file with `git add notes.txt`
@@ -152,7 +174,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 9. Restore the stashed changes with `git stash pop`
 10. Confirm `notes.txt` is back in the working tree and staged
 
-**Verify:** After `git stash pop`, `git status` shows `notes.txt` as a staged new file. `git stash list` is empty.
+**Verify:**
+
+After `git stash pop`, `git status` shows `notes.txt` as a staged new file. `git stash list` is empty.
 
 ---
 
@@ -161,6 +185,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Stage only some changes from a single file to make a focused commit.
 
 **Steps:**
+
 1. In `concepts-lab`, create a file `multi.txt` with three lines: `line1`, `line2`, `line3` and commit it
 2. Modify the file so that `line1` becomes `LINE1` and `line3` becomes `LINE3` (leave `line2` unchanged)
 3. Run `git diff` to confirm both hunks appear
@@ -170,7 +195,9 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 7. Commit the staged hunk
 8. Stage and commit the remaining change
 
-**Verify:** `git log --oneline` shows two separate commits. Running `git diff HEAD~1 HEAD~2` shows only the `line1` change. Running `git diff HEAD HEAD~1` shows only the `line3` change.
+**Verify:**
+
+`git log --oneline` shows two separate commits. Running `git diff HEAD~1 HEAD~2` shows only the `line1` change. Running `git diff HEAD HEAD~1` shows only the `line3` change.
 
 ---
 
@@ -179,6 +206,7 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 **Task:** Apply a simplified Git Flow workflow using branches and merges.
 
 **Steps:**
+
 1. Create a fresh repository called `flow-lab` and navigate into it
 2. Create an initial commit on `main` with a file `app.txt` containing `v1.0`
 3. Create a `develop` branch from `main` and switch to it
@@ -191,4 +219,6 @@ All exercises use a fresh, disposable repository unless stated otherwise.
 10. Delete the release branch
 11. Run `git log --oneline --graph --all` to visualize the full history
 
-**Verify:** `main` and `develop` both contain the `v1.1` change and the `login.txt` file. The tag `v1.1` exists and points to the merge commit on `main`. The feature and release branches are deleted. The graph shows the expected merge topology.
+**Verify:**
+
+`main` and `develop` both contain the `v1.1` change and the `login.txt` file. The tag `v1.1` exists and points to the merge commit on `main`. The feature and release branches are deleted. The graph shows the expected merge topology.