Index: basicnet/netprogs/ncpfs/ncpfs-inst.xml
===================================================================
--- basicnet/netprogs/ncpfs/ncpfs-inst.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ basicnet/netprogs/ncpfs/ncpfs-inst.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -4,9 +4,9 @@
 <para>Install <application><acronym>NCPFS</acronym></application> by running the following commands:</para>
 
-<para><screen><userinput>./configure --prefix=/usr --includedir=/usr/include \
+<screen><userinput>./configure --prefix=/usr --includedir=/usr/include \
     --mandir=/usr/share/man --datadir=/usr/share &amp;&amp;
 make &amp;&amp;
 make install &amp;&amp;
-make install-dev</userinput></screen></para>
+make install-dev</userinput></screen>
 
 </sect2>
Index: basicnet/netprogs/tcpwrappers/tcpwrappers-config.xml
===================================================================
--- basicnet/netprogs/tcpwrappers/tcpwrappers-config.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ basicnet/netprogs/tcpwrappers/tcpwrappers-config.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -12,8 +12,8 @@
 
 <para>Then perform the following edits on the
-<filename>/etc/inetd.conf</filename> configuration file:
+<filename>/etc/inetd.conf</filename> configuration file:</para>
 <screen><userinput>finger stream tcp nowait nobody /usr/sbin/in.fingerd in.fingerd</userinput></screen>
-becomes:
-<screen><userinput>finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd</userinput></screen></para>
+<para>becomes:</para>
+<screen><userinput>finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd</userinput></screen>
 
 <note><para>The finger server is used as an example here.</para></note>
Index: basicnet/netutils/traceroute/traceroute-exp.xml
===================================================================
--- basicnet/netutils/traceroute/traceroute-exp.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ basicnet/netutils/traceroute/traceroute-exp.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -11,6 +11,6 @@
 possible for all users to execute <command>traceroute</command>. For absolute 
 security, turn off the <acronym>SUID</acronym> bit in <command>traceroute</command>'s file 
-permissions with the command: 
-<screen><command>chmod 0755 /usr/sbin/traceroute</command></screen></para>
+permissions with the command:</para>
+<screen><command>chmod 0755 /usr/sbin/traceroute</command></screen>
 
 <para>The risk is that if a security problem such as a buffer overflow were 
@@ -26,6 +26,6 @@
 <acronym>SUID</acronym> root, then you 
 should move <filename>traceroute</filename> to <filename>/usr/bin</filename> 
-with the following command: 
-<screen><command>mv /usr/sbin/traceroute /usr/bin</command></screen></para>
+with the following command:</para>
+<screen><command>mv /usr/sbin/traceroute /usr/bin</command></screen>
 
 <para>This ensures that the binary is in the path for non-root users.</para>
Index: basicnet/textweb/w3m/w3m-inst.xml
===================================================================
--- basicnet/textweb/w3m/w3m-inst.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ basicnet/textweb/w3m/w3m-inst.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -5,8 +5,8 @@
 menu, mouse, cookie, and <acronym>SSL</acronym> support. Other models include:</para>
 
-<para><literallayout>baby   - bare minimum
+<literallayout>baby   - bare minimum
 little - color and menu support
 mouse  - color, menu, and mouse support
-cookie - color, menu, mouse, and cookie support</literallayout></para>
+cookie - color, menu, mouse, and cookie support</literallayout>
 
 <para>Install <application>w3m</application> by running the following commands:</para>
Index: gnome/config/config-core.xml
===================================================================
--- gnome/config/config-core.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ gnome/config/config-core.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -5,10 +5,9 @@
 
 <para>Create an <filename>.xinitrc</filename> file to start
-<application><acronym>GNOME</acronym></application>:
+<application><acronym>GNOME</acronym></application>:</para>
 <screen><userinput><command>echo "exec gnome-session" &gt;&gt;
 ~/.xinitrc</command></userinput></screen>
-and ensure all libraries can be found with:
+<para>and ensure all libraries can be found with:</para>
 <screen><userinput><command>ldconfig</command></userinput></screen>
