Removing some excess white space.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3186 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

appendixa/gettext-desc.xml

@@ -51,7 +51,7 @@ from a translation catalog.</para>
 <para><command>msggrep</command> extracts all messages of a translation
 catalog that match a given pattern or belong to some given source files.</para>
 
-<para><command>msginit</command> creates a new  <filename>.po</filename>
+<para><command>msginit</command> creates a new <filename>.po</filename>
 file, initializing the meta information with values from the user's
 environment.</para>
 

appendixa/groff-desc.xml

@@ -73,7 +73,7 @@ within troff or TeX input files into commands understood by TeX or troff.</para>
 <para><command>pic2graph</command> converts a PIC diagram into a cropped
 image.</para>
 
-<para><command>pre-grohtml </command> translates  the output of GNU troff
+<para><command>pre-grohtml </command> translates the output of GNU troff
 to html.</para>
 
 <para><command>post-grohtml</command> translates the output of GNU troff

appendixa/kernel-desc.xml

@@ -6,7 +6,7 @@ system that gets loaded. It detects and initializes all the components of your
 computer's hardware, then makes these components available as a tree of files
 to the software, and turns a single CPU into a multi-tasking machine capable
 of running scores of programs seemingly at the same time.</para>
-                                                            
+
 <para>The <emphasis>kernel headers</emphasis> define the interface to the
 services that the kernel provides. The headers in your system's
 <filename>include</filename> directory should <emphasis>always</emphasis> be

appendixa/modutils-desc.xml

@@ -1,7 +1,7 @@
 <sect2><title>Short descriptions</title>
 
 <para><command>depmod</command> creates a dependency file, based on the
-symbols it finds in the existing set of modules. This  dependency file is used
+symbols it finds in the existing set of modules. This dependency file is used
 by modprobe to automatically load the required modules.</para>
 
 <para><command>genksyms</command> generates symbol version information.</para>

appendixa/sysvinit-desc.xml

@@ -32,7 +32,7 @@ switch off the computer. But see halt.</para>
 But see halt.</para>
 
 <para><command>runlevel</command> reports the previous and the current
-runlevel, as noted in the last runlevel record  in
+runlevel, as noted in the last runlevel record in
 <filename>/var/run/utmp</filename>.</para>
 
 <para><command>shutdown</command> brings the system down in a secure way,
@@ -43,7 +43,7 @@ normally invoked by init when the system goes into single user mode.</para>
 
 <para><command>telinit</command> tells init which runlevel to enter.</para>
 
-<para><command>utmpdump</command> displays the content of  the given login
+<para><command>utmpdump</command> displays the content of the given login
 file in a friendlier format.</para>
 
 <para><command>wall</command> writes a message to all logged-in users.</para>

appendixb/appendixb.xml

@@ -5,7 +5,7 @@
 <para>This is a list of all the programs and library files that are
 installed in this book, each with a link to the package in Appendix A 
 to which it belongs.</para>
-  
+
 <itemizedlist>
 
 <listitem><para>a2p : <xref linkend="ch06-perl"/></para></listitem>
@@ -127,7 +127,7 @@ to which it belongs.</para>
 <listitem><para>elisp-comp : <xref linkend="ch06-automake"/></para></listitem>
 <listitem><para>elvtune : <xref linkend="ch06-util-linux"/></para></listitem>
 <listitem><para>env : <xref linkend="ch06-coreutils"/></para></listitem>
-<listitem><para>envsubst : <xref linkend="ch06-gettext"/></para></listitem>       
+<listitem><para>envsubst : <xref linkend="ch06-gettext"/></para></listitem>
 <listitem><para>enc2xs : <xref linkend="ch06-perl"/></para></listitem>
 <listitem><para>eqn : <xref linkend="ch06-groff"/></para></listitem>
 <listitem><para>e2n2graph : <xref linkend="ch06-groff"/></para></listitem>
@@ -294,7 +294,7 @@ to which it belongs.</para>
 <listitem><para>libncurses* : <xref linkend="ch06-ncurses"/></para></listitem>
 <listitem><para>libnetcfg : <xref linkend="ch06-perl"/></para></listitem>
 <listitem><para>libnsl : <xref linkend="ch06-glibc"/></para></listitem>
