Index: chapter09/etcshells.xml
===================================================================
--- chapter09/etcshells.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/etcshells.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -24,5 +24,5 @@
   login shells on the system. Applications use this file to determine
   whether a shell is valid. For each shell a single line should be
-  present, consisting of the shell's path, relative to the root of the
+  present, consisting of the shell's path relative to the root of the
   directory structure (/).</para>
 
Index: chapter09/inputrc.xml
===================================================================
--- chapter09/inputrc.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/inputrc.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -16,12 +16,12 @@
 
   <para>The <filename>inputrc</filename> file is the configuration file for
-  the Readline library, which provides editing capabilities while the user is
+  the readline library, which provides editing capabilities while the user is
   entering  a line from the terminal. It works by translating keyboard inputs
-  into specific actions.  Readline is used by Bash and most other shells as
+  into specific actions.  Readline is used by bash and most other shells as
   well as many other applications.</para>
 
   <para>Most people do not need user-specific functionality so the command
   below creates a global <filename>/etc/inputrc</filename> used by everyone who
-  logs in. If you later decide you need to override the defaults on a per-user
+  logs in. If you later decide you need to override the defaults on a per user
   basis, you can create a <filename>.inputrc</filename> file in the user's home
   directory with the modified mappings.</para>
Index: chapter09/introduction.xml
===================================================================
--- chapter09/introduction.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/introduction.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -19,10 +19,4 @@
     order but, at the same time, be executed as fast as possible.</para>
 
-<!--    <para>In the packages that were installed in Chapter&nbsp;6, there were two
-    different boot systems installed.  LFS provides the ability to easily
-    select which system the user wants to use and to compare and contrast the
-    two systems by actually running each system on the local computer.  The
-    advantages and disadvantages of these systems is presented below.</para>-->
-
   <sect2 id='sysv-desc'>
     <title>System V</title>
@@ -40,6 +34,5 @@
     can be run by the user:</para>
 
-<literallayout>
-0 &mdash; halt
+<literallayout>0 &mdash; halt
 1 &mdash; Single user mode
 2 &mdash; Multiuser, without networking
@@ -47,6 +40,5 @@
 4 &mdash; User definable
 5 &mdash; Full multiuser mode with display manager
-6 &mdash; reboot
-</literallayout>
+6 &mdash; reboot</literallayout>
 
     <para>The usual default run level is 3 or 5.</para>
@@ -70,5 +62,5 @@
     <itemizedlist>
       <listitem>
-          <para>Slower to boot.  A medium speed base LFS system 
+          <para>May be slower to boot.  A medium speed base LFS system 
           takes 8-12 seconds where the boot time is measured from the 
           first kernel message to the login prompt.  Network 
@@ -95,131 +87,5 @@
 
   </sect2>
-<!--
-  <sect2 id='sysd-desc'>
-    <title>Systemd</title>
 
-    <para>Systemd is a group of interconnected programs that handles system and
-    individual process requests.  It provides a dependency system between
-    various entities called "units".  It automatically addresses dependencies
-    between units and can execute several startup tasks in parallel.  It
-    provides login, inetd, logging, time, and networking services. </para>
+</sect1>
 
