fix some typos

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

chapter01/changelog.xml

@@ -389,7 +389,7 @@
           <para>[pierre] - Fix bash tests: add a couple of symlinks
           from /bin to /tools, create the tester user with the uid of
           the tty owner, run the bash tests with su &lt;&lt; EOF, and
-          explicitely defining stdin (with help from thomas and bdubbs).</para>
+          explicitly defining stdin (with help from thomas and bdubbs).</para>
         </listitem>
       </itemizedlist>
     </listitem>

chapter02/stages.xml

@@ -68,7 +68,7 @@
       <listitem>
         <para>A few operations, from <quote>Changing Ownership</quote> to
         <quote>Entering the Chroot Environment</quote> must be done as the
-        root user, with the LFS envirnment variable set for the root user.</para>
+        root user, with the LFS environment variable set for the root user.</para>
       </listitem>
 
       <listitem>

chapter04/settingenviron.xml

@@ -161,7 +161,7 @@ EOF</userinput></screen>
      <systemitem class="username">lfs</systemitem>
      user's environment in ways that can affect the building of critical LFS
      packages. To make sure the <systemitem class="username">lfs</systemitem>
-     user's envronment is clean, check for the
+     user's environment is clean, check for the
      presence of <filename>/etc/bash.bashrc</filename> and, if present, move it
      out of the way.  As the <systemitem class="username">root</systemitem>
      user, run:</para>

chapter06/bash.xml

@@ -74,7 +74,7 @@
 
 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
 
-    <para>Move the excutable to where it is expected:</para>
+    <para>Move the executable to where it is expected:</para>
 
 <screen><userinput remap="install">mv $LFS/usr/bin/bash $LFS/bin/bash</userinput></screen>
 

chapter06/findutils.xml

@@ -57,7 +57,7 @@
 
 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
 
-    <para>Move the excutable to its final expected location:</para>
+    <para>Move the executable to its final expected location:</para>
 
 <screen><userinput remap="install">mv -v $LFS/usr/bin/find $LFS/bin
 sed -i 's|find:=${BINDIR}|find:=/bin|' $LFS/usr/bin/updatedb</userinput></screen>

chapter06/gcc-pass2.xml

@@ -123,7 +123,7 @@ ln -s ../../../libgcc/gthr-posix.h $LFS_TGT/libgcc/gthr-default.h</userinput></s
         <listitem>
           <para>This option is automatically enabled when building a native
           compiler with a native compiler on x86. But here, we build with
-          a cross compiler, so we need to explicitely set this option.</para>
+          a cross compiler, so we need to explicitly set this option.</para>
         </listitem>
       </varlistentry>
 

chapter06/gzip.xml

@@ -55,7 +55,7 @@
 
 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
 
-    <para>Move the excutable to its final expected location:</para>
+    <para>Move the executable to its final expected location:</para>
 
 <screen><userinput remap="install">mv -v $LFS/usr/bin/gzip $LFS/bin</userinput></screen>
 

chapter06/introduction.xml

@@ -24,7 +24,7 @@
   <para>Once again, let us recall that improper setting of <envar>LFS</envar>
   together with building as root, may render your computer unusable.
   This whole chapter must be done as user <systemitem
-  class="username">lfs</systemitem>, with the enviroment as described in
+  class="username">lfs</systemitem>, with the environment as described in
   <xref linkend="ch-preps-settingenviron"/>.</para>
 
 </sect1>

chapter08/coreutils.xml

@@ -127,7 +127,7 @@ FORCE_UNSAFE_CONFIGURE=1 ./configure \
 
 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"</userinput></screen>
 
-    <para>The test-getlogin test is known to fail in the LFS chroot envronment.</para>
+    <para>The test-getlogin test is known to fail in the LFS chroot environment.</para>
 
     <para>Remove the temporary group:</para>
 

chapter08/revisedchroot.xml

@@ -50,7 +50,7 @@ rm -f /usr/lib/libfl.a
 rm -f /usr/lib/libz.a</userinput></screen>
 
   <para>There are also several files installed in the /usr/lib and /usr/libexec
-  directories with a file name extention of .la. These are "libtool archive"
+  directories with a file name extension of .la. These are "libtool archive"
   files. As already said, they are only useful when linking with static
   libraries. They are unneeded, and potentially harmful, when using dynamic
   shared libraries, specially when using also non-autotools build systems.

part3intro/toolchaintechnotes.xml

@@ -322,7 +322,7 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     configure script, <envar>CC_FOR_TARGET</envar> ends up as
     <command>cc</command> when the host is the same as the target, but is
     different from the build system. This is why
-    <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is put explicitely into
+    <parameter>CC_FOR_TARGET=$LFS_TGT-gcc</parameter> is put explicitly into
     the configure options.</para>
 
     <para>Upon entering the chroot environment in <xref