-<listitem><para>libnss*  : <xref linkend="ch06-glibc"/></para></listitem>
+<listitem><para>libnss* : <xref linkend="ch06-glibc"/></para></listitem>
 <listitem><para>libopcodes : <xref linkend="ch06-binutils"/></para></listitem>
 <listitem><para>libpanel : <xref linkend="ch06-ncurses"/></para></listitem>
 <listitem><para>libpcprofile : <xref linkend="ch06-glibc"/></para></listitem>
@@ -556,7 +556,7 @@ to which it belongs.</para>
 <listitem><para>swap : <xref linkend="ch06-lfs-bootscripts"/></para></listitem>
 <listitem><para>swapoff : <xref linkend="ch06-util-linux"/></para></listitem>
 <listitem><para>swapon : <xref linkend="ch06-util-linux"/></para></listitem>
-<listitem><para>symlink-tree : <xref linkend="ch06-automake"/></para></listitem>  
+<listitem><para>symlink-tree : <xref linkend="ch06-automake"/></para></listitem>
 <listitem><para>sync : <xref linkend="ch06-coreutils"/></para></listitem>
 <listitem><para>sysctl : <xref linkend="ch06-procps"/></para></listitem>
 <listitem><para>sysklogd : <xref linkend="ch06-lfs-bootscripts"/></para></listitem>

chapter01/how.xml

@@ -23,7 +23,7 @@ a compiler you need a compiler.</para>
 
 <para>The first thing to be done in <xref linkend="chapter05"/> is build a
 first pass of the toolchain, made up of Binutils and GCC. The programs from
-these  packages will be linked statically in order for them to be usable
+these packages will be linked statically in order for them to be usable
 independently of the host system. The second thing to do is build Glibc, the
 C library. Glibc will be compiled by the toolchain programs we just built in
 the first pass. The third thing to do is build a second pass of the toolchain.
@@ -40,7 +40,7 @@ is provided at the start of <xref linkend="chapter05"/>, including some notes
 on the differences between statically and dynamically linked programs.</para>
 
 <para>In <xref linkend="chapter06"/> your real LFS system will be built. The
-chroot (change root)  program is used to enter a virtual environment and start
+chroot (change root) program is used to enter a virtual environment and start
 a new shell whose root directory will be set to the LFS partition. This is very
 similar to rebooting and instructing the kernel to mount the LFS partition as
 the root partition. The reason that you don't actually reboot, but instead
@@ -54,7 +54,7 @@ would.</para>
 <para>To finish the installation, the bootscripts are set up in
 <xref linkend="chapter07"/>, the kernel and bootloader are set up in
 <xref linkend="chapter08"/>, and <xref linkend="chapter09"/> contains some
-pointers to help you after you finish the book.  Then, finally, you're ready to
+pointers to help you after you finish the book. Then, finally, you're ready to
 reboot your computer into your new LFS system.</para>
 
 <para>This is the process in a nutshell. Detailed information on the steps you 

chapter02/askforhelp.xml

@@ -39,7 +39,7 @@ help us to see other possible causes of your problem.)</para>
 <para>When something goes wrong during the stage where the configure script
 is run, look through the <filename>config.log</filename> file. This file
 may contain errors encountered during configure which weren't printed to
-the screen.  Include those relevant lines if you decide to ask for
+the screen. Include those relevant lines if you decide to ask for
 help.</para>
 
 </sect2>

chapter03/chapter03.xml

@@ -122,7 +122,7 @@ with the appropriate partition names.</para>
 
 <para>You should also ensure that this new partition is not mounted with
 permissions that are too restrictive (such as the nosuid, nodev or noatime
-options).  You can run the <userinput>mount</userinput> command without any
+options). You can run the <userinput>mount</userinput> command without any
 parameters to see with what options the LFS partition is mounted. If
 you see nosuid, nodev or noatime, you will need to remount it.</para>
  

chapter05/binutils-pass2.xml

@@ -54,7 +54,7 @@ should be easy to spot. The output shown will contain something like:</para>
 
 <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote>
 
-<para>And install the package:</para>                                              
+<para>And install the package:</para>
 
 <screen><userinput>make install</userinput></screen>
 

chapter05/chapter05.xml