-    <bridgehead renderas="sect3">Advantages</bridgehead>
-
-    <itemizedlist>
-      <listitem>
-          <para>Used on many established distributions by default.</para>
-      </listitem>
-
-      <listitem>
-          <para>There is extensive documentation. 
-          See <ulink url="http://www.freedesktop.org/wiki/Software/systemd/"/>.</para>
-      </listitem>
-
-      <listitem>
-          <para>Parallel execution of boot processes. A medium speed
-          base LFS system takes 6-10 seconds from kernel start to a 
-          login prompt.  Network connectivity is typically established 
-          about 2 seconds after the login prompt.  More complex startup
-          procedures may show a greater speedup when compared to System V.</para>
-      </listitem>
-
-      <listitem>
-          <para>Implements advanced features such as control groups to 
-          manage related processes.</para>
-      </listitem>
-
-      <listitem>
-          <para>Maintains backward compatibility with System V programs 
-          and scripts.</para>
-      </listitem>
-    </itemizedlist>
-
-    <bridgehead renderas="sect3">Disadvantages</bridgehead>
-
-    <itemizedlist>
-      <listitem>
-          <para>There is a substantial learning curve.</para>
-      </listitem>
-
-      <listitem>
-          <para>Some advanced features such as dbus or cgroups cannot be
-          disabled if they are not otherwise needed.</para>
-      </listitem>
-
-      <listitem>
-          <para>Although implemented as several executable programs
-          the user cannot choose to implement only the portions desired.</para>
-      </listitem>
-
-      <listitem>
-          <para>Due to the nature of using compiled programs, systemd is
-          more difficult to debug.</para>
-      </listitem>
-
-      <listitem>
-          <para>Logging is done in a binary format.  Extra tools must
-          be used to process logs or additional processes must be implemented
-          to duplicate traditional logging programs.</para>
-      </listitem>
-
-    </itemizedlist>
-
-  </sect2>
--->
-<!--
-  <sect2 id='sysv'>
-    <title>Selecting a Boot Method</title>
-
-    <para>Selecting a boot method in LFS is relatively easy.  
-    Both systems are installed side-by-side.  The only task needed is to
-    ensure the files that are needed by the system have the correct names.
-    The following scripts do that.</para>
-
-<screen><userinput remap="install">cat &gt; /usr/sbin/set-systemd &lt;&lt; "EOF"
-#! /bin/bash
-
-ln -svfn init-systemd   /sbin/init
-ln -svfn init.d-systemd /etc/init.d
-
-for tool in halt poweroff reboot runlevel shutdown telinit; do
-  ln -sfvn  ${tool}-systemd   /sbin/${tool}
-  ln -svfn  ${tool}-systemd.8 /usr/share/man/man8/${tool}.8
-done
-
-echo "Now reboot with /sbin/reboot-sysv"
-EOF
-
-chmod 0744 /usr/sbin/set-systemd
-
-cat &gt; /usr/sbin/set-sysv &lt;&lt; "EOF"
-#! /bin/bash
-
-ln -sfvn init-sysv    /sbin/init
-ln -svfn init.d-sysv  /etc/init.d
-
-for tool in halt poweroff reboot runlevel shutdown telinit; do
-  ln -sfvn  ${tool}-sysv   /sbin/${tool}
-  ln -svfn  ${tool}-sysv.8 /usr/share/man/man8/${tool}.8
-done
-
-echo "Now reboot with /sbin/reboot-systemd"
-EOF
-
-chmod 0744 /usr/sbin/set-sysv</userinput></screen>
-
-  <note><para>The comment about the correct command to reboot in the 
-  above scripts is correct.  The reboot command for the current boot
-  system must be used after the script changes the default reboot command.
-  </para></note>
-
-  <para>Now set the desired boot system.  The default is System V:</para>
-
-<screen><userinput remap="install">/usr/sbin/set-sysv</userinput></screen>
-
-  <para>Changing the boot system can be done at any time by running the 
-  appropriate script above and rebooting.</para>
-
-  </sect2>
--->
-</sect1>
Index: chapter09/network.xml
===================================================================
--- chapter09/network.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/network.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -14,15 +14,5 @@
     <primary sortas="d-network">network</primary>
   <secondary>configuring</secondary></indexterm>
-<!--
-  <para>This section only applies if a network card is to be
-  configured.</para>
-
-  <para>If a network card will not be used, there is likely no need to create
-  any configuration files relating to network cards. If that is the case, you
-  will need to remove the <filename class="symlink">network</filename> symlinks
-  from all run-level directories (<filename
-  class="directory">/etc/rc.d/rc*.d</filename>) after the bootscripts are
-  installed in <xref linkend="ch-config-bootscripts"/>.</para>
--->
+
   <sect2>
     <title>Creating Network Interface Configuration Files</title>
@@ -38,5 +28,5 @@
     the filename be <emphasis>ifconfig</emphasis>.</para>
 
-    <note><para>If the procedure in the previous section was not used, Udev
+    <note><para>If the procedure in the previous section was not used, udev
     will assign network card interface names based on system physical
     characteristics such as enp2s1. If you are not sure what your interface
@@ -65,5 +55,5 @@
     <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the
     System V 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
+    the system boot process. If set to anything but <quote>yes</quote> the NIC
     will be ignored by the network script and not be automatically brought up.
     The interface can be manually started or stopped with the
Index: chapter09/profile.xml
===================================================================
--- chapter09/profile.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/profile.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -104,6 +104,6 @@
   before the telephone number in order to get into the country. If any of the
   commands above fail with a message similar to the one shown below, this means
