Just a few basic clean-ups.

4 files changed, 23 insertions, 16 deletions

diff --git a/TODO b/TODO
index 5e3e67e..0f0818b 100644
--- a/TODO
+++ b/TODO
@@ -16,8 +16,15 @@ General
     in reference to how the admin might be misled into thinking that they are
     causing breakage...
 
-Chapter 2.
-* Booting the Installer
+Chapter 2. Installation
+
+* Section 'Booting the Installer'
+
+  Does this need to be reworked? Feels kinda kludgy and amateur.
+
+* At the tail end we might wish to tell the user about adduser and
+  inform him that he can skip ahead to chapter 9 briefly if he needs
+  more info.
 
 Chapter 4. Basic Shell Commands
 
diff --git a/chapter_01.xml b/chapter_01.xml
index 3dafaeb..c1e2bef 100644
--- a/chapter_01.xml
+++ b/chapter_01.xml
@@ -83,7 +83,7 @@ the Samba project, are released under the terms of the GPL.
 
 <para>
 Another very common license is the BSD license, which is arguably "more
-free" than the GPL but imposes no restrictions on derivative works.
+free" than the GPL because it imposes no restrictions on derivative works.
 The BSD license simply requires that the copyright remain intact along
 with a simple disclaimer.  Many of the utilities specific to Slackware
 are licensed with a BSD-style license.
diff --git a/chapter_02.xml b/chapter_02.xml
index c817bf4..1a4ef26 100644
--- a/chapter_02.xml
+++ b/chapter_02.xml
@@ -34,13 +34,13 @@ RAM.
 <title>Booting the Installer</title>
 
 <para>
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
-FILL THIS IN!  FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
+FILL THIS IN!
 </para>
 
 <para>
diff --git a/chapter_04.xml b/chapter_04.xml
index 827b92f..8ffeec3 100644
--- a/chapter_04.xml
+++ b/chapter_04.xml
@@ -21,7 +21,7 @@ that is what this chapter is all about.
 <para>
 Your Slackware Linux system comes with lots of built-in documentation
 for nearly every installed application.  Perhaps the most common method
-of reading system documentation is by using the
+of reading system documentation is 
 <application>man</application>(1).  <application>man</application>
 (short for manual) will bring up the included man-page for any
 application, system call, configuration file, or library you tell it
@@ -279,7 +279,8 @@ unless the first two already existed, as you saw in the example.
 
 <para>
 Removing a file is as easy as creating one.  The
-<application>rm</application>(1) will remove a file (assuming of course
+<application>rm</application>(1) command will remove a file 
+(assuming of course
 that you have permission to do this).  There are a few very common
 arguments to <application>rm</application>.  The first is
 <arg>-f</arg> and is used to force the removal of a file
@@ -342,8 +343,7 @@ order to deal with directories.
 </para>
 
 <screen><prompt>darkstar:~$ </prompt><userinput>zip -r /tmp/home.zip /home</userinput>
-<prompt>darkstar:~$ </prompt><userinput>zip /tmp/large_file.zip
-/tmp/large_file</userinput></screen>
+<prompt>darkstar:~$ </prompt><userinput>zip /tmp/large_file.zip /tmp/large_file</userinput></screen>
 
 <para>
 The order of the arguments is very important. The first filename must
@@ -423,8 +423,8 @@ One alternative to <application>gzip</application> is the
 almost the exact same way.  The advantage to
 <application>bzip2</application> is that it boasts greater compression
 strength. Unfortunately, achieving that greater compression is a slow
-process, so <application>bzip2</application> takes longer to run than
-other alternatives.
+and CPU-intensive process, so <application>bzip2</application> 
+typicall takes much longer to run than other alternatives.
 </para>
 
 </section>