-</para>
 
 <para>At this point you can bring up
Index: multimedia/cdwriteutils/kernel.xml
===================================================================
--- multimedia/cdwriteutils/kernel.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ multimedia/cdwriteutils/kernel.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -29,10 +29,9 @@
 your hardware.</para>
 
-<para>If necessary, recompile the kernel with
+<para>If necessary, recompile the kernel with</para>
 <screen>make CC=/opt/gcc-2.95.3/bin/gcc dep &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc bzImage &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc modules &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc modules_install</screen>
-</para>
 <para>
 Copy <filename>/usr/src/linux/arch/i386/boot/bzImage</filename> and
Index: multimedia/cdwriteutils/udftools/udftools-kernel-inst.xml
===================================================================
--- multimedia/cdwriteutils/udftools/udftools-kernel-inst.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ multimedia/cdwriteutils/udftools/udftools-kernel-inst.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -16,10 +16,9 @@
      UDF write support (DANGEROUS)       Y</screen>
 
-<para>If necessary, recompile the kernel with
+<para>If necessary, recompile the kernel with</para>
 <screen><userinput><command>make CC=/opt/gcc-2.95.3/bin/gcc dep &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc bzImage &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc modules &amp;&amp;
 make CC=/opt/gcc-2.95.3/bin/gcc modules_install</command></userinput></screen>
-</para>
 <para>
 Copy <filename>/usr/src/linux/arch/i386/boot/bzImage</filename> and
@@ -31,6 +30,6 @@
 
 <para>If you build packet writer as a module, add the following to
-<filename>/etc/modules.conf</filename>:
-<screen><userinput>alias block-major-97 pktcdvd</userinput></screen></para>
+<filename>/etc/modules.conf</filename>:</para>
+<screen><userinput>alias block-major-97 pktcdvd</userinput></screen>
 
 <para>Finally, create the packet driver device nodes in <filename
Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ postlfs/config/bootdisk.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -95,14 +95,14 @@
 instead in any commands that include "rescueimage".</para>
 
-<para>If you can not get your kernel down to the size needed to allow
+<para>If you can not get your rescueimage down to the size needed to allow
 all you need on the ramdisk image, don't fret.  You can always build a
 two diskette set, one boot and one root diskette.  The kernel will prompt
 you to insert the root file system diskette.  This will allow room for a
-compressed ramdisk image of 1440 blocks and a kernel of the same
+compressed ramdisk image of 1440 blocks and a rescueimage of the same
 size.</para>
 
-<para>The kernel size limits given above are likely to vary as
+<para>The rescueimage size limits given above are likely to vary as
 local system-specific configurations change.  Use them only as a
-guideline and not as gospel.  The size of the kernel image as shown by
+guideline and not as gospel.  The size of rescueimage as shown by
 <command>ls -sk</command> is only an approximation because of some
 "overhead".  On the system used to develop this version of these
@@ -124,5 +124,5 @@
 <listitem><para>add components to the file system</para></listitem>
 <listitem><para>make the compressed initrd</para></listitem>
-<listitem><para>join a kernel image and initrd onto a diskette</para></listitem>
+<listitem><para>join rescueimage and initrd onto a diskette</para></listitem>
 </itemizedlist>
 
@@ -238,5 +238,5 @@
 to minimize wasting space with unneeded inodes.</para>
 
-<para><emphasis>You must modify this to suit your kernel configuration and
+<para><emphasis>You must modify this to suit your rescueimage configuration and
 other needs.</emphasis>  For example, you may need
 <acronym>SCSI</acronym> devices and may not need
@@ -376,5 +376,5 @@
 basic utilities.  A file system package, like <application><ulink
 url="http://freshmeat.net/projects/e2fsprogs/">e2fsprogs</ulink></application>, or
-a package for the file system you are using will provide a minimal
+a package for the file system you are using, will provide a minimal
 set of utilities for file system checking and reconstruction.  The whole
 package will not be installed, but only certain needed components.</para>
@@ -438,5 +438,5 @@
 
 <para>There are two very useful utilities that any rescue disk should