@@ -308,7 +308,7 @@ the LFS partition).</para>
 <para>When logged in as <emphasis>root</emphasis>, making a single mistake
 can damage or even wreck your system. Therefore we recommend that you
 build the packages in this chapter as an unprivileged user. You could
-of course use your own user name,  but to make it easier to set up a clean
+of course use your own user name, but to make it easier to set up a clean
 work environment we'll create a new user <emphasis>lfs</emphasis> and
 use this one during the installation process. As <emphasis>root</emphasis>,
 issue the following commands to add the new user:</para>
@@ -382,7 +382,7 @@ export LFS LC_ALL PATH
 feature: <userinput>bash</userinput> uses a hash table to remember the
 full pathnames of executable files to avoid searching the PATH time and time
 again to find the same executable. However, we'd like the new tools to be
-used as soon as they are installed.  By switching off the hash function, our
+used as soon as they are installed. By switching off the hash function, our
 "interactive" commands (<userinput>make</userinput>,
 <userinput>patch</userinput>, <userinput>sed</userinput>,
 <userinput>cp</userinput> and so forth) will always use
@@ -400,7 +400,7 @@ making their messages follow the conventions of a specified country. If your
 host system uses a version of Glibc older than 2.2.4,
 having LC_ALL set to something other than "POSIX" or "C" during this chapter
 may cause trouble if you exit the chroot environment and wish to return later.
-By setting LC_ALL to "POSIX" (or "C", the two are equivalent)  we ensure that
+By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that
 everything will work as expected in the chroot environment.</para>
 
 <para>We prepend <filename>/tools/bin</filename> to the standard PATH so
@@ -454,7 +454,7 @@ Binutils build and source directories.</para>
 to the new dynamic linker. A simple sed will accomplish this:</para>
 
 <!-- Ampersands are needed to allow cut and paste -->
-   
+
 <screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs &amp;&amp;
 sed -e 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
 &nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE &gt; tempspecfile &amp;&amp;
@@ -476,7 +476,7 @@ name of your platform's dynamic linker in the above commands. Refer back to
 <para>Lastly, there is a possibility that some include files from the host
 system have found their way into GCC's private include dir. This can happen
 because of GCC's "fixincludes" process which runs as part of the GCC build.
-We'll explain more about this further on in this chapter.  For now, run the
+We'll explain more about this further on in this chapter. For now, run the
 following commands to eliminate this possibility:</para>
 
 <screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>

chapter05/gcc-pass1.xml

@@ -40,7 +40,7 @@ cd ../gcc-build</userinput></screen>
 <para>The meaning of the configure options:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--with-local-prefix=/tools</userinput>:  The
+<listitem><para><userinput>--with-local-prefix=/tools</userinput>: The
 purpose of this switch is to remove <filename>/usr/local/include</filename>
 from <userinput>gcc</userinput>'s include search path. This is not absolutely
 essential; however, we want to try to minimize the influence of the host

chapter05/gcc-pass2.xml

@@ -44,12 +44,12 @@ same working directory. They will all unfold into a single
 <screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch;
 patch -Np1 -i ../&gcc-specs-patch;</userinput></screen>
 
-<para>The first patch disables the GCC "fixincludes" script.  We mentioned this
+<para>The first patch disables the GCC "fixincludes" script. We mentioned this
 briefly earlier, but a slightly more in-depth explanation of the fixincludes 
-process is warranted here.  Under normal circumstances, the GCC fixincludes
-script scans your system for header files that need to be fixed.  It might find
+process is warranted here. Under normal circumstances, the GCC fixincludes
+script scans your system for header files that need to be fixed. It might find
 that some Glibc header files on your host system need to be fixed, fix them and
-put them in the GCC private include directory.  Then, later on in
+put them in the GCC private include directory. Then, later on in
 <xref linkend="chapter06"/>, after we've installed the newer Glibc, this
 private include directory would be searched before the system include
 directory, resulting in GCC finding the fixed headers from the host system,
@@ -159,7 +159,7 @@ usually aware of them but haven't yet gotten around to fixing them. In short,
 unless your results are vastly different from those at the above URL, it is safe
 to continue on.</para>
 
-<para>And finally install the package:</para>                                              
+<para>And finally install the package:</para>
 
 <screen><userinput>make install</userinput></screen>
 

chapter05/grep.xml

