Update INSTALL.md

diff --git a/INSTALL.md b/INSTALL.md
index b8f96b1977c4e16a48cdeeb9ca19eb951cec2dee..575600d87da184afdf2ac7e623cd11e7d04d0f19 100644 (file)
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -1,8 +1,10 @@
-# thus is not a POSIX compliant shell
+# Installing thus
+
+## thus is not a POSIX compliant shell
 
 thus uses a distinctly different syntax than other POSIX compliant shells. While fine for an end user to learn, some programs rely on POSIX compilant shells to run internal commands or scripts. Therefore, **it is not recommended that thus be set to the user's default shell**. Instead, thus should be automatically run by a separate POSIX compilant shell which in turn is set as the user's default shell. This allows utilities to function as before while presenting thus as the default shell in an interactive session.
 
-# "Installing" thus
+## Example configuration
 
 Here is a minimal example which assumes sh as the user's default shell (a similar approach can be used for other shells). We'll need to modify the scripts that are executed at login and during an interactive session. For sh, the login configuration file is `.profile`.
 
@@ -23,6 +25,6 @@ THUSLOGIN=-l
 test -z "$EXEUNT" && echo $- | grep -q i && exec thus $THUSLOGIN
 ```
 
-`THUSLOGIN` will be set to the `-l` flag only in the case when sh is running as a login shell. Running thus with the `-l` flag starts it up as a login shell.
+`THUSLOGIN` will be set to the `-l` flag only in the case when sh is running as a login shell. Running thus with the `-l` flag starts *it* as a login shell.
 
 Notice if sh is called from within thus, then it will run *as* thus which makes it impossible to open sh as an interactive subshell. This is why the `EXEUNT` environment variable is used as a guard in the command list. Defining `EXEUNT` will make all subsequent calls to sh as an interactive shell actually open sh, not thus.