Index: chapter08/kernel.xml
===================================================================
--- chapter08/kernel.xml	(revision 3ed279fe4d363178e7134f90e541a77d87f6e0fb)
+++ chapter08/kernel.xml	(revision 8b320e7219377ddab51f5e67396714d1d0d3141a)
@@ -16,6 +16,6 @@
 <segtitle>&buildtime;</segtitle>
 <segtitle>&diskspace;</segtitle>
-<seglistitem><seg>All default options: 4.20 SBU</seg>
-<seg>All default options: 181 MB</seg></seglistitem>
+<seglistitem><seg>4.20 SBU</seg>
+<seg>181 MB</seg></seglistitem>
 </segmentedlist>
 
@@ -23,5 +23,5 @@
 <segtitle>Linux installation depends on</segtitle>
 <seglistitem><seg>Bash, Binutils, Coreutils, Findutils,
-GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, Sed</seg></seglistitem>
+GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, and Sed</seg></seglistitem>
 </segmentedlist>
 </sect2>
@@ -30,5 +30,5 @@
 <title>Installation of the kernel</title>
 
-<para>Building the kernel involves a few steps -- configuration,
+<para>Building the kernel involves a few steps&mdash;configuration,
 compilation, and installation. Read the <filename>README</filename>
 file in the kernel source tree for alternative methods to the way this
@@ -50,6 +50,6 @@
 <screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
 
-<para>If, in <xref linkend="ch-scripts-console"/>, you decided to
-compile the keymap into the kernel, issue the command below:</para>
+<para>If, in <xref linkend="ch-scripts-console"/> the keymap was
+compiled into the kernel, issue the command below:</para>
 
 <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to  keymap]</replaceable> &gt; \
@@ -67,5 +67,5 @@
 information.</para>
 
-<note><para>When you configure the kernel, be sure to enable the
+<note><para>When configuring the kernel, be sure to enable the
 <quote>Support for hot-pluggable devices</quote> option under the
 <quote>General Setup</quote> menu. This enables hotplug events that
@@ -79,8 +79,8 @@
 class="directory">linux-&linux-version;</filename> directory. However,
 we do not recommend this option. It is often better to explore all the
-configuration menus and creating the kernel configuration from
+configuration menus and create the kernel configuration from
 scratch.</para>
 
-<para>For POSIX shared memory support, ensure that the kernel config
+<para>For POSIX-shared memory support, ensure that the kernel config
 option <quote>Virtual memory file system support</quote> is enabled.
 It resides within the <quote>File systems</quote> menu and is normally
@@ -95,5 +95,5 @@
 <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in
 this case &gcc-version;. Compiling with 2.95.x is known to cause failures in
-the glibc testsuite, so it is not recommended to compile the kernel
+the glibc test suite, so it is not recommended to compile the kernel
 with gcc 2.95.x.</para></note>
 
@@ -104,5 +104,5 @@
 <para>If using kernel modules, an
 <filename>/etc/modprobe.conf</filename> file may be needed.
-Information pertaining to modules and to kernel configuration is
+Information pertaining to modules and kernel configuration is
 located in the kernel documentation in the <filename
 class="directory">linux-&linux-version;/Documentation</filename>
@@ -110,5 +110,5 @@
 of interest.</para>
 
-<para>Be very careful when reading other documentation, because it
+<para>Be very careful when reading other documentation because it
 usually applies to 2.4.x kernels only. As far as we know, kernel
 configuration issues specific to Hotplug and Udev are not documented.
@@ -124,5 +124,5 @@
 configuration, especially if this is the first time using Udev.</para>
 
-<para>Install the modules, if your kernel configuration uses them:</para>
+<para>Install the modules, if the kernel configuration uses them:</para>
 
 <screen><userinput>make modules_install</userinput></screen>
@@ -161,5 +161,5 @@
 directory are not owned by <emphasis>root</emphasis>. Whenever a
 package is unpacked as user <emphasis>root</emphasis> (like we did
-here inside chroot), the files have the user and group IDs of whatever
+inside chroot), the files have the user and group IDs of whatever
 they were on the packager's computer. This is usually not a problem
 for any other package to be installed because the source tree is
@@ -181,6 +181,6 @@
 <segmentedlist>
 <segtitle>Installed files</segtitle>
-<seglistitem><seg>the kernel, the kernel headers,
-and the System.map</seg></seglistitem>
+<seglistitem><seg>kernel, kernel headers,
+and System.map</seg></seglistitem>
 </segmentedlist>
 
@@ -189,11 +189,11 @@
 
 <varlistentry id="kernel">
-<term>The <emphasis>kernel</emphasis></term>
+<term><command>kernel</command></term>
 <listitem>
-<para>the engine of the Linux system. When turning on your computer,
+<para>the engine of the Linux system. When turning on the computer,
 the kernel is the first part of the operating system that gets loaded.
 It detects and initializes all components of the computer's hardware,
 then makes these components available as a tree of files to the
-software, and turns a single CPU into a multitasking machine capable
+software and turns a single CPU into a multitasking machine capable
 of running scores of programs seemingly at the same time.</para>
 <indexterm zone="ch-bootable-kernel kernel"><primary sortas="b-kernel">kernel</primary></indexterm>
@@ -202,8 +202,8 @@
 
 <varlistentry id="kernel-headers">
-<term>The <emphasis>kernel headers</emphasis></term>
+<term><command>kernel headers</command></term>
 <listitem>
 <para>defines the interface to the services that the kernel provides.
-The headers in your system's <filename
+The headers in the system's <filename
 class="directory">include</filename> directory should
 <emphasis>always</emphasis> be the ones against which Glibc was
@@ -217,5 +217,5 @@
 <term><filename>System.map</filename></term>
 <listitem>
-<para>is a list of addresses and symbols. It maps the entry points and
+<para>a list of addresses and symbols. It maps the entry points and
 addresses of all the functions and data structures in the
 kernel.</para>
