Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 3df86b6699190f9397c74c4f8b10ebd603ae5168)
+++ postlfs/config/bootdisk.xml	(revision 8604d92fe917953b5914e27de66769a9eb02c98c)
@@ -149,5 +149,5 @@
 
 <para><parameter>bs=1k count=4096</parameter>: These parameters tell
-<filename>dd</filename> to read and write in "chunks" of 1024 bytes and
+<command>dd</command> to read and write in "chunks" of 1024 bytes and
 process 4096 "chunks".</para>
 
@@ -157,5 +157,5 @@
 the version of <command>mount</command> (older ones don't have the
 <userinput>-o loop</userinput> option) or if <filename>/etc/mtab</filename>
-is symlinked to <filename>/proc</filename> (which causes mount to be
+is symlinked to <filename class="directory">/proc</filename> (which causes mount to be
 unable to properly "unbind" a loop device, due to "lost" information).
 An alternate set of commands is provided, after these three commands,
@@ -186,5 +186,5 @@
 <option>-o loop</option> option <emphasis>and</emphasis> your
 <filename>/etc/mtab</filename> is a real file, rather than a symlink to
-<filename>/proc</filename>, the three above commands can be replaced
+<filename class="directory">/proc</filename>, the three above commands can be replaced
 by these next two commands.</para>
 
@@ -204,5 +204,5 @@
 command tells <command>mount</command> to bind the named file to a
 loopback device it automatically selects (the first available) and mount
-the device on <filename>/mnt/loop1</filename>.</para>
+the device on <filename class="directory">/mnt/loop1</filename>.</para>
 
 <para><emphasis>Add components to the file system</emphasis></para>
@@ -210,5 +210,5 @@
 <para><emphasis>A cautionary note:</emphasis> if you are not running in a
 <command>chroot</command> environment, be sure that you do not accidently
-omit the <filename>/mnt/loop1</filename> reference in the commands. If
+omit the <filename class="directory">/mnt/loop1</filename> reference in the commands. If
 you do so, you might replace the equivalent components on your host with
 the components that are installed by these procedures.  Even if you are
@@ -258,5 +258,5 @@
 &nbsp;&nbsp;/mnt/loop1/dev</command></userinput></screen>
 
-<para><emphasis>What is needed in the <filename>/etc</filename>
+<para><emphasis>What is needed in the <filename class="directory">/etc</filename>
 directory</emphasis></para>
 
@@ -276,5 +276,5 @@
 diskette to carry these files.</para>
 
-<para>Some might like to copy their <filename>/etc/rc*</filename>
+<para>Some might like to copy their <filename class="directory">/etc/rc*</filename>
 directory into the ramdisk image, but this may have no value, other
 than archival use, in a worst-case recovery scenario.  If you want
@@ -298,5 +298,5 @@
 <command>noauto</command> in the options field so they don't cause an
 attempt to mount a potentially corrupt partition.  Copy it to
-<filename>/tmp</filename>, edit it as desired and then:</para>
+<filename class="directory">/tmp</filename>, edit it as desired and then:</para>
 
 <screen><userinput><command>cp -a /tmp/fstab /mnt/loop1/etc</command></userinput></screen>
@@ -309,10 +309,10 @@
 control to <command>linuxrc</command> (<application><ulink
 url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox
-</ulink></application>).  It wants to run an <filename>/etc/init.d/rcS</filename>
+</ulink></application>).  It wants to run an <filename class="directory">/etc/init.d/rcS</filename>
 script to do any initial setup.</para>
 
 <para>If you use devfsd, you will need to set up the
 <filename>rcS</filename> script to handle the devfsd startup.  Put the
-following commands in <filename>/mnt/loop1/etc/init.d/rcS</filename>.
+following commands in <filename class="directory">/mnt/loop1/etc/init.d/rcS</filename>.
 You may also want to add some of the processes shown in the non-devfs
 version that follows.</para>
@@ -322,5 +322,6 @@
 /sbin/devfsd /dev</userinput></screen>
 
-<para>If you don't use devfsd, but created a static <filename>/dev</filename> 
+<para>If you don't use devfsd, but created a static <filename
+class="directory">/dev</filename> 
 directory using <command>MAKEDEV</command>, or any similar process, the
 <filename>rcS</filename> script will do slightly different things.
@@ -329,5 +330,5 @@
 files, thus saving space on the diskette.</para>
 
-<para>The script made next will mount <filename>/proc</filename>, turn
+<para>The script made next will mount <filename class="directory">/proc</filename>, turn
 on swap (no harm is done if it fails), make the
 <filename>/etc/passwd</filename> and <filename>/etc/group</filename>
@@ -533,5 +534,5 @@
 
 <para>To make a single-floppy rescue, using devfs, use the following
-commands. If you use the static <filename>/dev</filename> setup, use
+commands. If you use the static <filename class="directory">/dev</filename> setup, use
 <filename>/dev/fd0</filename> instead of the /dev/floppy/0.</para>
 
@@ -545,5 +546,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
-<userinput>0,0</userinput> gives it "no value", telling the kernel to not
+<option>0,0</option> 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
@@ -588,5 +589,5 @@
 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>/dev</filename>
+of your kernel image. 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>
