[virtualization-guide] Trivial fix of busted tags.
Justin Clift
justinclift at fedoraproject.org
Fri Jun 11 07:21:27 UTC 2010
commit 9058f83b8506e694b3d62c72c044f204de599450
Author: Justin Clift <justin at salasaga.org>
Date: Fri Jun 11 17:21:09 2010 +1000
Trivial fix of busted tags.
en-US/Storage_Pools_Partitions.xml | 66 ++++++++++++++++++++---------------
1 files changed, 38 insertions(+), 28 deletions(-)
---
diff --git a/en-US/Storage_Pools_Partitions.xml b/en-US/Storage_Pools_Partitions.xml
index 2cfa17e..9a07ae1 100644
--- a/en-US/Storage_Pools_Partitions.xml
+++ b/en-US/Storage_Pools_Partitions.xml
@@ -69,34 +69,44 @@
<para>
Change the <guibutton>Target Path</guibutton>, <guibutton>Format</guibutton>, and <guibutton>Source Path</guibutton> fields.
</para>
- <varlistentry><term><name>guest_images_disk</name></term><listitem>
- <para>
- The <parameter>name</parameter> parameter determines the name of the storage pool. This example uses the name <replaceable>guest_images_disk</replaceable> in the example below.
- </para>
- </listitem></varlistentry>
- <varlistentry><term> <device path='<replaceable>/dev/sdb</replaceable>'/></term>
- <listitem>
- <para>
- The <parameter>device</parameter> parameter with the <parameter>path</parameter> attribute
- specifies the device path of the storage device. This example uses the device <replaceable>/dev/sdb</replaceable> .
- </para>
- </listitem></varlistentry>
- <varlistentry><term><target> <path><replaceable>/dev</replaceable></path></term>
- <listitem>
- <para>
- The file system <parameter>target</parameter> parameter with the <parameter>path</parameter> sub-parameter determines the location on the host file system to attach volumes created with this this storage pool.
- </para>
- <para>
- For example, sdb1, sdb2, sdb3. Using <replaceable>/dev/</replaceable>, as in the example below, means volumes created from this storage pool can be accessed as <replaceable>/dev</replaceable>/sdb1, <replaceable>/dev</replaceable>/sdb2, <replaceable>/dev</replaceable>/sdb3.
- </para>
- </listitem></varlistentry>
- <varlistentry><term><format type='<replaceable>gpt</replaceable>'/></term>
- <listitem>
- <para>
- The <parameter>format</parameter> parameter specifies the partition table type. his example uses the <replaceable>gpt</replaceable> in the example below, to match the GPT disk label type created in the previous step.
- </para>
- </listitem></varlistentry>
- </variablelist>
+ <variablelist>
+ <varlistentry>
+ <term><name>guest_images_disk</name></term>
+ <listitem>
+ <para>
+ The <parameter>name</parameter> parameter determines the name of the storage pool. This example uses the name <replaceable>guest_images_disk</replaceable> in the example below.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term> <device path='<replaceable>/dev/sdb</replaceable>'/></term>
+ <listitem>
+ <para>
+ The <parameter>device</parameter> parameter with the <parameter>path</parameter> attribute
+ specifies the device path of the storage device. This example uses the device <replaceable>/dev/sdb</replaceable> .
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><target> <path><replaceable>/dev</replaceable></path></term>
+ <listitem>
+ <para>
+ The file system <parameter>target</parameter> parameter with the <parameter>path</parameter> sub-parameter determines the location on the host file system to attach volumes created with this this storage pool.
+ </para>
+ <para>
+ For example, sdb1, sdb2, sdb3. Using <replaceable>/dev/</replaceable>, as in the example below, means volumes created from this storage pool can be accessed as <replaceable>/dev</replaceable>/sdb1, <replaceable>/dev</replaceable>/sdb2, <replaceable>/dev</replaceable>/sdb3.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><format type='<replaceable>gpt</replaceable>'/></term>
+ <listitem>
+ <para>
+ The <parameter>format</parameter> parameter specifies the partition table type. his example uses the <replaceable>gpt</replaceable> in the example below, to match the GPT disk label type created in the previous step.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<!--<itemizedlist>
More information about the docs-commits
mailing list