-have to help in faster and more accurate recovery.  The first is a
+have, to help in faster and more accurate recovery.  The first is a
 partitioning utility.  The <command>sfdisk</command> program is
 used here because of its small size and great power.  Be warned though -
@@ -523,14 +523,15 @@
 ls -l /tmp/rootfs.gz</command></userinput></screen>  
 
-<para><emphasis>Join a kernel image and initrd onto a diskette</emphasis></para>
-
-<para>Now the kernel image and initial ramdisk image will be written to
+<para><emphasis>Join rescueimage and initrd onto a diskette</emphasis></para>
+
+<para>Now the rescueimage and initial ramdisk image will be written to
 the boot diskette.  Before doing this, calculate the number of blocks
-needed for the kernel and for the initrd, individually, by dividing each
+needed for rescueimage and for <filename>/tmp/rootfs.gz</filename>
+(the initial ramdisk), individually, by dividing each
 size by 1024 and adding one if there is any remainder.  Add these two
 results together.  They must total 1,440 or fewer blocks.  If they total
 more than this, don't worry too much.  Changes to make a two-diskette
 set are presented later.  Of course, you could reexamine your choices and
-try to shrink either the kernel or the initial ramdisk image.</para>
+try to shrink either the rescueimage or the initial ramdisk image.</para>
 
 <para>To make a single-floppy rescue, using devfs, use the following
@@ -572,23 +573,23 @@
 Make sure that this number, which may be different for you, matches your
 calculations from above.  You need to calculate a "magic number" now
-that will be inserted into the kernel image.  The value consists of three
+that will be inserted into rescueimage.  The value consists of three
 significant parts.  Two are discussed here.  The third is touched upon
 later.</para>
 
-<para>Bits 0 - 10 will contain the size of the kernel image, in blocks,
+<para>Bits 0 - 10 will contain the size of rescueimage, in blocks,
 that you calculated above, and which should match the results from the
 dd above. Bit 14 (the 15th bit, which is 2 to the 14th power, or 16,384)
 is a flag that, when set to 1, tells the kernel an initial ramdisk is to
 be loaded. So for the single-floppy rescue diskette, the two numbers
-16,384 and 481 (or whatever number is right for your kernel size) are
+16,384 and 481 (or whatever number is right for your rescueimage size) are
 added together to produce a decimal value, like 16865. This value is
-inserted into the proper place in the kernel image by the
+inserted into the proper place in rescueimage by the
 <command>rdev</command> command done next.</para>
 
-<para>Insert the "magic number" into the kernel image and then write the
-root file system right after the kernel on the floppy by executing the
+<para>Insert the "magic number" into rescueimage and then write the
+root file system right after rescueimage on the floppy by executing the
 following commands, with the proper numbers inserted. Notice that the
 <command>seek</command> parameter's number must be the size, in blocks,
-of your kernel image. If you use the static <filename class="directory">/dev</filename>
+of your rescueimage. If you use the static <filename class="directory">/dev</filename>
 setup, use <filename>/dev/fd0</filename> in the commands below, instead
 of <filename>/dev/floppy/0</filename>.</para>
@@ -598,5 +599,5 @@
 
 <para>In this command, <command>seek</command> was used to position to
-the block following the end of the kernel (480+1) and begin writing the
+the block following the end of the rescueimage (480+1) and begin writing the
 root file system to the floppy.</para>
 </sect3>
@@ -615,9 +616,9 @@
 <para>Modify the above instructions as follows. First a different magic
 number is needed. The 15th bit (bit 14) still needs to be set, but the
-size of the kernel image, in blocks, is replaced with a zero.  The third
+size of the rescueimage, in blocks, is replaced with a zero.  The third
 component, which was not discussed above, is now used. This is the 16th
 bit (bit 15) of the "magic number". When set, it tells the kernel to ask
 the user to insert the "root" floppy. It then loads the initrd image
-from that diskette.  Because the size of the kernel image was replaced
+from that diskette.  Because the size of the rescueimage was replaced
 by zero, the kernel starts loading from the "zero'th" block (the first
 one) on the second diskette.</para>
