Changes in chapter04/settingenviron.xml [4e26453:aa9ade1]

File:

• chapter04/settingenviron.xml (modified) (9 diffs)

chapter04/settingenviron.xml

@@ -20 +20 @@
 EOF</userinput></screen>
 
-  <para>When logged on as user <systemitem class="username">lfs</systemitem>,
-  or when switched to the &lfs-user; user using an <command>su</command> command
-  with the <quote><parameter>-</parameter></quote> option,
+  <para>When logged on as user <systemitem class="username">lfs</systemitem>
+  or switched to the &lfs-user; user using a <command>su</command> command
+  with <quote><parameter>-</parameter></quote> option,
   the initial shell is a <emphasis>login</emphasis> shell which reads
   the <filename>/etc/profile</filename> of the host (probably containing some
@@ -31 +31 @@
   <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no
   unwanted and potentially hazardous environment variables from the host system
-  leak into the build environment.</para>
+  leak into the build environment. The technique used here achieves the goal of
+  ensuring a clean environment.</para>
 
   <para>The new instance of the shell is a <emphasis>non-login</emphasis>
@@ -100 +101 @@
   Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote>
   (the two are equivalent) ensures that everything will work as expected in
-  the cross-compilation environment.</para>
+  the chroot environment.</para>
       </listitem>
     </varlistentry>
@@ -108 +109 @@
       <listitem>
   <para>The <envar>LFS_TGT</envar> variable sets a non-default, but compatible machine
-  description for use when building our cross-compiler and linker and when
-  cross-compiling our temporary toolchain. More information is provided by
+  description for use when building our cross compiler and linker and when cross
+  compiling our temporary toolchain. More information is contained in
   <xref linkend="ch-tools-toolchaintechnotes" role=""/>.</para>
       </listitem>
@@ -132 +133 @@
       <listitem>
   <para>If <filename class="directory">/bin</filename> is not a symbolic
-  link, it must be added to the <envar>PATH</envar> variable.</para>
+  link, then it has to be added to the <envar>PATH</envar> variable.</para>
       </listitem>
     </varlistentry>
@@ -163 +164 @@
       <term><parameter>export ...</parameter></term>
       <listitem>
-        <para>While the preceding commands have set some variables, in order
+        <para>While the above commands have set some variables, in order
         to make them visible within any sub-shells, we export them.</para>
       </listitem>
@@ -172 +173 @@
   <important>
 
-     <para>Several commercial distributions add an undocumented instantiation
+     <para>Several commercial distributions add a non-documented instantiation
      of <filename>/etc/bash.bashrc</filename> to the initialization of
      <command>bash</command>. This file has the potential to modify the
@@ -185 +186 @@
      <screen role="nodump"><userinput>[ ! -e /etc/bash.bashrc ] || mv -v /etc/bash.bashrc /etc/bash.bashrc.NOUSE</userinput></screen>
 
-     <para>When the <systemitem class="username">lfs</systemitem>
-     user is no longer needed (at the beginning of <xref
-     linkend="chapter-chroot-temporary-tools"/>), you may safely restore
+     <para>After use of the <systemitem class="username">lfs</systemitem>
+     user is finished at the beginning of <xref
+     linkend="chapter-chroot-temporary-tools"/>, you can restore
      <filename>/etc/bash.bashrc</filename> (if desired).</para>
 
@@ -196 +197 @@
   </important>
 
-  <para>Finally, to ensure the environment is fully prepared for building the
+  <para>Finally, to have the environment fully prepared for building the
   temporary tools, force the <command>bash</command> shell to read
   the new user profile:</para>