Resolve #133 and #134

Author: bowbahdoe

src/the_terminal/commands.md

@@ -2,12 +2,14 @@
 
 The primary way you interact with a terminal is by running commands.
 
-You start with a blank prompt and write something like the following.
+You start with a blank prompt and write something like the following[^nottyped].
 
 ```bash
 $ echo Hello
 Hello
 ```
 
 The first word is the name of the program to run. In this case `echo`. Everything after
-that is an "argument" to the program.
+that is an "argument" to the program.
+
+[^nottyped] You don't actually type the `$`. That is illustrative. Your terminal will give you something like a `$` or a `>` as a "prompt."

src/the_terminal/creating_files.md

@@ -1,6 +1,6 @@
 # Creating Files
 
-To create a blank file you can use the `touch`[^no_clue] command.
+To create a blank file you can use the `touch`[^why] command.
 
 ```bash
 $ touch hello.txt
@@ -12,8 +12,10 @@ using a program called a "text editor."
 There are some text editors, like [`vim`](https://www.vim.org/), which run entirely
 inside the terminal.[^diehard]
 
-One of the more popular ones at time of writing is [Visual Studio Code](https://code.visualstudio.com/). If you weren't otherwise shown a different option, that is a decent default. Install it and then you can use it to create and edit files.
+At the start of this book I showed you [VSCodium](https://vscodium.com/). If you weren't otherwise shown a different option, that is a decent default. You can use it to create and edit files.
+
+[^why]: This is called `touch` because it will "touch" a file and update its "last updated timestamp" but change nothing else.
 
-[^no_clue]: I have no clue why this is called `touch`.
 [^diehard]: These have their die hard supporters. The lunatics.
+
 [^thisbook]: This book has been written inside Visual Studio Code.