@@ -627,5 +628,5 @@
 value tells the kernel to prompt for, and then load, an initial ramdisk
 image from the first block on the inserted floppy.  So your first
-modification is to the command to write the "magic number" to the kernel
+modification is to the command to write the "magic number" to the rescueimage
 image on the diskette.</para>
 
Index: postlfs/config/compressdoc.xml
===================================================================
--- postlfs/config/compressdoc.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ postlfs/config/compressdoc.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -457,5 +457,5 @@
 file <filename>/etc/man.conf</filename>, as a
 <envar>MANPATH</envar>=<replaceable>/path</replaceable> section.</para>
-<para> Example:<screen><userinput>
+<para> Example:</para><screen><userinput>
     ...
     MANPATH=/usr/share/man
@@ -463,5 +463,5 @@
     MANPATH=/usr/X11R6/man
     MANPATH=/opt/qt/doc/man
-    ...</userinput></screen></para>
+    ...</userinput></screen>
 
 <para>Generally, package installation systems do not compress man/info pages, 
Index: postlfs/security/firewalling/busybox.xml
===================================================================
--- postlfs/security/firewalling/busybox.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ postlfs/security/firewalling/busybox.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -20,14 +20,14 @@
 simple and should still be acceptable from a security standpoint.
 Just add the following lines <emphasis>before</emphasis> the logging-rules 
-into the script.
+into the script.</para>
 
 <screen>iptables -A INPUT  -i ! ppp+  -j ACCEPT
-iptables -A OUTPUT -o ! ppp+  -j ACCEPT</screen></para>
+iptables -A OUTPUT -o ! ppp+  -j ACCEPT</screen>
 
 <para>If your daemons have to access the web themselves, like squid would need
-to, you could open OUTPUT generally and restrict INPUT.
+to, you could open OUTPUT generally and restrict INPUT.</para>
 
 <screen>iptables -A INPUT -m state --state ESTABLISHED,RELATED	-j ACCEPT
-iptables -A OUTPUT                                      -j ACCEPT</screen></para>
+iptables -A OUTPUT                                      -j ACCEPT</screen>
 
 <para>However, it is generally not advisable to leave OUTPUT unrestricted: you lose 
@@ -44,17 +44,17 @@
 <title>Have a look at the following examples:</title>
 
-<listitem><para>Squid is caching the web:
+<listitem><para>Squid is caching the web:</para>
 <screen>iptables -A OUTPUT -p tcp --dport 80                              -j ACCEPT
-iptables -A INPUT  -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT</screen></para></listitem>
+iptables -A INPUT  -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT</screen></listitem>
 
 <listitem><para>Your caching name server (e.g., dnscache) does its
-lookups via udp:
+lookups via udp:</para>
 <screen>iptables -A OUTPUT -p udp --dport 53                              -j ACCEPT
-iptables -A INPUT  -p udp --sport 53 -m state --state ESTABLISHED -j ACCEPT</screen></para></listitem>
+iptables -A INPUT  -p udp --sport 53 -m state --state ESTABLISHED -j ACCEPT</screen></listitem>
 
 <listitem><para>Alternatively, if you want to be able to ping your box to ensure
-it's still alive:
+it's still alive:</para>
 <screen>iptables -A INPUT  -p icmp -m icmp --icmp-type echo-request -j ACCEPT
-iptables -A OUTPUT -p icmp -m icmp --icmp-type echo-reply   -j ACCEPT</screen></para></listitem>
+iptables -A OUTPUT -p icmp -m icmp --icmp-type echo-reply   -j ACCEPT</screen></listitem>
 
 <listitem><para><anchor id='postlfs-security-fw-BB-4' xreflabel="example no. 4"/>If you are 
@@ -66,22 +66,22 @@
 
 <para>To avoid these delays you could reject the requests 
-with a 'tcp-reset':
+with a 'tcp-reset':</para>
 
 <screen>iptables -A INPUT  -p tcp --dport 113 -j REJECT --reject-with tcp-reset