-  that your locale was either not installed in Chapter&nbsp;6 or is not supported by
-  the default installation of Glibc.</para>
+  that your locale was either not installed in <xref linkend="ch-system-glibc"/> 
+  or is not supported by the default installation of Glibc.</para>
 
 <screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen>
@@ -115,5 +115,5 @@
 
   <!-- FIXME: the xlib example will became obsolete real soon -->
-  <para>Some packages beyond LFS may also lack support for your chosen locale. One
+  <!--<para>Some packages beyond LFS may also lack support for your chosen locale. One
   example is the X library (part of the X Window System), which outputs the
   following error message if the locale does not exactly match one of the character
@@ -129,5 +129,5 @@
   For example, one would have to change "de_DE.ISO-8859-15@euro" to
   "de_DE@euro" in order to get this locale recognized by Xlib.</para>
-
+-->
   <para>Other packages can also function incorrectly (but may not necessarily
   display any error messages) if the locale name does not meet their expectations.
@@ -146,5 +146,5 @@
 EOF</userinput></screen>
 
-  <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the recommended
+  <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended
   one for United States English users) locales are different. <quote>C</quote>
   uses the US-ASCII 7-bit character set, and treats bytes with the high bit set
Index: chapter09/symlinks.xml
===================================================================
--- chapter09/symlinks.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/symlinks.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -22,5 +22,5 @@
     Intel and Realtek, the network card manufactured by Intel may become eth0
     and the Realtek card becomes eth1. In some cases, after a reboot the cards
-    get renumbered the other way around.</para>
+    could get renumbered the other way around.</para>
     
     <para>In the new naming scheme, typical network device names would then
@@ -45,5 +45,5 @@
       <title>Creating Custom Udev Rules</title>
    
-      <para>The naming scheme can be customized by creating custom Udev
+      <para>The naming scheme can be customized by creating custom udev
       rules.  A script has been included that generates the initial rules.
       Generate these rules by running:</para>
@@ -69,7 +69,7 @@
       the hardware ID nor the driver is used to determine which name to give an
       interface; this information is only for reference. The second line is the
-      Udev rule that matches this NIC and actually assigns it a name.</para>
-  
-      <para>All Udev rules are made up of several keys, separated by commas and
+      udev rule that matches this NIC and actually assigns it a name.</para>
+  
+      <para>All udev rules are made up of several keys, separated by commas and
       optional whitespace. This rule's keys and an explanation of each of them
       are as follows:</para>
@@ -77,14 +77,14 @@
       <itemizedlist>
         <listitem>
-          <para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore
+          <para><literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore
           devices that are not network cards.</para>
         </listitem>
         <listitem>
-          <para><literal>ACTION=="add"</literal> - This tells Udev to ignore this
+          <para><literal>ACTION=="add"</literal> - This tells udev to ignore this
           rule for a uevent that isn't an add ("remove" and "change" uevents also
           happen, but don't need to rename network interfaces).</para>
         </listitem>
         <listitem>
-          <para><literal>DRIVERS=="?*"</literal> - This exists so that Udev will
+          <para><literal>DRIVERS=="?*"</literal> - This exists so that udev will
           ignore VLAN or bridge sub-interfaces (because these sub-interfaces do
           not have drivers). These sub-interfaces are skipped because the name
@@ -97,5 +97,5 @@
         <listitem>
           <para><literal>ATTR{type}=="1"</literal> - This ensures the rule only
-          matches the primary interface in the case of certain wireless drivers,
+          matches the primary interface in the case of certain wireless drivers
           which create multiple virtual interfaces. The secondary interfaces are
           skipped for the same reason that VLAN and bridge sub-interfaces are
@@ -104,5 +104,5 @@
         <listitem>
           <para><literal>NAME</literal> - The value of this key is the name that
-          Udev will assign to this interface.</para>
+          udev will assign to this interface.</para>
         </listitem>
       </itemizedlist>
@@ -134,6 +134,6 @@
     the physical path to the CD or DVD device. Second, it can operate in
     <quote>by-id</quote> mode (default for IDE and SCSI devices), where the
