Index: introduction/important/beyond.xml
===================================================================
--- introduction/important/beyond.xml	(revision cec675bd4c742f28ea43769fd562dfcf893b31f1)
+++ introduction/important/beyond.xml	(revision 24ca7aa4ad919fb6a85acc1a1e1953ca2ea70d83)
@@ -17,10 +17,10 @@
 
   <para>The packages that are installed in this book are only the tip of the
-  iceberg. We hope that the experience you gained with the LFS book and 
-  the BLFS book will give you the background needed to compile, install 
+  iceberg. We hope that the experience you gained with the LFS book and
+  the BLFS book will give you the background needed to compile, install
   and configure packages that are not included in this book.</para>
 
   <para>When you want to install a package to a location other than
-  <filename class='directory'>/</filename>, or 
+  <filename class='directory'>/</filename>, or
   <filename class='directory'>/usr</filename>, you are installing
   outside the default environment settings on most machines.  The following
@@ -35,5 +35,5 @@
     </listitem>
     <listitem>
-      <para>Expand the <envar>PATH</envar> for 
+      <para>Expand the <envar>PATH</envar> for
       <systemitem class="username">root</systemitem> to include
       <filename class='directory'>$PREFIX/sbin</filename>.</para>
@@ -62,6 +62,6 @@
     </listitem>
     <listitem>
-      <para>Add <filename class='directory'>$PREFIX/include</filename> to 
-      <envar>CPPFLAGS</envar> when compiling packages that depend on 
+      <para>Add <filename class='directory'>$PREFIX/include</filename> to
+      <envar>CPPFLAGS</envar> when compiling packages that depend on
       the package you installed.</para>
     </listitem>
@@ -81,7 +81,7 @@
     </listitem>
     <listitem>
-      <para>If you know the name of the executable, but not the package 
-      that the executable belongs to, first try a google search with the name of the 
-      executable. If the results are overwhelming, try searching for the given 
+      <para>If you know the name of the executable, but not the package
+      that the executable belongs to, first try a google search with the name of the
+      executable. If the results are overwhelming, try searching for the given
       executable in the Debian repository at
       <ulink url="http://www.debian.org/distrib/packages#search_contents"/>.</para>
@@ -95,5 +95,5 @@
       <para>Many of the newer packages follow the <command>./configure
       &amp;&amp; make &amp;&amp; make install</command> process.
-      Help on the options accepted by configure can be obtained via the 
+      Help on the options accepted by configure can be obtained via the
       command <command>./configure --help</command>.</para>
     </listitem>
@@ -114,8 +114,8 @@
   <tip>
     <para>If you have found a package that is only available in .deb or .rpm
-    format, there are two small scripts, <command>rpm2targz</command> and 
-    <command>deb2targz</command> that are available at 
-    <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and 
-    <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 
+    format, there are two small scripts, <command>rpm2targz</command> and
+    <command>deb2targz</command> that are available at
+    <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and
+    <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives
     into a simple <filename>tar.gz</filename> format.</para>
   </tip>
Index: introduction/important/bootscripts.xml
===================================================================
--- introduction/important/bootscripts.xml	(revision cec675bd4c742f28ea43769fd562dfcf893b31f1)
+++ introduction/important/bootscripts.xml	(revision 24ca7aa4ad919fb6a85acc1a1e1953ca2ea70d83)
@@ -24,9 +24,9 @@
   </indexterm>
 
-  <para>The BLFS Bootscripts package contains the init 
-  scripts that are used throughout the book. It is assumed that you will be 
-  using the blfs-bootscripts package in conjuction with a compatible 
-  lfs-bootscripts package. Refer to 
-  <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more 
+  <para>The BLFS Bootscripts package contains the init
+  scripts that are used throughout the book. It is assumed that you will be
+  using the blfs-bootscripts package in conjuction with a compatible
+  lfs-bootscripts package. Refer to
+  <ulink url="&lfs-root;/chapter07/bootscripts.html"/> for more
   information on the lfs-bootscripts package.</para>
 
@@ -38,13 +38,13 @@
   </itemizedlist>
 