-iptables -A OUTPUT -p tcp --sport 113 -m state --state RELATED -j ACCEPT</screen></para></listitem>
+iptables -A OUTPUT -p tcp --sport 113 -m state --state RELATED -j ACCEPT</screen></listitem>
 
 <listitem><para>To log and drop invalid packets, mostly harmless packets
-that came in after netfilter's timeout, sometimes scans:
+that came in after netfilter's timeout, sometimes scans:</para>
 
 <screen>iptables -I INPUT 1 -p tcp -m state --state INVALID -j LOG --log-prefix \ 
 "FIREWALL:INVALID"
-iptables -I INPUT 2 -p tcp -m state --state INVALID -j DROP</screen></para></listitem>
+iptables -I INPUT 2 -p tcp -m state --state INVALID -j DROP</screen></listitem>
 
 <listitem><para>Anything coming from the outside should not have a
-private address, this is a common attack called IP-spoofing:
+private address, this is a common attack called IP-spoofing:</para>
 
 <screen>iptables -t nat -A PREROUTING -i ppp+ -s 10.0.0.0/8     -j DROP
 iptables -t nat -A PREROUTING -i ppp+ -s 172.16.0.0/12	-j DROP
-iptables -t nat -A PREROUTING -i ppp+ -s 192.168.0.0/16	-j DROP</screen></para></listitem>
+iptables -t nat -A PREROUTING -i ppp+ -s 192.168.0.0/16	-j DROP</screen></listitem>
 
 <listitem><para>To simplify debugging and be fair to anyone who'd like to 
@@ -90,8 +90,8 @@
 
 <para>Obviously this must be done directly after logging as the very
-last lines before the packets are dropped by policy:
+last lines before the packets are dropped by policy:</para>
 
 <screen>iptables -A INPUT                        -j REJECT
-iptables -A OUTPUT -p icmp --icmp-type 3 -j ACCEPT</screen></para></listitem>
+iptables -A OUTPUT -p icmp --icmp-type 3 -j ACCEPT</screen></listitem>
 </itemizedlist>
 <!--</orderedlist>-->
Index: pst/sgml/docbook-dsssl/docbook-dsssl-config.xml
===================================================================
--- pst/sgml/docbook-dsssl/docbook-dsssl-config.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ pst/sgml/docbook-dsssl/docbook-dsssl-config.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -6,8 +6,7 @@
 <para>The following configuration is necessary in order to utilize
 <application>OpenJade</application> to convert the <acronym>BLFS</acronym> 
-Book from <acronym>XML</acronym> to <acronym>HTML</acronym>:
+Book from <acronym>XML</acronym> to <acronym>HTML</acronym>:</para>
 <screen><userinput><command>ln -sf <replaceable>[your home directory]</replaceable>/BLFS/BOOK/blfs.dsl \
 /usr/share/sgml/docbook/dsssl-stylesheets-&docbook-dsssl-version;/html/</command></userinput></screen>
-</para>
 
 <para>If you would like to test <application>Docbook <acronym>XML</acronym>
Index: server/other/cvsserver/cvsserver-inst.xml
===================================================================
--- server/other/cvsserver/cvsserver-inst.xml	(revision 27d830e47395304d5ac3bf880f0ac5d63e866c21)
+++ server/other/cvsserver/cvsserver-inst.xml	(revision a4acd463255bb560e798eb67f8f25ee602670921)
@@ -39,9 +39,9 @@
 <para>Test access to the <acronym>CVS</acronym> repository from a remote 
 machine using a user account that has <command>ssh</command> access to the 
-<acronym>CVS</acronym> server with the following commands:
+<acronym>CVS</acronym> server with the following commands:</para>
 <note><para>Replace <replaceable>[servername]</replaceable> with the 
 <acronym>IP</acronym> address or host name of the <acronym>CVS</acronym> 
 repository machine.  You will be prompted for the user's shell account password 
-before <acronym>CVS</acronym> checkout can continue.</para></note></para>
+before <acronym>CVS</acronym> checkout can continue.</para></note>
 
 