-    rules it creates depend on identification strings stored in the CD or DVD
-    device itself. The path is determined by Udev's <command>path_id</command>
+    rules it creates depend on identification strings stored on the CD or DVD
+    device itself. The path is determined by udev's <command>path_id</command>
     script, and the identification strings are read from the hardware by its
     <command>ata_id</command> or <command>scsi_id</command> programs, depending
@@ -160,9 +160,9 @@
     should not use by-path persistence, because each time the device is plugged
     into a new external port, its physical path will change. All
-    externally-connected devices will have this problem if you write Udev rules
+    externally-connected devices will have this problem if you write udev rules
     to recognize them by their physical path; the problem is not limited to CD
     and DVD drives.</para></important>
 
-    <para>If you wish to see the values that the Udev scripts will use, then
+    <para>If you wish to see the values that the udev scripts will use, then
     for the appropriate CD-ROM device, find the corresponding directory under
     <filename class="directory">/sys</filename> (e.g., this can be
@@ -183,10 +183,10 @@
     <quote>by-id</quote> or <quote>by-path</quote>):</para>
 
-<screen role="nodump"><userinput>sed -i -e 's/"write_cd_rules"/"write_cd_rules <replaceable>mode</replaceable>"/' \
-    /etc/udev/rules.d/83-cdrom-symlinks.rules</userinput></screen>
+<screen role="nodump"><userinput>sed -e 's/"write_cd_rules"/"write_cd_rules <replaceable>mode</replaceable>"/' \
+    -i /etc/udev/rules.d/83-cdrom-symlinks.rules</userinput></screen>
 
     <para>Note that it is not necessary to create the rules files or symlinks
-    at this time, because you have bind-mounted the host's
-    <filename class="directory">/dev</filename> directory into the LFS system,
+    at this time because you have bind-mounted the host's
+    <filename class="directory">/dev</filename> directory into the LFS system
     and we assume the symlinks exist on the host. The rules and symlinks will
     be created the first time you boot your LFS system.</para>
@@ -194,5 +194,5 @@
     <para>However, if you have multiple CD-ROM devices, then the symlinks
     generated at that time may point to different devices than they point to on
-    your host, because devices are not discovered in a predictable order. The
+    your host because devices are not discovered in a predictable order. The
     assignments created when you first boot the LFS system will be stable, so
     this is only an issue if you need the symlinks on both systems to point to
@@ -213,7 +213,7 @@
     <filename>/dev/video0</filename> refers to the camera and
     <filename>/dev/video1</filename> refers to the tuner, and sometimes
-    after a reboot the order changes to the opposite one.
+    after a reboot the order changes.
     For all classes of hardware except sound cards and network cards, this is
-    fixable by creating Udev rules for custom persistent symlinks.
+    fixable by creating udev rules for custom persistent symlinks.
     The case of network cards is covered separately in
     <xref linkend="ch-config-network"/>, and sound card configuration can
@@ -238,8 +238,6 @@
 <literal>
 # Persistent symlinks for webcam and tuner
-KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", \
-    SYMLINK+="webcam"
-KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", \
-    SYMLINK+="tvtuner"
+KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", SYMLINK+="webcam"
+KERNEL=="video*", ATTRS{device}=="0x036f",  ATTRS{vendor}=="0x109e", SYMLINK+="tvtuner"
 </literal>
 EOF</userinput></screen>
Index: chapter09/udev.xml
===================================================================
--- chapter09/udev.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/udev.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -16,5 +16,5 @@
   </indexterm>
 
-  <para>In <xref linkend="chapter-building-system"/>, we installed the Udev
+  <para>In <xref linkend="chapter-building-system"/>, we installed the udev
   package when <phrase revision="sysv">eudev</phrase>
   <phrase revision="systemd">systemd</phrase> was built. Before we go into the
@@ -31,5 +31,5 @@
   the world.</para>
 
-  <para>Using the Udev method, only those devices which are detected by the
+  <para>Using the udev method, only those devices which are detected by the
   kernel get device nodes created for them. Because these device nodes will be
   created each time the system boots, they will be stored on a <systemitem
@@ -136,5 +136,5 @@
       might contain the string
       <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