-  <para>The blfs-bootscripts package will be used throughout the BLFS book 
-  for startup scripts.  Unlike LFS, each init script has a separate install target 
-  in the blfs-bootscripts package. It is recomended you keep the package source 
-  directory around until completion of your BLFS system. When a script is 
-  requested from blfs-bootscripts, simply change to the directory and as the 
-  <systemitem class="username">root</systemitem> user, execute the given 
+  <para>The blfs-bootscripts package will be used throughout the BLFS book
+  for startup scripts.  Unlike LFS, each init script has a separate install target
+  in the blfs-bootscripts package. It is recomended you keep the package source
+  directory around until completion of your BLFS system. When a script is
+  requested from blfs-bootscripts, simply change to the directory and as the
+  <systemitem class="username">root</systemitem> user, execute the given
   <command>make install-<replaceable>[init-script]</replaceable></command>
-  command. This command installs the init script to its proper location (along 
-  with any auxillary configuration scripts) and also creates the appropriate 
+  command. This command installs the init script to its proper location (along
+  with any auxillary configuration scripts) and also creates the appropriate
   symlinks to start and stop the service at the appropriate run-level.</para>
 
Index: introduction/important/patches.xml
===================================================================
--- introduction/important/patches.xml	(revision cec675bd4c742f28ea43769fd562dfcf893b31f1)
+++ introduction/important/patches.xml	(revision 24ca7aa4ad919fb6a85acc1a1e1953ca2ea70d83)
@@ -33,8 +33,8 @@
   </itemizedlist>
 
-  <para>In short, the book only includes patches that are either required or 
-  recommended. There is a 
+  <para>In short, the book only includes patches that are either required or
+  recommended. There is a
   <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
-  which hosts various patches (including the patches referenced in the books) 
+  which hosts various patches (including the patches referenced in the books)
   to enable you to configure your LFS the way you like it.</para>
 
Index: introduction/important/pkgmgt.xml
===================================================================
--- introduction/important/pkgmgt.xml	(revision cec675bd4c742f28ea43769fd562dfcf893b31f1)
+++ introduction/important/pkgmgt.xml	(revision 24ca7aa4ad919fb6a85acc1a1e1953ca2ea70d83)
@@ -48,7 +48,7 @@
     <title>Upgrade Issues</title>
 
-    <para>A Package Manager makes it easy to upgrade to newer versions when 
-    they are released. Generally the instructions in the LFS and BLFS Book can be 
-    used to upgrade to the newer versions. Here are some points that you should 
+    <para>A Package Manager makes it easy to upgrade to newer versions when
+    they are released. Generally the instructions in the LFS and BLFS Book can be
+    used to upgrade to the newer versions. Here are some points that you should
     be aware of when upgrading packages, especially on a running system.</para>
 
@@ -78,5 +78,5 @@
       </listitem>
       <listitem>
-        <para>If you are upgrading a running system, be on the lookout for packages 
+        <para>If you are upgrading a running system, be on the lookout for packages
         that use <command>cp</command> instead of <command>install</command>
         to install files. The latter command is usually safer if the executable or library
@@ -134,11 +134,11 @@
 
       <para>The installation needs to be faked, so that the package thinks that it is
-      installed in <filename class="directory">/usr</filename> though in reality it is 
-      installed in <filename class="directory">/usr/pkg</filename> hierarchy. 
-      Installing in this manner is not usually a trivial task. For example, consider 
-      that you are installing a package libfoo-1.1. The following instructions may 
+      installed in <filename class="directory">/usr</filename> though in reality it is
+      installed in <filename class="directory">/usr/pkg</filename> hierarchy.
+      Installing in this manner is not usually a trivial task. For example, consider
+      that you are installing a package libfoo-1.1. The following instructions may
       not install the package properly:</para>
 
-<screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1 
+<screen><userinput>./configure --prefix=/usr/pkg/libfoo/1.1
 make
 make install</userinput></screen>
@@ -211,9 +211,9 @@
       <title>User Based Management</title>
 
-      <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann, 
-      and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints 
-      Project</ulink>. In this scheme, each package is installed as a separate user 
-      into the standard locations. Files belonging to a package are easily identified 
-      by checking the user id. The features and shortcomings of this approach are 
+      <para>This scheme, that is unique to LFS, was devised by Matthias Benkmann,
+      and is available from the <ulink url="http://www.linuxfromscratch.org/hints/">Hints
+      Project</ulink>. In this scheme, each package is installed as a separate user
+      into the standard locations. Files belonging to a package are easily identified
+      by checking the user id. The features and shortcomings of this approach are
       too complex to describe in this section. For the details please see the hint at <ulink
       url="http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt"/>.</para>
