release-notes/devel/en_US FileSystems.xml,1.8,1.9

[Karsten Wade (kwade)]

Author: kwade

Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25680

Modified Files:
	FileSystems.xml 
Log Message:
XML fixes to match test3 usage.


Index: FileSystems.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/FileSystems.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- FileSystems.xml	25 Sep 2006 07:43:26 -0000	1.8
+++ FileSystems.xml	26 Sep 2006 10:00:34 -0000	1.9
@@ -10,8 +10,8 @@
   <para>
     Fedora Core 6 provides basic support for encrypted swap partitions
     and non-root file systems. To use it, add entries to
-    <code>/etc/crypttab</code> and reference the created devices in
-    <code>/etc/fstab</code>.
+    <filename>/etc/crypttab</filename> and reference the created devices in
+    <filename>/etc/fstab</filename>.
   </para>
 
   <para>
@@ -25,7 +25,7 @@
   </para>
 
   <para>
-    The following example shows an <code>/etc/crypttab</code> entry for a
+    The following example shows an <filename>/etc/crypttab</filename> entry for a
     swap partition:
   </para>
 
@@ -33,43 +33,43 @@
 ]]></screen>
 
   <para>
-    This creates an encrypted block device
-    <code>/dev/mapper/my_swap</code>, which can be referenced in
-    <code>/etc/fstab</code>. The next example shows an entry for a
-    filesystem volume:
+    This creates an encrypted block device <filename
+      class="devicefile">/dev/mapper/my_swap</filename>, which can be
+    referenced in <filename>/etc/fstab</filename>. The next example
+    shows an entry for a filesystem volume:
   </para>
 
 <screen><![CDATA[my_volume /dev/hda5 /etc/volume_key cipher=aes-cbc-essiv:sha256 
 ]]></screen>
 
   <para>
-    The <code>/etc/volume_key</code> file contains a plaintext
-    encryption key. You can also specify <code>none</code> as the key
-    file name, and the system instead asks for the encryption key during
-    boot.
+    The <filename>/etc/volume_key</filename> file contains a plaintext
+    encryption key. You can also specify <option>none</option> as the
+    key file name, and the system instead asks for the encryption key
+    during boot.
   </para>
 
   <para>
     The recommended method is to use
-    <emphasis role='strong'>LUKS</emphasis> for file system volumes:
+    <application>LUKS</application> for file system volumes:
   </para>
 
   <itemizedlist>
     <listitem>
       <para>
-        Create the encrypted volume using <code>cryptsetup
-        luksFormat</code>
+        Create the encrypted volume using <command>cryptsetup
+        luksFormat</command>
       </para>
     </listitem>
     <listitem>
       <para>
-        Add the necessary entry to <code>/etc/crypttab</code>
+        Add the necessary entry to <filename>/etc/crypttab</filename>
       </para>
     </listitem>
     <listitem>
       <para>
-        Set up the volume manually using <code>cryptsetup
-        luksOpen</code> or reboot
+        Set up the volume manually using <command>cryptsetup
+        luksOpen</command> or reboot
       </para>
     </listitem>
     <listitem>
@@ -79,7 +79,7 @@
     </listitem>
     <listitem>
       <para>
-        Set up an <code>/etc/fstab</code> entry
+        Set up an <filename>/etc/fstab</filename> entry
       </para>
     </listitem>
   </itemizedlist>