Index: chapter07/bootscripts.xml
===================================================================
--- chapter07/bootscripts.xml	(revision 07da7ec07dacb3888288e9991520742125bcd7b0)
+++ chapter07/bootscripts.xml	(revision aabd480689b6c9bd4b28ee66c1cfa3b7a717a334)
@@ -11,5 +11,6 @@
 
 <sect2 role="package"><title/>
-<para>The LFS-Bootscripts package contains a set of bootscripts.</para>
+<para>The LFS-Bootscripts package contains a set of scripts to start/stop the
+LFS system at bootup/shutdown.</para>
 
 <segmentedlist>
@@ -34,5 +35,5 @@
 </sect2>
 
-<sect2 id="contents-bootscripts" role="content"><title>Contents of LFS-bootscripts</title>
+<sect2 id="contents-bootscripts" role="content"><title>Contents of LFS-Bootscripts</title>
 
 <segmentedlist>
Index: chapter07/introduction.xml
===================================================================
--- chapter07/introduction.xml	(revision 07da7ec07dacb3888288e9991520742125bcd7b0)
+++ chapter07/introduction.xml	(revision aabd480689b6c9bd4b28ee66c1cfa3b7a717a334)
@@ -8,8 +8,8 @@
 <?dbhtml filename="introduction.html"?>
 
-<para>This chapter details how to install the bootscripts and set them up
-properly. Most of these scripts will work without modification, but a
-few require additional configuration files because they deal with
-hardware-dependent information.</para>
+<para>This chapter details how to install and configure the LFS-Bootscripts
+package. Most of these scripts will work without modification, but a few require
+additional configuration files because they deal with hardware-dependent
+information.</para>
 
 <para>System-V style init scripts are employed in this book because they are
Index: chapter07/network.xml
===================================================================
--- chapter07/network.xml	(revision 07da7ec07dacb3888288e9991520742125bcd7b0)
+++ chapter07/network.xml	(revision aabd480689b6c9bd4b28ee66c1cfa3b7a717a334)
@@ -55,11 +55,10 @@
 network script and not brought up.</para>
 
-<para>The <envar>SERVICE</envar> variable defines the method of
-obtaining the IP address. The LFS bootscripts have a modular IP
-assignment format, and creating additional files in the <filename
-class="directory" condition="html">/etc/sysconfig/network-devices/services</filename>
-<filename class="directory" condition="pdf">/etc/sysconfig/network- devices/services</filename>
-directory allows other IP assignment methods. This is commonly used
-for Dynamic Host Configuration Protocol (DHCP), which is addressed in the BLFS book.</para>
+<para>The <envar>SERVICE</envar> variable defines the method of 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
+allows other IP assignment methods. This is commonly used for Dynamic Host
+Configuration Protocol (DHCP), which is addressed in the BLFS book.</para>
 
 <para>The <envar>GATEWAY</envar> variable should contain
Index: chapter07/udev.xml
===================================================================
--- chapter07/udev.xml	(revision 07da7ec07dacb3888288e9991520742125bcd7b0)
+++ chapter07/udev.xml	(revision aabd480689b6c9bd4b28ee66c1cfa3b7a717a334)
@@ -83,25 +83,22 @@
 processes and to <command>udev</command> for device node creation.</para>
 
-<para>The <command>S10udev</command> initscript takes care of creating
-these device nodes when Linux is booted. This script starts with
-registering <command>/sbin/udevsend</command> as a hotplug event handler.
-Hotplug events (discussed below) should not be generated during this
-stage, but <command>udev</command> is registered just in case they do
-occur.  The <command>udevstart</command> program then walks through
-the <systemitem class="filesystem">/sys</systemitem> filesystem and
-creates devices under <filename class="directory">/dev</filename> that
-match the descriptions.  For example,
-<filename>/sys/class/tty/vcs/dev</filename> contains the string
-<quote>7:0</quote> This string is used by <command>udevstart</command>
-to create <filename>/dev/vcs</filename> with major number
-<emphasis>7</emphasis> and minor <emphasis>0</emphasis>.  The names and
-permissions of the nodes created under the
-<filename class="directory">/dev</filename> directory are configured according
-to the rules specified in the files within the
-<filename class="directory">/etc/udev/rules.d/</filename> directory.  These are
-numbered in a similar fashion to the LFS bootscripts.  If
-<command>udev</command> can't find a rule for the device it is creating, it will
-default permissions to <emphasis>660</emphasis> and ownership to
-<emphasis>root:root</emphasis>.</para>
+<para>The <command>S10udev</command> initscript takes care of creating these
+device nodes when Linux is booted. This script starts with registering
+<command>/sbin/udevsend</command> as a hotplug event handler.  Hotplug events
+(discussed below) should not be generated during this stage, but
+<command>udev</command> is registered just in case they do occur.  The
+<command>udevstart</command> program then walks through the <systemitem
+class="filesystem">/sys</systemitem> filesystem and creates devices under
+<filename class="directory">/dev</filename> that match the descriptions.  For
+example, <filename>/sys/class/tty/vcs/dev</filename> contains the string
+<quote>7:0</quote> This string is used by <command>udevstart</command> to create
+<filename>/dev/vcs</filename> with major number <emphasis>7</emphasis> and minor
+<emphasis>0</emphasis>.  The names and permissions of the nodes created under
+the <filename class="directory">/dev</filename> directory are configured
+according to the rules specified in the files within the <filename
+class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in
+a similar fashion to the LFS-Bootscripts package. If <command>udev</command>
+can't find a rule for the device it is creating, it will default permissions to
+<emphasis>660</emphasis> and ownership to <emphasis>root:root</emphasis>.</para>
 
 <para>Once the above stage is complete, all devices that were already
