Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 7b3d96c93f96edf9985f6e2a0aadcecbbe980462)
+++ postlfs/config/bootdisk.xml	(revision 78b3cd61eb5836b5c75f20dcb5efd2804a5a6994)
@@ -66,8 +66,8 @@
 <para>You should make a custom kernel that includes only those features
 needed to rescue your system, so it will have the least size.  No
-sense in building in support for things like <command>xfree86</command>,
-<command>dri</command>, etc, as most rescues are performed from the
-command prompt.  Along the same lines, if you have GCC-2.95.*, it is
-known to produce smaller kernels.  So you might want to use that
+sense in building in support for things like <application>xfree86</application>,
+<application>dri</application>, etc, as most rescues are performed from the
+command prompt.  Along the same lines, if you have <xref linkend="gcc2"/>, it 
+is known to produce smaller kernels.  So you might want to use that
 compiler for this kernel.  If you do so, don't overlook any loadable
 modules (which are not addressed here) you might need - they need to be
@@ -84,11 +84,10 @@
 components shown in this document, you will need a kernel that is 643 or
 fewer blocks in size.  If you want the optional programs - a very basic
-editor, like ed, and rudimentary disk partitioning, like sfdisk - the
-kernel will need to be 595 or fewer blocks in size.  This should not be
-a major problem unless your needs are fairly esoteric.  On the system
-used to develop this version of the procedures, using only ext2 file
-systems and not using networking or CDs for recovery, the kernel image
-is only 481 blocks.  And there may be more to gain - it has not been
-closely examined for additional gains.</para>
+editor, like <command>ed</command>, and rudimentary disk partitioning, like 
+<command>sfdisk</command> - the kernel will need to be 595 or fewer blocks in 
+size.  This should not be a major problem unless your needs are fairly 
+esoteric.  On the system used to develop this version of the procedures, using 
+only ext2 file systems and not using networking or <acronym>CD</acronym>s for 
+recovery, the kernel image is only 481 blocks.  And there may be more to gain - it has not been closely examined for additional gains.</para>
 
 <para>This kernel image will be called "rescueimage" hereinafter. You
@@ -134,6 +133,6 @@
 system</emphasis></para>
 
-<screen><userinput><command>mkdir -p /mnt/loop1</command>
-<command>dd if=/dev/zero of=/tmp/rfloppy bs=1k count=4096</command></userinput></screen>
+<screen><userinput><command>mkdir -p /mnt/loop1
+dd if=/dev/zero of=/tmp/rfloppy bs=1k count=4096</command></userinput></screen>
 
 <para><emphasis>Command explanations</emphasis></para>
@@ -163,7 +162,7 @@
 that you can use if you don't have either of these situations.</para>
 
-<screen><userinput><command>losetup /dev/loop1 /tmp/rfloppy</command>
-<command>mke2fs -m 0 -N 504 /dev/loop1</command>
-<command>mount -t ext2 /dev/loop1 /mnt/loop1</command></userinput></screen>
+<screen><userinput><command>losetup /dev/loop1 /tmp/rfloppy
+mke2fs -m 0 -N 504 /dev/loop1
+mount -t ext2 /dev/loop1 /mnt/loop1</command></userinput></screen>
 
 <para><emphasis>Command explanations</emphasis></para>
@@ -190,6 +189,6 @@
 by these next two commands.</para>
 
-<screen><userinput><command>mke2fs -F -m 0 -N 504 /tmp/rfloppy</command>
-<command>mount -o loop /tmp/rfloppy /mnt/loop1</command></userinput></screen>
+<screen><userinput><command>mke2fs -F -m 0 -N 504 /tmp/rfloppy
+mount -o loop /tmp/rfloppy /mnt/loop1</command></userinput></screen>
 
 <para><emphasis>Command explanations</emphasis></para>
@@ -220,6 +219,6 @@
 <para>First, to have as much free space as possible, remove the
 <filename>lost+found</filename> directory, which is not needed because
