fix typo's

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

appendixa/bin86-shortdesc.xml

@@ -2,7 +2,7 @@
 
 <para>Last checked against version &bin86-contversion;</para>
 
-<para>Bin86 is a simple assember and linker for 8086 - 80386 machine
+<para>Bin86 is a simple assembler and linker for 8086 - 80386 machine
   code.</para>
 
 <para>Bin86 installs the following:</para>

appendixa/makedev-shortdesc.xml

@@ -8,7 +8,7 @@ directory. Detailed information about device nodes may be found
 in the <filename>Documentation/devices.txt</filename> file under
 the Linux kernel source tree.</para>
 
-<para>MAKDEV installs the following:</para>
+<para>MAKEDEV installs the following:</para>
 
 <sect3><title>Program Files</title>
 <para>MAKEDEV</para></sect3>

appendixa/procps-shortdesc.xml

@@ -3,7 +3,7 @@
 <para>Last checked against version &procps-contversion;.</para>
 
 <para>The Procps package provides programs to monitor and
-hault system processes. Procps gathers information about
+halt system processes. Procps gathers information about
 processes via the <filename>/proc</filename> directory.</para>
 
 <para>Procps installs the following:</para>

appendixa/shellutils-shortdesc.xml

@@ -2,7 +2,7 @@
 
 <para>Last checked against version &sh-utils-contversion;.</para>
 
-<para>The sh-utils package contains a number of basic shell manipulation
+<para>The Sh-utils package contains a number of basic shell manipulation
 utilities.</para>
 
 <para>Sh-utils installs the following:</para>

chapter01/changelog.xml

@@ -195,7 +195,7 @@ warning about --enable-kernel.</para></listitem>
 
 <listitem><para>December 10th, 2002 [gerard]: Chapter 04 - Changed all
 links into Freshmeat.net project links, removed lfs-packages tarball. This
-was done because the LFS FTP achive won't contain the packages anymore,
+was done because the LFS FTP archive won't contain the packages anymore,
 instead you have to go to the package's download sites to get
 them.</para></listitem>
 

chapter05/bash-inst.xml

@@ -29,18 +29,19 @@ following command:</para>
 <para>The meaning of the configure options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--enable-static-link:</userinput> This option
+<listitem><para><userinput>--enable-static-link</userinput>: This option
 causes the <userinput>bash</userinput> program to be statically
 linked.</para></listitem>
 
-<listitem><para><userinput>--prefix=$LFS/static:</userinput> This option
-installs all of Bash's files under the $LFS/static directory, which becomes
-the /static directory when chroot'ed or reboot'ed into
-LFS.</para></listitem>
+<listitem><para><userinput>--prefix=$LFS/static</userinput>: This option
+installs all of Bash's files under the
+<filename class="directory">$LFS/static</filename> directory, which becomes
+the <filename class="directory">/static</filename> directory when chroot'ed
+or reboot'ed into LFS.</para></listitem>
 
-<listitem><para><userinput>--with-curses:</userinput> This option causes
-bash to be linked against the curses library instead of the default termcap
-library which is being phased out and has become obsolete. Note, on most
+<listitem><para><userinput>--with-curses</userinput>: This option causes
+<filename>bash</filename> to be linked against the curses library instead
+of the default termcap library which has become obsolete. Note, on most
 all Linux systems, the curses library is provided by the Ncurses
 package (so in truth we link against the ncurses library).</para>
 

chapter05/binutils-inst.xml

@@ -22,7 +22,7 @@ cd ../binutils-build</userinput></screen></para>
 <para>The meaning of the (new) configure switches are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--disable-nls:</userinput> This option disables
+<listitem><para><userinput>--disable-nls</userinput>: This option disables
 internationalization (also known as i18n). We don't need this for our
 static programs and nls often causes problems when you're linking
 statically.</para></listitem>
@@ -35,7 +35,7 @@ statically.</para></listitem>
 <para>The meaning of the make option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>make LDFLAGS="-all-static":</userinput> This is
+<listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This is
 how we tell Binutils that all programs should be statically linked. Setting
 the <emphasis>LDFLAGS</emphasis> variable is the common way of specifying we
 want a static link to take place, however, its value and the way it is set

chapter05/bzip2-inst.xml

@@ -13,7 +13,7 @@ environment:</para>
 <para>The meaning of the make option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>CC="gcc -static -s":</userinput> The Bzip2 package
+<listitem><para><userinput>CC="gcc -static -s"</userinput>: The Bzip2 package
 does not honour the <emphasis>LDFLAGS</emphasis> variable, so instead we set
 the <emphasis>CC</emphasis> variable which defines which compiler to use.
 The <emphasis>-static</emphasis> option tells the compiler to link all
@@ -27,7 +27,7 @@ programs statically.</para></listitem>
 <para>The meaning of the make option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>PREFIX=$LFS/static:</userinput> Instead of