Index: introduction/important/position.xml
===================================================================
--- introduction/important/position.xml	(revision cec675bd4c742f28ea43769fd562dfcf893b31f1)
+++ introduction/important/position.xml	(revision 24ca7aa4ad919fb6a85acc1a1e1953ca2ea70d83)
@@ -22,19 +22,19 @@
   LFS based system.</para>
 
-  <para>In traditional Unix systems, <filename>/usr</filename> usually 
+  <para>In traditional Unix systems, <filename>/usr</filename> usually
   contains files that come with the system distribution, and the <filename>
-  /usr/local</filename> tree is free for the local administrator to manage. 
-  The only really hard and fast rule is that Unix distributions should not 
-  touch <filename>/usr/local</filename>, except perhaps to create the basic 
+  /usr/local</filename> tree is free for the local administrator to manage.
+  The only really hard and fast rule is that Unix distributions should not
+  touch <filename>/usr/local</filename>, except perhaps to create the basic
   directories within it.</para>
 
   <para>With Linux distributions, like Red Hat, Debian etc. a possible rule is
-  that <filename>/usr</filename> is managed by the distribution's 
-  package system and <filename>/usr/local</filename> is not.  This way the 
+  that <filename>/usr</filename> is managed by the distribution's
+  package system and <filename>/usr/local</filename> is not.  This way the
   package manager's database knows about every file within
   <filename>/usr</filename>.</para>
 
-  <para>LFS users build their own system and so deciding where 
-  the system ends and local files begin is not straightforward.  So the choice 
+  <para>LFS users build their own system and so deciding where
+  the system ends and local files begin is not straightforward.  So the choice
   should be made in order to make things easier to administer.  There are several
   reasons for dividing files between <filename>/usr</filename> and
@@ -43,26 +43,26 @@
   <itemizedlist>
     <listitem>
-      <para>On a network of several machines all running LFS, 
-      or mixed LFS and other Linux distributions, 
+      <para>On a network of several machines all running LFS,
+      or mixed LFS and other Linux distributions,
       <filename>/usr/local</filename> could be used to hold packages
       that are common between all the computers in the network.  It can be
-      NFS mounted or mirrored from a single server.  Here local 
+      NFS mounted or mirrored from a single server.  Here local
       indicates local to the site.</para>
     </listitem>
     <listitem>
-      <para>On a network of several computers all running an identical 
-      LFS system <filename>/usr/local</filename> could hold 
-      packages that are different between the machines.  In this case local refers 
+      <para>On a network of several computers all running an identical
+      LFS system <filename>/usr/local</filename> could hold
+      packages that are different between the machines.  In this case local refers
       to the individual computers.</para>
     </listitem>
     <listitem>
-      <para>Even on a single computer <filename>/usr/local</filename> can 
-      be useful if you have several distributions installed simultaneously, and want 
+      <para>Even on a single computer <filename>/usr/local</filename> can
+      be useful if you have several distributions installed simultaneously, and want
       a place to put packages that will be the same on all of them.</para>
     </listitem>
     <listitem>
-      <para>Or you might regularly rebuild your LFS, but 
-      want a place to put files that you don't want to rebuild each time.  This way 
-      you can wipe the LFS file system and start from a clean 
+      <para>Or you might regularly rebuild your LFS, but
+      want a place to put files that you don't want to rebuild each time.  This way
+      you can wipe the LFS file system and start from a clean
       partition every time without losing everything.</para>
     </listitem>
@@ -72,9 +72,9 @@
   /usr/site</filename>, rather than <filename>/usr/local</filename>?</para>
 
-  <para>There is nothing stopping you, many sites do make their own trees, 
+  <para>There is nothing stopping you, many sites do make their own trees,
   however it makes installing new software more difficult.  Automatic installers
   often look for dependencies in <filename>/usr</filename> and
   <filename>/usr/local</filename>, and if the file it is looking
-  for is in <filename>/usr/site</filename> instead, the installer will 
+  for is in <filename>/usr/site</filename> instead, the installer will
   probably fail unless you specifically tell it where to look.</para>
 
