Improve raw README.md readability

diff --git a/README.md b/README.md
index 0207371cba2b1cb7cd996b547fbb8d206e09d4ab..5f134a031f76321db10dfab76e28e22283c2bb7e 100644 (file)
--- a/README.md
+++ b/README.md
@@ -18,22 +18,25 @@ thus is a custom Unix shell for POSIX platforms.
 
 ## Building
 
-thus uses [cbs](https://github.com/trenthuber/cbs/) as its build system.
+thus uses [cbs](https://trenthuber.com/code/cbs.git/) as its build system.
 
 ```console
-> git clone --recursive https://github.com/trenthuber/thus/
+> git clone --recursive https://trenthuber.com/git/thus.git
 > cd thus/
 > cc -o build build.c
 > build
 ```
 
-After building, you can use `install` to add the shell to your path. The default installation prefix is `/usr/local/`, but a custom one can be passed as an argument to the utility.
+After building, you can use `install` to add the shell to your path. The default
+installation prefix is `/usr/local/`, but a custom one can be passed as an
+argument to the utility.
 
 ```console
 > sudo ./install
 ```
 
-After installing, you can use `uninstall` to remove the shell from the install location.
+After installing, you can use `uninstall` to remove the shell from the install
+location.
 
 ```console
 > sudo ./uninstall
@@ -41,24 +44,38 @@ After installing, you can use `uninstall` to remove the shell from the install l
 
 ## Quirks
 
-While thus operates for the most part like Bourne shell, there are a few places where it takes a subtly different approach.
+While thus operates for the most part like Bourne shell, there are a few places
+where it takes a subtly different approach.
 
 ### Quotes
 
-Quoting is done with double quotes (`"..."`) and undergoes no shell substitution, similar to single quotes in Bourne shell. In place of substitution, quotes can be concatenated with surrounding tokens not separated by whitespace.
+Quoting is done with double quotes (`"..."`) and undergoes no shell
+substitution, similar to single quotes in Bourne shell. In place of
+substitution, quotes can be concatenated with surrounding tokens not separated
+by whitespace.
 
 ### Environment variables and aliases
 
-Environment variables are referred to by tokens that begin and end with a `$`. For example, evaluating the path would look like `$PATH$`. Setting environment variables is done with the `set` built-in command, not with the `name=value` syntax. This syntax is similarly avoided when declaring aliases with the `alias` built-in command.
+Environment variables are referred to by tokens that begin and end with a `$`.
+For example, evaluating the path would look like `$PATH$`. Setting environment
+variables is done with the `set` built-in command, not with the `name=value`
+syntax. This syntax is similarly avoided when declaring aliases with the `alias`
+built-in command.
 
 ### Leading and trailing slashes
 
-Prepending `./` to executables located in the current directory is not mandatory unless there already exists an executable in `$PATH$` with the same name that you would like to override.
+Prepending `./` to executables located in the current directory is not mandatory
+unless there already exists an executable in `$PATH$` with the same name that
+you would like to override.
 
-The `$HOME$`, `$PWD$`, and `$PATH$` environment variables are always initialized with trailing slashes. Therefore, whenever one of these variables or `~` is substituted in the shell, it will retain the trailing slash.
+The `$HOME$`, `$PWD$`, and `$PATH$` environment variables are always initialized
+with trailing slashes. Therefore, whenever one of these variables or `~` is
+substituted in the shell, it will retain the trailing slash.
 
 ## Resources
 
 - [TTY Demystified](http://www.linusakesson.net/programming/tty/)
-- [Process Groups and Terminal Signaling](https://cs162.org/static/readings/ic221_s16_lec17.html)
-- [Terminal Input Sequences](https://en.wikipedia.org/wiki/ANSI_escape_code#Terminal_input_sequences)
+- [Process Groups and Terminal Signaling](
+https://cs162.org/static/readings/ic221_s16_lec17.html)
+- [Terminal Input Sequences](
+https://en.wikipedia.org/wiki/ANSI_escape_code#Terminal_input_sequences)