Index: general/genlib/genlib.xml
===================================================================
--- general/genlib/genlib.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ general/genlib/genlib.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -41,6 +41,6 @@
 
   <para>There are certain libraries which nearly <emphasis>everyone</emphasis>
-  will need at some point.  In this chapter we list these and some others and
-  explain why you may want to install them.</para>
+  will need at some point.  In this chapter these and some others are listed and
+  it is explained why you may want to install them.</para>
 
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="apr.xml"/>
Index: general/genlib/libatomic_ops.xml
===================================================================
--- general/genlib/libatomic_ops.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ general/genlib/libatomic_ops.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -104,12 +104,14 @@
 
     <para>
-      <command>sed -i 's#AC_PROG_RANLIB ...</command>: These seds massage the
-      autotool files so that a shared library is built, the tests pass and the
-      docs are installed where we want.
+      <command>sed -i 's#AC_PROG_RANLIB ...</command>: These
+      <command>sed</command>s massage the autotool files so that a shared 
+      library is built, the tests pass, and the docs are installed in an
+      appropriate directory.
     </para>
 
     <para>
-      <command>autoreconf -i</command>: This regenerates the configure script
-      and the Makefile.in files and installs a missing file.
+      <command>autoreconf -i</command>: This regenerates the
+      <command>configure</command> script and the <filename>Makefile.in</filename>
+      files and installs a missing file.
     </para>
 
Index: gnome/core/gnome-session.xml
===================================================================
--- gnome/core/gnome-session.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ gnome/core/gnome-session.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -139,5 +139,5 @@
 
       <para>
-        If you are not using <application>gdm</application> to start your
+        If you are not using <application>GDM</application> to start your
         <application>GNOME</application> desktop, you will need to invoke
         <command>gnome-session</command> <emphasis>instead of</emphasis> invoking
@@ -153,8 +153,8 @@
         daemons and either <application>Metacity</application> or
         <application>gnome-shell</application>. A desktop manager such as
-        <application>gdm</application> will invoke <application>ConsoleKit</application>
+        <application>GDM</application> will invoke <application>ConsoleKit</application>
         before the window manager, but if you use <command>startx</command> the first
         invocation after booting may fail because the daemon is not already running,
-        so we will invoke it first.
+        so it is invoked first.
       </para>
 
@@ -164,6 +164,6 @@
         backup your current <filename>~/.xinitrc</filename> before proceeding.
         Note that you will be able to invoke <application>GNOME Terminal</application>
-        from the menu, so there is no reason to invoke xterm here. Create a new
-        <filename>.xinitrc</filename> using this command:
+        from the menu, so there is no reason to invoke <command>xterm</command> here.
+        Create a new <filename>.xinitrc</filename> using this command:
       </para>
 
Index: introduction/important/building-notes.xml
===================================================================
--- introduction/important/building-notes.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ introduction/important/building-notes.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -17,12 +17,12 @@
 
   <para>Those people who have built an LFS system may be aware
-  of the general principles of downloading and unpacking software.  We will
-  however repeat some of that information here for those new to building
+  of the general principles of downloading and unpacking software. Some
+  of that information is repeated here for those new to building
   their own software.</para>
 
   <para>Each set of installation instructions contains a URL from which you
-  can download the package.  We do however keep a selection of patches
-  available via HTTP.  These are referenced as needed in the installation
-  instructions.</para>
+  can download the package.  The patches; however, are stored on the LFS
+  servers and are available via HTTP.  These are referenced as needed in the
+  installation instructions.</para>
 
   <para>While you can keep the source files anywhere you like, we assume that
Index: introduction/important/libraries.xml
===================================================================
--- introduction/important/libraries.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ introduction/important/libraries.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -29,5 +29,5 @@
     systems they are the only type available.</para>
 