+<listitem><para><userinput>PREFIX=$LFS/static</userinput>: Instead of
 passing a <emphasis>--prefix=$LFS/static</emphasis> to a configure script,
 we set the <emphasis>PREFIX</emphasis> variable to accomplish the same goal
 (since there is no configure script present).</para></listitem>

chapter05/diffutils-inst.xml

@@ -11,7 +11,7 @@
 <para>The meaning of the configure options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>LDFLAGS="-static":</userinput> This is the most
+<listitem><para><userinput>LDFLAGS="-static"</userinput>: This is the most
 common way to tell a package that all programs should be statically linked.
 This way the <emphasis>LDFLAGS</emphasis> environment variable is set, but
 only in the subshell that the <filename>configure</filename> script runs
@@ -20,9 +20,8 @@ in. When <userinput>configure</userinput> has done its job, the
 and the <filename>Makefile</filename> files contain will contain this
 variable locally.</para></listitem>
 
-<listitem><para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2:</userinput>
-The <emphasis>CPPFLAGS</emphasis> variable is a variable that's read by the
-cpp program (C PreProcessor). The value of this variable tells the
+<listitem><para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2</userinput>: The <emphasis>CPPFLAGS</emphasis> variable is a variable that's read by
+the cpp program (C PreProcessor). The value of this variable tells the
 preprocessor to replace every instance of <emphasis>re_max_failures</emphasis>
 it finds with <emphasis>re_max_failures2</emphasis> before handing the source
 file to the compiler itself for compilation. This package has problems

chapter05/gcc-inst.xml

@@ -28,19 +28,19 @@ cd ../gcc-build</userinput></screen></para>
 <para>The meaning of the configure options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--prefix=/static:</userinput> This is NOT a
+<listitem><para><userinput>--prefix=/static</userinput>: This is NOT a
 typo. GCC hard codes some paths while compiling and so we need to pass
 <filename class="directory">/static</filename> as the prefix during the
 configure stage. We will pass the real installation prefix (<filename
-class="directory">$LFS/static</filename> during the installation
+class="directory">$LFS/static</filename>) during the installation
 stage later on.</para></listitem>
 
-<listitem><para><userinput>--disable-shared:</userinput> This prevents the
+<listitem><para><userinput>--disable-shared</userinput>: This prevents the
 build of dynamic libraries. They are useless to us at the moment. We'll
 create them when we reinstall GCC in chapter 6.</para></listitem>
 
 <listitem><para><userinput>--with-as=$LFS/static/bin/as and
---with-ld=$LFS/static/bin/ld:</userinput> GCC can be miscompiled if your
+--with-ld=$LFS/static/bin/ld</userinput>: GCC can be miscompiled if your
 host distribution's Binutils package is quite old. We need a good working
 static GCC until we reinstall GCC later in chapter 6. So by using
 <filename>as</filename> and <filename>ld</filename> from the Binutils
@@ -55,14 +55,14 @@ correctly.</para></listitem>
 <para>The meaning of the make options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>BOOT_LDFLAGS="-static":</userinput> This is
+<listitem><para><userinput>BOOT_LDFLAGS="-static"</userinput>: This is
 GCC's equivalent to make LDFLAGS="-static" as we use with other packages to
 compile them statically.</para></listitem>
 
-<listitem><para><userinput>bootstrap:</userinput> The
+<listitem><para><userinput>bootstrap</userinput>: The
 <emphasis>bootstrap</emphasis> target doesn't just compile GCC, but it
 compiles GCC a second time. It uses the first compiled programs to compile
-itself a second and third time to make sure the compiler compiled properly
+itself a second and third time to make sure the compiler was compiled properly
 and can compile itself properly.</para></listitem>
 </itemizedlist>
 
@@ -73,7 +73,7 @@ and can compile itself properly.</para></listitem>
 <para>The meaning of the make option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>install-no-fixedincludes:</userinput> This prevents
+<listitem><para><userinput>install-no-fixedincludes</userinput>: This prevents
 the fixincludes script from running. Preventing this is necessary because
 under normal circumstances the GCC installation will run the fixincludes
 script which scans your system for header files that need to be fixed. It
@@ -95,8 +95,9 @@ class="symlink">$LFS/static/bin/cc</filename> symlink. A lot of programs
 and scripts try to run <userinput>cc</userinput> instead of
 <userinput>gcc</userinput> This is to keep programs generic and usable on
 all kinds of Unix systems. Not everybody has GNU CC installed. Just running
-cc (C Compiler) leaves the user free to decide which C compiler to install.
-The symlink will point to the system's default compiler.</para>
+<userinput>cc</userinput> (C Compiler) leaves the user free to decide which
+C compiler to install. The symlink will point to the system's default
+compiler.</para>
 
 <para><screen><userinput>ln -s gcc $LFS/static/bin/cc</userinput></screen></para>
 

