[Clfs-commits] commit: r4054 - /trunk/BOOK/chroot/x86/before-chroot.xml

[svn at cross-lfs.org]

Author: chris at beaker67.com
Date: Wed Oct 15 18:47:17 2008
New Revision: 4054

Log:
Text cleanup on the before-chroot page

Modified:
    trunk/BOOK/chroot/x86/before-chroot.xml

Modified: trunk/BOOK/chroot/x86/before-chroot.xml
==============================================================================
--- trunk/BOOK/chroot/x86/before-chroot.xml (original)
+++ trunk/BOOK/chroot/x86/before-chroot.xml Wed Oct 15 18:47:17 2008
@@ -14,25 +14,25 @@
 
     <para>Before we can enter the chroot we have to make sure that the system is
     in the proper state. From this point on the <envar>${CLFS_TARGET}</envar>
-    enviornment variable will no longer exist, so it will have no bearing on the
-    rest of the book. From this point on, most packages will rely on
+    environment variable will no longer exist, so it will have no bearing on the
+    rest of the book - most packages will rely on
     <command>config.guess</command> provided by
     <xref linkend="ch-system-automake"/>. Packages that do not use autotools
-    either do not care about the target triplet, or they have their own means
-    of determining it's value.</para>
+    either do not care about the target triplet, or have their own means
+    of determining its value.</para>
 
-    <para>In both cases, The information about the host cpu used to determine
+    <para>In both cases, the information about the host cpu used to determine
     the target triplet is gathered from the same place,
     <command>uname -m</command>. Executing this command outside of the chroot
-    aswell as inside the chroot will have the exact same output.</para>
+    as well as inside the chroot will have the exact same output.</para>
 
-   <para>If you're unsure if you're host and target have the same target
-    triplet, you can use this test to determine what the hosts target triplet
+   <para>If you're unsure if your host and target have the same target
+    triplet, you can use this test to determine what the host's target triplet
     is and if you need to take any steps to ensure that you don't build for the
     wrong architecture. Extract the <xref linkend="ch-system-automake"/> tarball
     and <command>cd</command> into the created directory. Then execute the
-    following to see what they detected target triplet is by
-    <command>config.guess</command>.</para>
+    following to see what the detected target triplet is by
+    <command>config.guess</command>:</para>
 
 <screen><userinput>lib/config.guess</userinput></screen>
 
@@ -51,7 +51,7 @@
     ever output i686. It is not possible to get an output of i486 or i586.</para>
 
     <para>To test if setarch does everything you need it to, execute the
-    following command from inside of the <xref linkend="ch-system-automake"/>
+    following command from inside the <xref linkend="ch-system-automake"/>
     directory:</para>
 
 <screen><userinput>setarch linux32 lib/config.guess</userinput></screen>
@@ -94,7 +94,7 @@
 
     <para os="uuc">Extract the tarball and <command>cd</command> into the
     created directory. To build the Uname Hack you must have the kernel sources
-    for you currently running kernel available. Build the Uname Hack with the
+    for your currently running kernel available. Build the Uname Hack with the
     following or similar command:</para>
 
 <screen os="uud"><userinput>make uname_hack_fake_machine=i486</userinput></screen>
@@ -106,29 +106,29 @@
         <term><parameter>uname_hack_fake_machine=i486</parameter></term>
         <listitem>
           <para>This parameter sets the value that the uts machine type will be
-          changed to. Alternativley this could be set to i586 or i686.</para>
+          changed to. Alternatively this could be set to i586 or i686.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para os="uuf">In the top level directory of the Uname Hack pacakage you
-    should see a file named uname_hack.ko. As soon as that module is loaded
-    into the running kernel the output of <command>uname -m</command> will be
-    affected immediately system-wide. Load the kernel module with the following
-    command:</para>
+    <para os="uuf">In the top level directory of the Uname Hack package you
+    should see a file named <filename>uname_hack.ko</filename>. As soon as
+    that module is loaded into the running kernel the output of
+    <command>uname -m</command> will be affected immediately system-wide.
+    Load the kernel module with the following command:</para>
 
 <screen os="uug"><userinput>insmod uname_hack.ko</userinput></screen>
 
     <para os="uuh">To test if the Uname Hack is working properly, execute the
-    following command from inside of the <xref linkend="ch-system-automake"/>
+    following command from inside the <xref linkend="ch-system-automake"/>
     directory:</para>
 
 <screen os="uui"><userinput>lib/config.guess</userinput></screen>
 
     <para os="uuj">The output of the above command should be the same as the
-    <envar>${CLFS_TARGET}</envar> enviornment variable. If this is not the
-    case, You can try and get help on the CLFS Support Mailing List or the
+    <envar>${CLFS_TARGET}</envar> environment variable. If this is not the
+    case, you can try and get help on the CLFS Support Mailing List or the
     IRC Channel. See <xref linkend="ch-intro-askforhelp"/> for more
     information.</para>