-      The default rules provided with Udev will cause <command>udevd</command>
+      The default rules provided with udev will cause <command>udevd</command>
       to call out to <command>/sbin/modprobe</command> with the contents of the
       <envar>MODALIAS</envar> uevent environment variable (which should be the
@@ -150,5 +150,5 @@
 
       <para>The kernel itself is also able to load modules for network
-      protocols, filesystems and NLS support on demand.</para>
+      protocols, filesystems, and NLS support on demand.</para>
 
     </sect3>
@@ -178,10 +178,10 @@
       bus driver properly exports the necessary aliases to <systemitem
       class="filesystem">sysfs</systemitem>. In other cases, one should
-      arrange module loading by other means. With Linux-&linux-version;, Udev is
+      arrange module loading by other means. With Linux-&linux-version;, udev is
       known to load properly-written drivers for INPUT, IDE, PCI, USB, SCSI,
       SERIO, and FireWire devices.</para>
 
       <para>To determine if the device driver you require has the necessary
-      support for Udev, run <command>modinfo</command> with the module name as
+      support for udev, run <command>modinfo</command> with the module name as
       the argument.  Now try locating the device directory under
       <filename class="directory">/sys/bus</filename> and check whether there is
@@ -191,5 +191,5 @@
       class="filesystem">sysfs</systemitem>, the driver supports the device and
       can talk to it directly, but doesn't have the alias, it is a bug in the
-      driver. Load the driver without the help from Udev and expect the issue
+      driver. Load the driver without the help from udev and expect the issue
       to be fixed later.</para>
 
@@ -207,5 +207,5 @@
 
     <sect3>
-      <title>A kernel module is not loaded automatically, and Udev is not
+      <title>A kernel module is not loaded automatically, and udev is not
       intended to load it</title>
 
@@ -215,5 +215,5 @@
       <emphasis>snd-pcm</emphasis> by making the sound cards available to OSS
       applications), configure <command>modprobe</command> to load the wrapper
-      after Udev loads the wrapped module. To do this, add a
+      after udev loads the wrapped module. To do this, add a
       <quote>softdep</quote> line to the corresponding
       <filename>/etc/modprobe.d/<replaceable>&lt;filename&gt;</replaceable>.conf</filename>
@@ -280,5 +280,5 @@
       <para>Further text assumes that the driver is built statically into the
       kernel or already loaded as a module, and that you have already checked
-      that Udev doesn't create a misnamed device.</para>
+      that udev doesn't create a misnamed device.</para>
 
       <para>Udev has no information needed to create a device node if a kernel
@@ -298,10 +298,10 @@
       <title>Device naming order changes randomly after rebooting</title>
 
-      <para>This is due to the fact that Udev, by design, handles uevents and
+      <para>This is due to the fact that udev, by design, handles uevents and
       loads modules in parallel, and thus in an unpredictable order. This will
       never be <quote>fixed</quote>. You should not rely upon the kernel device
       names being stable. Instead, create your own rules that make symlinks with
       stable names based on some stable attributes of the device, such as a
-      serial number or the output of various *_id utilities installed by Udev.
+      serial number or the output of various *_id utilities installed by udev.
       See <xref linkend="ch-config-symlinks"/> and
       <xref linkend="ch-config-network"/> for examples.</para>
Index: chapter09/usage.xml
===================================================================
--- chapter09/usage.xml	(revision 96f04d7906bb26ba31cc35c35e4cc82261bbad1d)
+++ chapter09/usage.xml	(revision a3d0817020eee2b1ea6ebfe10f3a0ea9e26829be)
@@ -236,48 +236,4 @@
       <para>For information on kernel module loading and udev, see 
       <xref linkend="module-loading"/>.</para>
-<!--
-    <sect3>
-      <title>Module Loading</title>
-
-      <para>Device drivers compiled as modules may have aliases built into them.
-      Aliases are visible in the output of the <command>modinfo</command>
-      program and are usually related to the bus-specific identifiers of devices
-      supported by a module. For example, the <emphasis>snd-fm801</emphasis>
-      driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,
-      and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.
-      For most devices, the bus driver exports the alias of the driver that
-      would handle the device via <systemitem
-      class="filesystem">sysfs</systemitem>. E.g., the
-      <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file
-      might contain the string
-      <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
-      The default rules provided with Udev will cause <command>udevd</command>
-      to call out to <command>/sbin/modprobe</command> with the contents of the
-      <envar>MODALIAS</envar> uevent environment variable (which should be the
-      same as the contents of the <filename>modalias</filename> file in sysfs),
-      thus loading all modules whose aliases match this string after wildcard
-      expansion.</para>
-
-      <para>In this example, this means that, in addition to
-      <emphasis>snd-fm801</emphasis>, the obsolete (and unwanted)
-      <emphasis>forte</emphasis> driver will be loaded if it is
-      available. See below for ways in which the loading of unwanted drivers can
-      be prevented.</para>
-
-      <para>The kernel itself is also able to load modules for network
-      protocols, filesystems and NLS support on demand.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Handling Hotpluggable/Dynamic Devices</title>
-
-      <para>When you plug in a device, such as a Universal Serial Bus (USB) MP3
-      player, the kernel recognizes that the device is now connected and
-      generates a uevent. This uevent is then handled by
-      <command>udevd</command> as described above.</para>
-
-    </sect3>
--->
   </sect2>
 