-    <para>On almost all Linux platforms we also have shared libraries 
+    <para>On almost all Linux platforms there are also shared libraries 
     (libfoo.so) - one copy of the library is loaded into virtual memory, and 
     shared by all the programs which call any of its functions. This is space 
Index: introduction/important/locale-issues.xml
===================================================================
--- introduction/important/locale-issues.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ introduction/important/locale-issues.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -282,5 +282,5 @@
     # Non-UTF-8 manual page is OK
     iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue
-    # If we got here, we found UTF-8 manual page, bad.
+    # Found a UTF-8 manual page, bad.
     echo "UTF-8 manual page: $a" >&amp;2
 done
Index: introduction/welcome/packages.xml
===================================================================
--- introduction/welcome/packages.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ introduction/welcome/packages.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -30,5 +30,5 @@
 
   <para>We would like to ask a favor, however.  Although this is a public
-  resource for you to use, we do not want to abuse it.  We have already had one
+  resource for you to use, please do not abuse it.  We have already had one
   unthinking individual download over 3 GB of data, including multiple copies of
   the same files that are placed at different locations (via symlinks) to make
Index: introduction/welcome/which.xml
===================================================================
--- introduction/welcome/which.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ introduction/welcome/which.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -19,5 +19,5 @@
   followed in a linear manner. This is because LFS provides instructions
   on how to create a base system which is capable of turning into anything
-  from a web server to a multimedia desktop system. BLFS is where we try
+  from a web server to a multimedia desktop system. BLFS attempts
   to guide you in the process of going from the base system to your intended
   destination. Choice is very much involved.</para>
Index: multimedia/libdriv/libdvdnav.xml
===================================================================
--- multimedia/libdriv/libdvdnav.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ multimedia/libdriv/libdvdnav.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -89,6 +89,7 @@
 
     <para><command>./autogen.sh</command>: This package does not come with the
-    normal configure script, so we need to use the <command>autogen.sh</command>
-    script to generate and run <command>configure</command>.</para>
+    normal <command>configure</command> script, so
+    the <command>autogen.sh</command> script is used to generate and run
+    <command>configure</command>.</para>
   </sect2>
 
Index: multimedia/libdriv/libdvdread.xml
===================================================================
--- multimedia/libdriv/libdvdread.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ multimedia/libdriv/libdvdread.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -83,6 +83,7 @@
 
     <para><command>./autogen.sh</command>: This package does not come with the
-    normal configure script, so we need to use the <command>autogen.sh</command>
-    script to generate and run <command>configure</command>.</para>
+    normal <command>configure</command> script, so the
+    <command>autogen.sh</command> script is used to generate and run
+    <command>configure</command>.</para>
   </sect2>
 
Index: networking/netutils/wicd.xml
===================================================================
--- networking/netutils/wicd.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ networking/netutils/wicd.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -132,16 +132,24 @@
   <sect2 role="commands">
     <title>Command Explanations</title>
-    <para><command>sed -i '/wpath...</command>: The sed prevents installation of logrotate
-    and systemd configuration files. You may omit it if you use these utilities.</para>
-    <para><option>--no-install-kde</option>: Prevent installation of  
+
+    <para><command>sed -i '/wpath...</command>: This <command>sed</command>
+    prevents installation of <command>logrotate</command> and systemd
+    configuration files. You may omit it if you use these utilities.</para>
+
+    <para><option>--no-install-kde</option>: Prevent installation of an 
     autostart desktop file for KDE. If you use KDE, you should instead install the 
     <ulink url="http://projects.kde.org/projects/extragear/network/wicd-kde">Wicd KDE Client</ulink>.
     </para>
+
     <para><option>--no-install-acpi</option>: Prevent installation of  
-    suspend and resume scripts for acpid. Omit this option if you use acpid.</para>
+    <command>suspend</command> and <command>resume</command> scripts for acpid.
+    Omit this option if you use acpid.</para>
+
     <para><option>--no-install-pmutils</option>: Prevent installation of hooks for 
     pm-utils. Omit this option if you use pm-utils.</para>
