Merge pull request #11 from astroDimitrios/spolier_syntax_fix

Fix spoiler syntax for FCM comparisons.

episodes/01-basics.md

@@ -81,13 +81,15 @@ the same files concurrently.
 
 :::::::::::::::::::::::::::::::::::::::::  callout
 
-## Moving to Git from FCM
+## Migrating to Git from FCM
 
 If you currently use [FCM](https://metomi.github.io/fcm/doc/user_guide/getting_started.html) 
 (a wrapper around Subversion, SVN) then look out for the following dropdowns.
 They contain the FCM equivalent for git commands.
 
-::: spoiler FCM Comparison
+::: spoiler
+
+### FCM Comparison
 
 Running the `git ...` command is equivalent to:
 

episodes/03-create.md

@@ -96,7 +96,9 @@ No commits yet
 nothing to commit (create/copy files and use "git add" to track)
 ```
 
-::: spoiler FCM Comparison
+::: spoiler
+
+### FCM Comparison
 
 `git status` is equivalent to:
 

episodes/04-changes.md

@@ -140,7 +140,9 @@ so that we can write a longer message.
 changes made in the commit. Generally, the message should complete the sentence "If applied, this commit will" <commit message here>.
 If you want to go into more detail, add a blank line between the summary line and your additional notes. Use this additional space to explain why you made changes and/or what their impact will be.
 
-::: spoiler FCM Comparison
+::: spoiler
+
+### FCM Comparison
 
 Running `git add` followed by `git commit` is equivalent to:
 
@@ -186,7 +188,9 @@ the commit's author,
 when it was created,
 and the log message Git was given when the commit was created.
 
-::: spoiler FCM Comparison
+::: spoiler
+
+### FCM Comparison
 
 `git log` is equivalent to:
 

episodes/05-history.md

@@ -211,7 +211,9 @@ By default,
 it recovers the version of the file recorded in `HEAD`,
 which is the last saved commit.
 
-::: spoiler FCM Comparison
+::: spoiler
+
+### FCM Comparison
 
 `git restore` is equivalent to: