Index: chapter08/fstab.xml
===================================================================
--- chapter08/fstab.xml	(revision 4abce96c4b09b3a38451773015cb5c926614ab90)
+++ chapter08/fstab.xml	(revision 1dc34de7baaf4bcb5600ae04e809b7087452d648)
@@ -10,8 +10,8 @@
 <indexterm zone="ch-bootable-fstab"><primary sortas="e-/etc/fstab">/etc/fstab</primary></indexterm>
 
-<para>The <filename>/etc/fstab</filename> file is used by some programs to
-determine where file systems are to be mounted by default, which
-must be checked and in which order. Create a new file systems table like
-this:</para>
+<para>The <filename>/etc/fstab</filename> file is used by some
+programs to determine where file systems are to be mounted by default,
+which must be checked, and in which order. Create a new file systems
+table like this:</para>
 
 <screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"
@@ -29,33 +29,38 @@
 EOF</userinput></screen>
 
-<para>Of course, replace <replaceable>[xxx]</replaceable>, <replaceable>[yyy]</replaceable>
-and <replaceable>[fff]</replaceable> with the values appropriate for your system --
-for example <filename class="partition">hda2</filename>, <filename class="partition">hda5</filename> and
-<systemitem class="filesystem">reiserfs</systemitem>. For all the details on the six fields in this
-table, see <command>man 5 fstab</command>.</para>
+<para>Replace <replaceable>[xxx]</replaceable>,
+<replaceable>[yyy]</replaceable> and <replaceable>[fff]</replaceable>
+with the values appropriate for the system. For example, <filename
+class="partition">hda2</filename>, <filename
+class="partition">hda5</filename>, and <systemitem
+class="filesystem">reiserfs</systemitem>. For details on the six
+fields in this file, see <command>man 5 fstab</command>.</para>
 
-<para>When using a reiserfs partition, the <parameter>1 1</parameter> at the
-end of the line should be replaced with <parameter>0 0</parameter>, as such a
-partition does not need to be dumped or checked</para>
+<para>When using a reiserfs partition, the <parameter>1 1</parameter>
+at the end of the line should be replaced with <parameter>0
+0</parameter> because such a partition does not need to be dumped or
+checked.</para>
 
-<para>The <filename class="directory">/dev/shm</filename> mount point for
-<systemitem class="filesystem">tmpfs</systemitem> is included to
-allow enabling POSIX shared memory. Your kernel must have the required support
-built into it for this to work -- more about this in the next section. Please
-note that currently very little software actually uses POSIX shared memory.
-Therefore you can consider the <filename class="directory">/dev/shm</filename> mount point
-optional. For more information, see
-<filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel source
-tree.</para>
+<para>The <filename class="directory">/dev/shm</filename> mount point
+for <systemitem class="filesystem">tmpfs</systemitem> is included to
+allow enabling POSIX shared memory. The kernel must have the required
+support built into it for this to work (more about this in the next
+section). Please note that very little software currently uses POSIX
+shared memory.  Therefore, consider the <filename
+class="directory">/dev/shm</filename> mount point optional. For more
+information, see
+<filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel
+source tree.</para>
 
-<para>There are other lines which you may consider adding to your
-<filename>fstab</filename> file. One example is a line to use if you intend to
-use USB devices:</para>
+<para>There are other lines which may be added to the
+<filename>/etc/fstab</filename> file. One example is a line for USB
+devices:</para>
 
 <screen> usbfs         /proc/bus/usb usbfs   devgid=14,devmode=0660 0 0 </screen>
 
-<para>This option will of course only work if you have the
-"Support for Host-side USB" and "USB device filesystem"
-compiled into your kernel (not as a module).</para>
+<para>This option will only work if the <quote>Support for Host-side
+USB</quote> and <quote>USB device filesystem</quote> are compiled into
+the kernel (not as a module).</para>
 
 </sect1>
+
Index: chapter08/grub.xml
===================================================================
--- chapter08/grub.xml	(revision 4abce96c4b09b3a38451773015cb5c926614ab90)
+++ chapter08/grub.xml	(revision 1dc34de7baaf4bcb5600ae04e809b7087452d648)
@@ -12,58 +12,63 @@
 <secondary>configuring</secondary></indexterm>
 
-<para>Your shiny new LFS system is almost complete. One of the last things to
-do is ensure you can boot it. The instructions below apply only to computers of
-IA-32 architecture, meaning mainstream PCs. Information on <quote>boot
-loading</quote> for other architectures should be available in the usual
-resource-specific locations for those architectures.</para>
+<para>Your shiny new LFS system is almost complete. One of the last
+things to do is ensure that it can be properly booted. The
+instructions below apply only to computers of IA-32 architecture,
+meaning mainstream PCs. Information on <quote>boot loading</quote> for
+other architectures should be available in the usual resource-specific
+locations for those architectures.</para>
 
-<para>Boot loading can be a complex area. First, a few cautionary words. You
-really should be familiar with your current boot loader and any other
-operating systems present on your hard drive(s) that you might wish to keep
-bootable. Please make sure that you have an emergency boot disk ready, so that
-you can rescue your computer if, by any chance, your computer becomes unusable
-(un-bootable).</para>
+<para>Boot loading can be a complex area. First, a few cautionary
+words. Be familiar with the current boot loader and any other
+operating systems present on the hard drive(s) that need to be
+bootable. Please make sure that an emergency boot disk is ready to
+<quote>rescue</quote> the computer if, by chance, the computer becomes
+unusable (un-bootable).</para>
 
-<para>Earlier, we compiled and installed the Grub boot loader software in
-preparation for this step. The procedure involves writing some special Grub
-files to specific locations on the hard drive. Before we get to that, we
-highly recommend that you create a Grub boot floppy diskette just in case.
-Insert a blank floppy diskette and run the following commands:</para>
+<para>Earlier, we compiled and installed the Grub boot loader software
+in preparation for this step. The procedure involves writing some
+special Grub files to specific locations on the hard drive. We highly
+recommend a Grub boot floppy diskette be created as a backup. Insert a
+blank floppy diskette and run the following commands:</para>
 
 <screen><userinput>dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1
 dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1</userinput></screen>
 
-<para>Remove the diskette and store it somewhere safe. Now we'll run the
+<para>Remove the diskette and store it somewhere safe. Now, run the
 <command>grub</command> shell:</para>
 
 <screen><userinput>grub</userinput></screen>
 
-<para>Grub uses its own naming structure for drives and partitions, in the form
-of (hdn,m), where <emphasis>n</emphasis> is the hard drive number, and
-<emphasis>m</emphasis> the partition number, both starting from zero. This
-means, for instance, that partition <filename class="partition">hda1</filename> is (hd0,0) to
-Grub, and <filename class="partition">hdb2</filename> is (hd1,1). In contrast to Linux, Grub
-doesn't consider CD-ROM drives to be hard drives, so if you have a CD on
-<filename class="partition">hdb</filename>, for example, and a second hard drive on
-<filename class="partition">hdc</filename>, that second hard drive would still be (hd1).</para>
+<para>Grub uses its own naming structure for drives and partitions, in
+the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
+is the hard drive number and <emphasis>m</emphasis> is the partition
+number, both starting from zero. For example, partition <filename
+class="partition">hda1</filename> is <emphasis>(hd0,0)</emphasis> to
+Grub, and <filename class="partition">hdb3</filename> is
+<emphasis>(hd1,2)</emphasis>. In contrast to Linux, Grub does not
+consider CD-ROM drives to be hard drives. For example, if using a CD
+on <filename class="partition">hdb</filename> and a second hard drive
+on <filename class="partition">hdc</filename>, that second hard drive
+would still be <emphasis>(hd1)</emphasis>.</para>
 
-<para>Using the above information, determine the appropriate designator for
-your root partition (or boot partition, if you use a separate one). For the
-following example, we'll assume your root (or separate boot) partition is
-<filename class="partition">hda4</filename>.</para>
+<para>Using the above information, determine the appropriate
+designator for the root partition (or boot partition, if a separate
+one is used). For the following example, it is assumed that the root
+(or separate boot) partition is <filename
+class="partition">hda4</filename>.</para>
 
-<para>First, tell Grub where to search for its <filename>stage{1,2}</filename>
-files -- you can use the Tab key everywhere to make Grub show the alternatives:</para>
+<para>First, tell Grub where to search for its
+<filename>stage{1,2}</filename> files. The Tab key can be used
+everywhere to make Grub show the alternatives:</para>
 
 <screen><userinput>root (hd0,3)</userinput></screen>
 
-
-<warning><para>The following command will overwrite your current boot loader.
-Don't run the command if this is not what you want. For example, you may be
-using a third party boot manager to manage your MBR (Master Boot Record). In
-this scenario, it would probably make more sense to install Grub into the
-<quote>boot sector</quote> of the LFS partition, in which case this next command
-would become: <userinput>setup (hd0,3)</userinput>.</para></warning>
-
+<warning><para>The following command will overwrite the current boot
+loader. Do not run the command if this is not desired, for example, if
+using a third party boot manager to manage the Master Boot Record
+(MBR). In this scenario, it would probably make more sense to install
+Grub into the <quote>boot sector</quote> of the LFS partition. In this
+case, this next command would become: <userinput>setup
+(hd0,3)</userinput>.</para></warning>
 
 <para>Tell Grub to install itself into the MBR (Master Boot Record) of
@@ -72,11 +77,11 @@
 <screen><userinput>setup (hd0)</userinput></screen>
 
-<para>If all is well, Grub will have reported finding its files in
-<filename class="directory">/boot/grub</filename>. That's all there is to it:</para>
+<para>If all went well, Grub will have reported finding its files in
+<filename class="directory">/boot/grub</filename>. That's all there is
+to it. Quit the <command>grub</command> shell:</para>
 
 <screen><userinput>quit</userinput></screen>
 
-<para>Now we need to create a <quote>menu list</quote> file, defining Grub's
-boot menu:</para>
+<para>Create a <quote>menu list</quote> file defining Grub's boot menu:</para>
 
 <screen><userinput>cat &gt; /boot/grub/menu.lst &lt;&lt; "EOF"
@@ -98,5 +103,5 @@
 EOF</userinput></screen>
 
-<para>You may want to add an entry for your host distribution. It might look
+<para>Add an entry for the host distribution if desired. It might look
 like this:</para>
 
@@ -108,6 +113,6 @@
 EOF</userinput></screen>
 
-<para>Also, if you happen to dual-boot Windows, the following entry should
-allow booting it:</para>
+<para>Also, if dual-booting Windows, the following entry will allow
+booting it:</para>
 
 <screen><userinput>cat &gt;&gt; /boot/grub/menu.lst &lt;&lt; "EOF"
@@ -117,7 +122,8 @@
 EOF</userinput></screen>
 
-<para>If <command>info grub</command> doesn't tell you all you want to
-know, you can find more information regarding Grub on its website, located at:
+<para>If <command>info grub</command> does not provide all necessary material, additional
+information regarding Grub is located on its website at:
 <ulink url="http://www.gnu.org/software/grub/"/>.</para>
 
 </sect1>
+
Index: chapter08/introduction.xml
===================================================================
--- chapter08/introduction.xml	(revision 4abce96c4b09b3a38451773015cb5c926614ab90)
+++ chapter08/introduction.xml	(revision 1dc34de7baaf4bcb5600ae04e809b7087452d648)
@@ -8,8 +8,9 @@
 <?dbhtml filename="introduction.html"?>
 
-<para>This chapter will make LFS bootable. This chapter deals with creating a
-<filename>fstab</filename> file, building a
-kernel for the new LFS system and installing the Grub bootloader
-so that the LFS system can be selected for booting at startup.</para>
+<para>This chapter will make the LFS system bootable. This chapter
+discusses creating an <filename>fstab</filename> file, building a
+kernel for the new LFS system, and installing the Grub bootloader so
+that the LFS system can be selected for booting at startup.</para>
 
 </sect1>
+
Index: chapter08/kernel.xml
===================================================================
--- chapter08/kernel.xml	(revision 4abce96c4b09b3a38451773015cb5c926614ab90)
+++ chapter08/kernel.xml	(revision 1dc34de7baaf4bcb5600ae04e809b7087452d648)
@@ -30,8 +30,8 @@
 <title>Installation of the kernel</title>
 
-<para>Building the kernel involves a few steps: configuration, compilation, and
-installation. If you don't like the way this book configures the kernel, view
-the <filename>README</filename> file in the kernel source tree for alternative
-methods.</para>
+<para>Building the kernel involves a few steps -- configuration,
+compilation, and installation. Read the <filename>README</filename>
+file in the kernel source tree for alternative methods to the way this
+book configures the kernel.</para>
 
 <para>Prepare for compilation by running the following command:</para>
@@ -39,21 +39,22 @@
 <screen><userinput>make mrproper</userinput></screen>
 
-<para>This ensures that the kernel tree is absolutely clean. The kernel team
-recommends that this command be issued prior to <emphasis>each</emphasis>
-kernel compilation. You shouldn't rely on the source tree being clean after
+<para>This ensures that the kernel tree is absolutely clean. The
+kernel team recommends that this command be issued prior to each
+kernel compilation. Do not rely on the source tree being clean after
 un-tarring.</para>
 
-<para>Also, ensure that the kernel does not attempt to pass hotplugging events
-to userspace until userspace specifies that it is ready:</para>
+<para>Also, ensure that the kernel does not attempt to pass
+hotplugging events to userspace until userspace specifies that it is
+ready:</para>
 
 <screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
 
-<para>If, in <xref linkend="ch-scripts-console"/>, you decided you want
-to compile the keymap into the kernel, issue the command below:</para>
+<para>If, in <xref linkend="ch-scripts-console"/>, you decided to
+compile the keymap into the kernel, issue the command below:</para>
 
 <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to  keymap]</replaceable> &gt; \
     <replaceable>[unpacked sources dir]</replaceable>/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen>
 
-<para>For example, if you have a Dutch keyboard, you would use
+<para>For example, if using a Dutch keyboard, use
 <filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
 
@@ -66,25 +67,34 @@
 information.</para>
 
-<para>If you wish, you may skip kernel configuration by simply copying the
-kernel config file, <filename>.config</filename>, from your host system
-(assuming it is available) to the unpacked <filename class="directory">linux-&linux-version;</filename>
-directory. However, we
-don't recommend this option. You're much better off exploring all the
-configuration menus and creating your own kernel configuration from
+<note><para>When you configure 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
+are used by <command>udev</command> to populate the <filename
+class="directory">/dev</filename> directory with device
+nodes.</para></note>
+
+<para>If desired, skip kernel configuration by copying the kernel
+config file, <filename>.config</filename>, from the host system
+(assuming it is available) to the unpacked <filename
+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
 scratch.</para>
 
-<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 enabled by default.</para>
-
-<para>LFS bootscripts make the assumption that you either compile
-both <quote>Support for Host-side USB</quote> and
-<quote>USB device filesystem</quote> directly into the kernel, or don't compile them at
-all. Bootscripts will not work properly if it is a module (<filename>usbcore.ko</filename>).</para>
-
-<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 do <emphasis>not</emphasis> compile the kernel with gcc 2.95.x
-unless you know what you're getting yourself into.</para></note>
+<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
+enabled by default.</para>
+
+<para>LFS bootscripts make the assumption that either both
+<quote>Support for Host-side USB</quote> and <quote>USB device
+filesystem</quote> have been compiled directly into the kernel, or
+that neither is compiled at all.  Bootscripts will not work properly
+if it is a module (usbcore.ko).</para>
+
+<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
+with gcc 2.95.x.</para></note>
 
 <para>Compile the kernel image and modules:</para>
@@ -92,29 +102,25 @@
 <screen><userinput>make</userinput></screen>
 
-<para>If you intend to use kernel modules, you may need an
-<filename>/etc/modprobe.conf</filename> file. Information pertaining
-to modules and to kernel configuration in general may be found in the
-kernel documentation, which is found in the
-<filename class="directory">linux-&linux-version;/Documentation</filename> directory.
-The modprobe.conf man page
-<!-- removed for review from tldp.org
-and the kernel HOWTO at
-<ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> -->
-may also be of interest to you.</para>
-
-<para>Be very suspicious while reading other documentation, because it
-usually applies to 2.4.x kernels only. As far as the editors know, kernel
-configuration issues specific to Hotplug and Udev
-are documented nowhere. The problem is that Udev will create a device node
-only if Hotplug or a user-written script inserts the corresponding module
-into the kernel, and not all modules are detectable by Hotplug. Note
-that statements like
-<screen>alias char-major-XXX some-module</screen>
-in <filename>/etc/modprobe.conf</filename> file don't work with
+<para>If using kernel modules, an
+<filename>/etc/modprobe.conf</filename> file may be needed.
+Information pertaining to modules and to kernel configuration is
+located in the kernel documentation in the <filename
+class="directory">linux-&linux-version;/Documentation</filename>
+directory. The <emphasis>modprobe.conf</emphasis> man page may also be
+of interest.</para>
+
+<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.
+The problem is that Udev will create a device node only if Hotplug or
+a user-written script inserts the corresponding module into the
+kernel, and not all modules are detectable by Hotplug. Note that
+statements like <screen>alias char-major-XXX some-module</screen> in
+the <filename>/etc/modprobe.conf</filename> file do not work with
 Udev, and other aliases are often unnecessary with Hotplug.</para>
 
-<para>Because of all those compilcations with Hotplug, Udev and modules, we
-strongly recommend you to start with a completely non-modular kernel
-configuration, especially if this is the first time you use Udev.</para>
+<para>Because of the complications with Hotplug, Udev, and modules, we
+strongly recommend starting with a completely non-modular kernel
+configuration, especially if this is the first time using Udev.</para>
 
 <para>Install the modules, if your kernel configuration uses them:</para>
@@ -122,47 +128,50 @@
 <screen><userinput>make modules_install</userinput></screen>
 
-<para>If you have a lot of modules and very little space, you may want to
-consider stripping and compressing the modules. For most people such compression
-isn't worth the trouble, but if you're really pressed for space, then have a look at
-<ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
-
-<para>Kernel compilation has finished but more steps are required to complete
-the installation. Some files need to be copied to the <filename class="directory">/boot</filename>
-directory.</para>
-
-<para>The path to the kernel image may vary depending on the platform you're
-using. Issue the following command to install the kernel:</para>
+<para>If there are many modules and very little space, consider
+stripping and compressing the modules. For most users, such
+compression is not worth the time, but if the system is pressed for
+space, see <ulink
+url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
+
+<para>After kernel compilation is complete, additional steps are
+required to complete the installation. Some files need to be copied to
+the <filename class="directory">/boot</filename> directory.</para>
+
+<para>The path to the kernel image may vary depending on the platform
+being used. Issue the following command to install the kernel:</para>
 
 <screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen>
 
-<para><filename>System.map</filename> is a symbol file for the kernel. It maps
-the function entry points of every function in the kernel API (Application Programming Interface), as well as the
-addresses of the kernel data structures for the running kernel. Issue the
-following command to install the map file:</para>
+<para><filename>System.map</filename> is a symbol file for the kernel.
+It maps the function entry points of every function in the kernel API,
+as well as the addresses of the kernel data structures for the running
+kernel. Issue the following command to install the map file:</para>
 
 <screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen>
 
-<para><filename>.config</filename> is the kernel configuration file that was
-produced by the <command>make menuconfig</command> step above. It contains all
-the config selections for the kernel that was just compiled. It's a good idea
-to keep this file for future reference:</para>
+<para><filename>.config</filename> is the kernel's configuration file
+that was produced by the <command>make menuconfig</command> step
+above. It contains all the configuration selections for the kernel
+that was just compiled. It is a good idea to keep this file for future
+reference:</para>
 
 <screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen>
 
-<para>It is important to note that the files in the kernel source directory are
-not owned by <emphasis>root</emphasis>. Whenever you unpack a package as user
-<emphasis>root</emphasis> (like we did here inside chroot), the files end up
-having the user and group IDs of whatever they were on the packager's computer.
-This is usually not a problem for any other package you install because you
-remove the source tree after the installation. But the Linux source tree is
-often kept around for a long time, so there's a chance that whatever user ID
-the packager used will be assigned to somebody on your machine and then that
-person would have write access to the kernel source.</para>
-
-<para>If you are going to keep the kernel source tree around, you may want to
-run <command>chown -R 0:0</command> on the
-<filename class="directory">linux-&linux-version;</filename> directory to ensure all files are
-owned by user <emphasis>root</emphasis>.</para>
-
+<para>It is important to note that the files in the kernel source
+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
+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
+removed after the installation. However, the Linux source tree is
+often retained for a long time.  Because of this, there is a chance
+that whatever user ID the packager used will be assigned to somebody
+on the machine. That person would then have write access to the kernel
+source.</para>
+
+<para>If the kernel source tree is going to retained, run
+<command>chown -R 0:0</command> on the <filename
+class="directory">linux-&linux-version;</filename> directory to ensure
+all files are owned by user <emphasis>root</emphasis>.</para>
 </sect2>
 
@@ -182,9 +191,9 @@
 <listitem>
 <indexterm zone="ch-bootable-kernel kernel"><primary sortas="b-kernel">kernel</primary></indexterm>
-<para>is the engine of your Linux system.
-When switching on your box, the kernel is the first part of your operating
-system that gets loaded. It detects and initializes all the components of your
-computer's hardware, then makes these components available as a tree of files
-to the software, and turns a single CPU into a multi-tasking machine capable
+<para>the engine of the Linux system. When turning on your 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
 of running scores of programs seemingly at the same time.</para>
 </listitem>
@@ -195,9 +204,10 @@
 <listitem>
 <indexterm zone="ch-bootable-kernel kernel-headers"><primary sortas="e-kernel-headers">kernel headers</primary></indexterm>
-<para>define the interface to the
-services that the kernel provides. The headers in your system's
-<filename class="directory">include</filename> directory should <emphasis>always</emphasis> be
-the ones against which Glibc was compiled and should therefore
-<emphasis>not</emphasis> be replaced when upgrading the kernel.</para>
+<para>defines the interface to the services that the kernel provides.
+The headers in your system's <filename
+class="directory">include</filename> directory should
+<emphasis>always</emphasis> be the ones against which Glibc was
+compiled and therefore, should <emphasis>not</emphasis> be replaced
+when upgrading the kernel.</para>
 </listitem>
 </varlistentry>
@@ -207,6 +217,7 @@
 <listitem>
 <indexterm zone="ch-bootable-kernel System.map"><primary sortas="e-/boot/System.map">/boot/System.map</primary></indexterm>
-<para>is a list of addresses and symbols. It maps the entry points and addresses 
-of all the functions and data structures in the kernel.</para>
+<para>is a list of addresses and symbols. It maps the entry points and
+addresses of all the functions and data structures in the
+kernel.</para>
 </listitem>
 </varlistentry>
@@ -216,2 +227,3 @@
 
 </sect1>
+
