Reprise of r6318.

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

chapter07/bootscripts.xml

@@ -80,8 +80,8 @@ sets the screen font</para>
 <varlistentry id="functions-bootscripts">
 <term><command>functions</command></term>
 <listitem>
-<para>Contains common functions that are used by several bootscripts, such as
-error and status checking</para>
+<para>Contains common functions, such as error and status checking, that are
+used by several bootscripts</para>
 <indexterm zone="ch-scripts-bootscripts functions-bootscripts"><primary sortas="d-functions">functions</primary></indexterm>
 </listitem>
 </varlistentry>

chapter07/console.xml

@@ -13,10 +13,9 @@
 
 <para>This section discusses how to configure the <command>console</command>
 bootscript that sets up the keyboard map and the console font. If non-ASCII
-characters (British pound and Euro character are examples of non-ASCII
-characters) will not be used and the keyboard is a U.S. one, skip this section.
-Without the configuration file, the <command>console</command> bootscript will
-do nothing.</para>
+characters (e.g., the British pound sign and Euro character) will not be used
+and the keyboard is a U.S. one, skip this section. Without the configuration
+file, the <command>console</command> bootscript will do nothing.</para>
 
 <para>The <command>console</command> script reads the
 <filename>/etc/sysconfig/console</filename> file for configuration information.

chapter07/network.xml

@@ -53,7 +53,7 @@ the network script will bring up the Network Interface Card (NIC) during booting
 of the system. If set to anything but <quote>yes</quote> the NIC will be ignored
 by the network script and not be brought up.</para>
 
-<para>The <envar>SERVICE</envar> variable defines the method used in obtaining
+<para>The <envar>SERVICE</envar> variable defines the method used for obtaining
 the IP address. The LFS-Bootscripts package has a modular IP assignment format,
 and creating additional files in the <filename
 class="directory">/etc/sysconfig/network-devices/services</filename> directory

chapter07/setclock.xml

@@ -17,11 +17,11 @@ clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
 hardware clock's time to the local time using the
 <filename>/etc/localtime</filename> file (which tells the
 <command>hwclock</command> program which timezone the user is in). There is no
-way to detect whether or not the hardware clock is set to UTC time, so this
+way to detect whether or not the hardware clock is set to UTC, so this
 needs to be configured manually.</para>
 
-<para>If you cannot remember whether or not the hardware clock is set to UTC
-time, find out by running the <userinput>hwclock --localtime --show</userinput>
+<para>If you cannot remember whether or not the hardware clock is set to UTC,
+find out by running the <userinput>hwclock --localtime --show</userinput>
 command. This will display what the current time is according to the hardware
 clock. If this time matches whatever your watch says, then the hardware clock is
 set to local time. If the output from <command>hwclock</command> is not local

chapter07/udev.xml

@@ -124,7 +124,7 @@ To solve this, the <command>S05modules</command> bootscript was added to the
 LFS-Bootscripts package, along with the
 <filename>/etc/sysconfig/modules</filename> file. By adding module names to the
 <filename>modules</filename> file, these modules will be loaded when the
-computer is starts up. This allows <command>udev</command> to detect the devices
+computer starts up. This allows <command>udev</command> to detect the devices
 and create the appropriate device nodes.</para>
 
 <para>Note that on slower machines or for drivers that create a lot

chapter07/usage.xml

@@ -18,7 +18,7 @@ particular Linux distribution, they should work the same in LFS too. LFS has its
 own way of doing things, but it respects generally accepted standards.</para>
 
 <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
-works using a run-levels scheme. There are seven (from 0 to 6) run-levels
+works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels
 (actually, there are more run-levels, but they are for special cases and are
 generally not used. The init manual page describes those details), and each one
 of those corresponds to the actions the computer is supposed to perform when it