@@ -294,9 +250,9 @@
     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
+    <command>hwclock</command> program which timezone to use). There is no
     way to detect whether or not the hardware clock is set to UTC, so this
     needs to be configured manually.</para>
 
-    <para>The <command>setclock</command> is run via
+    <para>The <command>setclock</command> program is run via
     <application>udev</application> when the kernel detects the hardware
     capability upon boot.  It can also be run manually with the stop parameter to
@@ -316,5 +272,5 @@
     <para>Change the value of the <envar>UTC</envar> variable below
     to a value of <parameter>0</parameter> (zero) if the hardware clock
-    is <emphasis>not</emphasis> set to UTC time.</para>
+    is <emphasis>NOT</emphasis> set to UTC time.</para>
 
     <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
@@ -337,5 +293,5 @@
     time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
 
-    <note><para>The CLOCKPARAMS and UTC paramaters may be alternatively set
+    <note><para>The CLOCKPARAMS and UTC paramaters may also be set
     in the <filename>/etc/sysconfig/rc.site</filename> file.</para></note>
 
@@ -353,5 +309,5 @@
 
   <para>This section discusses how to configure the <command>console</command>
-  bootscript that sets up the keyboard map, console font and console kernel log
+  bootscript that sets up the keyboard map, console font, and console kernel log
   level. If non-ASCII characters (e.g., the copyright sign, the British pound
   sign and Euro symbol) will not be used and the keyboard is a U.S. one, much
@@ -506,5 +462,5 @@
       <para>Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous
       example, bright colors are no longer available on the Linux console unless
-      a framebuffer is used. If one wants to have bright colors without
+      a framebuffer is used. If one wants to have bright colors without a
       framebuffer and can live without characters not belonging to his language,
       it is still possible to use a language-specific 256-glyph font, as
@@ -549,5 +505,5 @@
       languages, because there accents are added to unaccented ASCII
       characters, or two ASCII characters are composed together. However, in
-      UTF-8 mode it is a problem, e.g., for the Greek language, where one
+      UTF-8 mode it is a problem; e.g., for the Greek language, where one
       sometimes needs to put an accent on the letter <quote>alpha</quote>.
       The solution is either to avoid the use of UTF-8, or to install the
@@ -557,9 +513,9 @@
 
     <listitem>
-      <para>For Chinese, Japanese, Korean and some other languages, the Linux
+      <para>For Chinese, Japanese, Korean, and some other languages, the Linux
       console cannot be configured to display the needed characters. Users
       who need such languages should install the X Window System, fonts that
       cover the necessary character ranges, and the proper input method (e.g.,
-      SCIM, it supports a wide variety of languages).</para>
+      SCIM, supports a wide variety of languages).</para>
     </listitem>
 
@@ -572,5 +528,5 @@
     the Linux text console localization. It has nothing to do with setting
     the proper keyboard layout and terminal fonts in the X Window System, with
-    ssh sessions or with a serial console. In such situations, limitations
+    ssh sessions, or with a serial console. In such situations, limitations
     mentioned in the last two list items above do not apply.</para>
   </note>
@@ -586,7 +542,7 @@
     </indexterm>
   
-    <para>At times, it is desired to create files at boot time.  For instance,
+    <para>At times, it is desirable to create files at boot time.  For instance,
     the <filename class="directory">/tmp/.ICE-unix</filename> directory
-    may be desired.  This can be done by creating an entry in the
+    is often needed.  This can be done by creating an entry in the
     <filename>/etc/sysconfig/createfiles</filename> configuration script.
     The format of this file is embedded in the comments of the default 