chapter05/grep-inst.xml

@@ -12,10 +12,11 @@
 <para>The meaning of the configure option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--disable-perl-regexp:</userinput> This
-configure option makes sure Grep is not linked against the PCRE library,
-which is often only available as a shared library in distributions. Not
-using this option might result in a compilation error.</para></listitem>
+<listitem><para><userinput>--disable-perl-regexp</userinput>: This
+configure option makes sure <filename>grep</filename> is not linked against
+the PCRE library, which is often only available as a shared library in
+distributions. Not using this option might result in a compilation
+error.</para></listitem>
 </itemizedlist>
 
 <para>Continue with compiling the package:</para>

chapter05/make-inst.xml

@@ -22,10 +22,11 @@
 otherwise the `-l' option will probably not work. You may need special
 privileges to complete the installation of /mnt/lfs/static/bin/make.</screen></blockquote>
 
-<para>You can safely ignore this warning. The make program doesn't actually
-need to be owned by group kmem and setgid for the <emphasis>-l</emphasis>
-option to work. (This option tells make not to start any new jobs when a
-certain load on the system has been reached.)</para>
+<para>You can safely ignore this warning. The <userinput>make</userinput>
+program doesn't actually need to be owned by group kmem and setgid for the
+<emphasis>-l</emphasis> option to work. (This option tells
+<userinput>make</userinput> not to start any new jobs when a certain load
+on the system has been reached.)</para>
 
 </sect2>
 

chapter05/patch-inst.xml

@@ -11,7 +11,7 @@
 <para>The meaning of the configure option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>CPPFLAGS=-D_GNU_SOURCE:</userinput> This flag
+<listitem><para><userinput>CPPFLAGS=-D_GNU_SOURCE</userinput>: This flag
 fixes installation problems of this package on PPC and m68k platforms (that
 we know of). It doesn't hurt compilation on other platforms, such as x86,
 so we do it by default.</para></listitem>

chapter05/setting-environment.xml

@@ -21,8 +21,8 @@ Other users of the system will be have read permission, and executable
 permission to directories. It is advisable to keep this setting throughout
 your LFS installation.</para>
 
-<para>The LFS variable has been explained in previous chapters. LC_ALL is
-a variable used for internationalization.</para>
+<para>The LFS variable should of course be set to the mount point you
+chose.</para>
 
 <para>The LC_ALL variable controls the localization of certain programs,
 making their messages follow the conventions of a specified country. If your

chapter05/shellutils-inst.xml

@@ -29,9 +29,10 @@ it.</para>
 NOTE: to install su, run 'make install-root' as root</screen></blockquote>
 
 <para>You can safely ignore that warning. You need to be logged in as root
-in order to install su the way Sh-utils wants to install it, which is being
-suid root. Because we don't need su during Chapter 6, and su will be properly
-installed when we re-install Sh-utils in Chapter 6.</para>
+in order to install <filename>su</filename> the way Sh-utils wants to install
+it, which is suid root. Because we don't need <filename>su</filename> during
+Chapter 6, and <filename>su</filename> will be properly installed when we
+re-install Sh-utils in Chapter 6.</para>
 
 </sect2>
 

chapter05/utillinux-inst.xml

@@ -11,8 +11,8 @@
 
 <para><screen><userinput>make -C lib</userinput></screen></para>
 
-<para>We only need the <emphasis>mount</emphasis> and
-<emphasis>umount</emphasis> programs at the moment, so we won't be
+<para>We only need the <filename>mount</filename> and
+<filename>umount</filename> programs at the moment, so we won't be
 compiling the entire package. Compile these two programs by issuing
 the following command:</para>
 

chapter06/bzip2-inst.xml

@@ -23,7 +23,7 @@ against it.</para>
 
 <para>Copy the Bzip2 binary into the <filename
 class="directory">/bin</filename> directory, make some
-neccessary symbolic links and clean up.</para>
+necessary symbolic links and clean up.</para>
 
 <para><screen><userinput>cp bzip2-shared /bin/bzip2 &amp;&amp;
 cp -a libbz2.so* /lib &amp;&amp;

chapter06/config-shadowpwd.xml

@@ -9,7 +9,7 @@ file within the unpacked shadow password suite's source tree. There's one
 thing to keep in mind if you decide to use shadow support: programs that
 need to verify passwords (for example xdm, ftp daemons, pop3 daemons) need
 to be 'shadow-compliant', that is they need to be able to work with 
-hadowed passwords.</para>
+shadowed passwords.</para>
 
 <para>To enable shadowed passwords, run the following command:</para>
 

chapter06/e2fsprogs-inst.xml

@@ -18,7 +18,7 @@ cd ../e2fsprogs-build</userinput></screen></para>
 
 <itemizedlist>
 
-<listitem><para><userinput>--with-root-prefix="":</userinput> Certain
+<listitem><para><userinput>--with-root-prefix=""</userinput>: Certain
 programs (such as the e2fsck program) are considered essential programs.
 When, for example, <filename class="directory">/usr</filename> isn't
 mounted, these essential program have to be available. They belong in
@@ -28,7 +28,7 @@ to E2fsprogs's configure, the programs are placed in the
 <filename class="directory">/usr</filename> directory, which is not what we
 want.</para></listitem>
 
-<listitem><para><userinput>--enable-elf-shlibs:</userinput> This creates
+<listitem><para><userinput>--enable-elf-shlibs</userinput>: This creates
 the shared libraries which some programs in this package make use
 of.</para></listitem>
 

chapter06/gcc-inst.xml

@@ -30,14 +30,14 @@ cd ../gcc-build</userinput></screen></para>
 <para>The meanings of the configure options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--enable-threads=posix:</userinput> This enables
+<listitem><para><userinput>--enable-threads=posix</userinput>: This enables
 C++ exception handling for multi-threaded code.</para></listitem>
 
-<listitem><para><userinput>--enable-__cxa_atexit:</userinput> This option
+<listitem><para><userinput>--enable-__cxa_atexit</userinput>: This option
 will result in C++ shared libraries and C++ programs that are interoperable
 with other Linux distributions.</para></listitem>
 
-<listitem><para><userinput>--enable-clocale=gnu:</userinput> There is a risk
+<listitem><para><userinput>--enable-clocale=gnu</userinput>: There is a risk
 that some people will build ABI incompatible C++ libraries if they didn't
 install all of the glibc localedata. Using --enable-clocale=gnu ensures that
 the "right thing" is done in all cases. If you don't wish to use this option,

chapter06/glibc-inst.xml

@@ -81,14 +81,14 @@ cd ../glibc-build</userinput></screen></para>
 <para>The meaning of the configure options are:</para>
 
 <itemizedlist>
-<listitem><para><userinput>--disable-profile:</userinput> This disables the
+<listitem><para><userinput>--disable-profile</userinput>: This disables the
 building of libraries with profiling information. This command may be
 omitted if you plan to do profiling.</para></listitem>
 
-<listitem><para><userinput>--enable-add-ons:</userinput> This enables the
+<listitem><para><userinput>--enable-add-ons</userinput>: This enables the
 add-on that we install with Glibc, linuxthreads</para></listitem>
 
-<listitem><para><userinput>--libexecdir=/usr/bin:</userinput> This will
+<listitem><para><userinput>--libexecdir=/usr/bin</userinput>: This will
 cause the pt_chown program to be installed in the /usr/bin
 directory.</para></listitem>
 </itemizedlist>

chapter06/kernel-manpages.xml

@@ -1,6 +1,6 @@
 <sect1 id="ch06-kernel-manpages">
 <title>Installing Linux-&kernel-version; man pages</title>
-<?dbhtml filename="kernel-manpges.html" dir="chapter06"?>
+<?dbhtml filename="kernel-manpages.html" dir="chapter06"?>
 
 <screen>Estimated build time:           &kernel-manpages-time;
 Estimated required disk space:  &kernel-manpages-compsize;</screen>

chapter06/ncurses-inst.xml

@@ -24,7 +24,7 @@ where they're expected to reside:</para>
 
 <para><screen><userinput>mv /usr/lib/libncurses.so.5* /lib</userinput></screen></para>
 
-<para>Since the libaries have been moved to
+<para>Since the libraries have been moved to
 <filename>/lib</filename>, a few symlinks are currently pointing
 towards non-existing files. Recreate those symlinks:</para>
 

chapter06/nettools-inst.xml

@@ -20,7 +20,7 @@ it's up to the kernel to make them available to the system.</para>
 <para><screen><userinput>make</userinput></screen></para>
 
 <para>If you intend to accept the default settings, you may skip
-the questions generated by <emphasis>make</emphasis> by runing
+the questions generated by <emphasis>make</emphasis> by runnnnnnnnning
 <userinput>yes "" | make</userinput> instead.</para>
 
 <para>Finish installing the package:</para>

chapter06/vim-inst.xml

@@ -19,7 +19,7 @@ install it. This patch fixes a compile problem with GCC-3.2:</para>
 <para>The meaning of the make option is:</para>
 
 <itemizedlist>
-<listitem><para><userinput>CPPFLAGS=-DSYS_VIMRC_FILE=\\\"/etc/vimrc\\\":</userinput>
+<listitem><para><userinput>CPPFLAGS=-DSYS_VIMRC_FILE=\\\"/etc/vimrc\\\"</userinput>:
 This option above causes vim to look for the
 <filename>/etc/vimrc</filename> file which contains vim's global settings.
 Normally, this file is assumed to be located in <filename