@@ -23,11 +23,11 @@ Estimated required disk space:  &grep-compsize-tools;</screen>
 <itemizedlist>
 <listitem><para><userinput>--disable-perl-regexp</userinput>: This makes sure
 that <userinput>grep</userinput> does not get linked against a PCRE library
-that may be present on the host, but would not be available once we enter the
+that may be present on the host and would not be available once we enter the
 chroot environment.</para></listitem>
 <listitem><para><userinput>--with-included-regex</userinput>: This ensures that
-Grep uses its internal regular expression code.  Without it, it will use
-the code from Glibc, which is known to be slightly buggy.</para></listitem>
+Grep uses its internal regular expression code. Without this switch, Grep will
+use the code from Glibc, which is known to be slightly buggy.</para></listitem>
 </itemizedlist>
 
 <para>Compile the programs:</para>

chapter05/utillinux.xml

@@ -14,7 +14,7 @@ Estimated required disk space:  &util-linux-compsize-tools;</screen>
 <title>Installation of Util-linux</title>
 
 <para>Util-linux doesn't use the freshly installed headers and libraries from
-the <filename>/tools</filename> directory.  This is fixed by altering the
+the <filename>/tools</filename> directory. This is fixed by altering the
 configure script:</para>
 
 <screen><userinput>cp configure configure.backup

chapter06/chapter06.xml

@@ -101,7 +101,7 @@ the chroot command.</para>
 
 <para>Notice that <filename class="directory">/tools/bin</filename> comes
 last in the PATH. This means that a temporary tool will not be used any more
-as soon as its final version is installed.  Well, at least when the shell
+as soon as its final version is installed. Well, at least when the shell
 doesn't remember the locations of executed binaries -- for this reason hashing
 is switched off by passing the <userinput>+h</userinput> option to
 <userinput>bash</userinput>.</para>

chapter06/coreutils.xml

@@ -53,7 +53,7 @@ makes some assumptions with regards to the presence of non-root users and
 groups that don't apply this early into the LFS build. We therefore create
 a dummy system user and two dummy groups to allow the tests to run
 properly. Should you choose not to run the test suite, skip down to
-"Install the package".  The following commands will prepare us for the test
+"Install the package". The following commands will prepare us for the test
 suite. Create two dummy groups and a dummy user name:</para>
 
 <screen><userinput>echo "dummy1:x:1000" >> /etc/group

chapter06/groff.xml

@@ -16,7 +16,7 @@ Estimated required disk space:  &groff-compsize;</screen>
 <title>Installation of Groff</title>
 
 <para>Groff expects the environment variable PAGE to contain the default paper
-size. For those in the United States, the command below is appropriate.  If you
+size. For those in the United States, the command below is appropriate. If you
 live elsewhere, you may want to change <emphasis>PAGE=letter</emphasis> to
 <emphasis>PAGE=A4</emphasis>.</para>
 

chapter06/ncurses.xml

@@ -3,7 +3,7 @@
 <?dbhtml filename="ncurses.html" dir="chapter06"?>
 
 <para>The Ncurses package contains libraries for the terminal-independent
-handling of character  screens.</para>
+handling of character screens.</para>
 
 <screen>Estimated build time:           &ncurses-time;
 Estimated required disk space:  &ncurses-compsize;</screen>

chapter06/procinfo.xml

@@ -22,7 +22,7 @@ Estimated required disk space:  &procinfo-compsize;</screen>
 <para>The meaning of the make parameter:</para>
 <itemizedlist>
 <listitem><para><userinput>LDLIBS=-lncurses</userinput>: This tells Procinfo
-to use the <filename>libncurses</filename> library instead of  the
+to use the <filename>libncurses</filename> library instead of the
 long-obsolete <filename>libtermcap</filename>.</para></listitem>
 </itemizedlist>
 

chapter08/grub.xml

@@ -97,7 +97,7 @@ wrong which can lead to problems in some circumstances. It's best to disable
 this functionality and let the kernel determine the amount of memory itself,
 hence the use of the <emphasis>--no-mem-option</emphasis> above.</para></note>
 
-<para>You may want to add an entry for your host distribution.  It might look
+<para>You may want to add an entry for your host distribution. It might look
 like this:</para>
 
 <screen><userinput>cat &gt;&gt; /boot/grub/menu.lst &lt;&lt; "EOF"</userinput>