-it is only used by fsck.  Since fsck will never be run on this file
-system, it is unneeded.
+it is only used by <command>fsck</command>.  Since <command>fsck</command> 
+will never be run on this file system, it is unneeded.
 
 <screen><userinput><command>rmdir /mnt/loop1/lost+found/</command></userinput></screen></para>
@@ -323,6 +322,6 @@
 /sbin/devfsd /dev</userinput></screen>
 
-<para>If you don't use devfsd, but created a static /dev/directory
-using <command>MAKEDEV</command>, or any similar process, the
+<para>If you don't use devfsd, but created a static <filename>/dev</filename> 
+directory using <command>MAKEDEV</command>, or any similar process, the
 <filename>rcS</filename> script will do slightly different things.
 Also, don't forget that it is creating the
@@ -442,5 +441,6 @@
 it is not what is considered to be "user friendly".  But the
 <command>fdisk</command> and <command>cfdisk</command> programs are
-substantially larger or require more shared objects, like ncurses.</para>
+substantially larger or require more shared objects, like <application>ncurses
+</application>.</para>
 
 <para>The second utility is an editor.  Most graphical editors are
@@ -473,6 +473,5 @@
 strip -p --strip-unneeded --remove-section=.comment \
     -o /mnt/loop1/bin/ed /bin/ed
-chmod 555 /mnt/loop1/sbin/sfdisk /mnt/loop1/bin/ed
-</command></userinput></screen>
+chmod 555 /mnt/loop1/sbin/sfdisk /mnt/loop1/bin/ed</command></userinput></screen>
 
 <para>Also, keeping in mind your space limitations, copy any other
@@ -500,6 +499,5 @@
 strip -p --strip-unneeded --remove-section=.comment \
 &nbsp;&nbsp;&nbsp;&nbsp;-o /mnt/loop1/lib/libdl.so.2 /lib/libdl-2.3.2.so &amp;&amp;
-chmod 555 /mnt/loop1/lib/{libc.so.6,ld-linux.so.2,libdl.so.2}
-</command></userinput></screen>  
+chmod 555 /mnt/loop1/lib/{libc.so.6,ld-linux.so.2,libdl.so.2}</command></userinput></screen>  
 
 <para>Note that the above commands change the names of the libraries,
@@ -511,5 +509,5 @@
 
 <para>Unmount the loopback file.  If you used <command>mount</command>'s
-<command>-o loop</command> option, the "bond" between the loop device
+<userinput>-o loop</userinput> option, the "bond" between the loop device
 and the file will be removed when the unmount is done.  Just omit the
 <command>losetup -d /dev/loop1</command> from the following
@@ -521,6 +519,5 @@
 losetup -d /dev/loop1 &amp;&amp;  # Omit if mount's -o loop was used
 gzip -9 &lt; /tmp/rfloppy &gt; /tmp/rootfs.gz
-ls -l /tmp/rootfs.gz
-</command></userinput></screen>  
+ls -l /tmp/rootfs.gz</command></userinput></screen>  
 
 <para><emphasis>Join a kernel image and initrd onto a diskette</emphasis></para>
@@ -539,6 +536,6 @@
 <filename>/dev/fd0</filename> instead of the /dev/floppy/0.</para>
 
-<screen><userinput><command>dd if=rescueimage of=/dev/floppy/0 bs=1k</command>
-<command>rdev /dev/floppy/0 0,0
+<screen><userinput><command>dd if=rescueimage of=/dev/floppy/0 bs=1k
+rdev /dev/floppy/0 0,0
 rdev -R /dev/floppy/0 0</command></userinput></screen>
 
@@ -548,5 +545,5 @@
 the kernel will use when it boots. Because it loads an initrd, it will
 automatically set that as the root device, initially. So, the
-<command>0,0</command> gives it "no value", telling the kernel to not
+<userinput>0,0</userinput> gives it "no value", telling the kernel to not
 mount any other device. Some folks give <filename>/dev/fd0</filename> or
 something similar. But this has effect <emphasis>only</emphasis> when