+
     <para><option>--no-install-init</option>: Prevent installation of any init scripts, 
-    as we install our own bootscript.</para>
+    as a bootscript is installed later in the instructions.</para>
+
     <para><option>--wicdgroup=<replaceable>&lt;group&gt;</replaceable></option>: 
     The group that will have permission to use the Wicd client (default is the 
@@ -186,5 +194,5 @@
       frontends. If you are only going to use Wicd from command-line, you can configure
       it using the configuration files in <filename>/etc/wicd</filename>. For a list of 
-      available options, take a look at the man-pages for: wicd-manager-settings.conf, 
+      available options, look at the man-pages for: wicd-manager-settings.conf, 
       wicd-wired-settings.conf and wicd-wireless-settings.conf.</para>
       
Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/config/bootdisk.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -30,5 +30,5 @@
     used as a rescue device: floppy, cdrom, usb drive, or even a network card.
     Which one you use depends on your hardware and your BIOS.  In the past,
-    we usually thought of rescue device as a floppy disk.  Today, many
+    a rescue device was thought to be a floppy disk.  Today, many
     systems do not even have a floppy drive.</para>
 
Index: postlfs/config/inputrc.xml
===================================================================
--- postlfs/config/inputrc.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/config/inputrc.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -63,5 +63,5 @@
 <literal># Begin /etc/inputrc
 
-# Make sure we don't output everything on the 1 line
+# Make sure everything is not output to one line
 set horizontal-scroll-mode Off
 
Index: postlfs/config/profile.xml
===================================================================
--- postlfs/config/profile.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/config/profile.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -273,5 +273,5 @@
 
 <screen role="root"><userinput>cat &gt; /etc/profile.d/umask.sh &lt;&lt; "EOF"
-<literal># By default we want the umask to get set.
+<literal># By default, the umask should be set.
 if [ "$(id -gn)" = "$(id -un)" -a $EUID -gt 99 ] ; then
   umask 002
Index: postlfs/filesystems/aboutlvm.xml
===================================================================
--- postlfs/filesystems/aboutlvm.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/filesystems/aboutlvm.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -58,5 +58,5 @@
   </variablelist> 
 
-  <para>To give a concrete example, suppose that we have two 2 TB disks.
+  <para>To give a concrete example, suppose that you have two 2 TB disks.
   Also suppose a really large amount of space is required for a very large database,
   mounted on <filename class='directory'>/srv/mysql</filename>.  This is what
Index: postlfs/filesystems/aboutraid.xml
===================================================================
--- postlfs/filesystems/aboutraid.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/filesystems/aboutraid.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -114,10 +114,10 @@
 sdd2:     300 GB   fd Linux raid auto  /home    (RAID 5) /dev/md2 </literal></screen>
 
-    <para>Is this arrangement, we are creating a separate boot partition as the
+    <para>Is this arrangement, a separate boot partition is created as the
     first small RAID array and a root filesystem as the secong RAID array,
     both mirrored.  The third partition is a large (about 1TB) array for the
     <filename class='directory'>/home</filename> directory.  This provides
     an ability to stripe data across multiple devices, improving speed for 
-    botih reading and writing large files.  Finally, we create a fourth array
+    botih reading and writing large files.  Finally, a fourth array is created
     that concatenates two partitions into a larger device.</para>
 
Index: postlfs/virtualization/qemu-kvm.xml
===================================================================
--- postlfs/virtualization/qemu-kvm.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ postlfs/virtualization/qemu-kvm.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -179,5 +179,5 @@
 
     <para>To install an operating system, download an iso of your choice or use
-    a pre-intalled cdrom device.  For the purposes of this example, we will use
+    a pre-intalled cdrom device.  For the purposes of this example, use
     Fedora 16 that is downloaded as
     <filename>Fedora-16-x86_64-Live-LXDE.iso</filename> in the current
Index: pst/printing/gs.xml
===================================================================
--- pst/printing/gs.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ pst/printing/gs.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -248,5 +248,5 @@
       JPEG 2000 files <!-- I can't get it to compile using a system installed
       version of openjpeg. It seems the ghostscript version has been heavily
-      modified... --> so we can all remove the jasper source. The default color
+      modified... --> so jasper source can be removed. The default color
       management system is now <application>lcms2</application> so the
       <application>lcms</application> source is not needed.
@@ -260,6 +260,6 @@
 
     <para>
-      <parameter>LIBS=-lz</parameter>: We use the LIBS variable to tell the
-      linker (ld) to link against the system installed
+      <parameter>LIBS=-lz</parameter>: Use the <envar>LIBS</envar> variable to
+      tell the linker (ld) to link against the system installed
       <application>zlib</application>.
     </para>
Index: xsoft/graphweb/firefox.xml
===================================================================
--- xsoft/graphweb/firefox.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ xsoft/graphweb/firefox.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -317,10 +317,11 @@
 
     <para>
-      <command>ln -sfv ... /usr/bin/firefox</command>: this puts a symbolic link
-      to the <command>firefox</command> executable in your ${PATH}.
-    </para>
-
-    <para>
-      <command>mkdir -p /usr/lib/mozilla/plugins</command>: this checks
+      <command>ln -sfv ... /usr/bin/firefox</command>: This puts a symbolic link
+      to the <command>firefox</command> executable in your <envar>PATH</envar>
+      variable.
+    </para>
+
+    <para>
+      <command>mkdir -p /usr/lib/mozilla/plugins</command>: This checks
       that <filename class="directory">/usr/lib/mozilla/plugins</filename>
       exists.
@@ -328,10 +329,10 @@
 
     <para>
-      <command>ln -sv ... /usr/lib/firefox-&firefox-version;</command>: this
+      <command>ln -sv ... /usr/lib/firefox-&firefox-version;</command>: This
       makes a symbolic link to
       <filename class="directory">/usr/lib/mozilla/plugins</filename>. It's not
-      really needed, <application>Firefox</application> checks
+      really needed, as <application>Firefox</application> checks
       <filename class="directory">/usr/lib/mozilla/plugins</filename> by
-      default, we make the symbolic link to keep all the plugins installed in
+      default, but the symbolic link is made to keep all the plugins installed in
       one folder.
     </para>
Index: xsoft/office/libreoffice.xml
===================================================================
--- xsoft/office/libreoffice.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ xsoft/office/libreoffice.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -315,6 +315,6 @@
       <command>./download</command>: The build process runs the
       <command>download</command> script which downloads some 470 MB of
-      tarballs. We run the download script to get it out of the way at the
-      start so we can make a backup copy of the downloaded files.
+      tarballs. The download script is ran to get it out of the way at the
+      start so a backup copy of the downloaded files are on hand.
     </para>
 
Index: xsoft/other/rox-filer.xml
===================================================================
--- xsoft/other/rox-filer.xml	(revision 4abd884171526ea90cb93437c0b19ebcf70d7c18)
+++ xsoft/other/rox-filer.xml	(revision ec64d2804f88801eb4289d8dc5809ff87dc9a320)
@@ -210,9 +210,9 @@
 
       <para>
-        That works fine for mounting, but to unmount it we need to run the
-        command <command>fusermount -u ${MOUNTPOINT}</command>. You could set
+        That works fine for mounting, but to unmount it the
+        command <command>fusermount -u ${MOUNTPOINT}</command> is ran. You could set
         that as your default umount command in your rox preferences, but you
         would then be unable to unmount any normal mountpoints (that need
-        umount). What we need is a script that will unmount a Fuse mountpoint
+        umount). A script is needed that will unmount a Fuse mountpoint
         with <command>fusermount -u ${MOUNTPOINT}</command> and everything else
         with <command>umount</command>. As the
