Index: docs/libvir.html =================================================================== RCS file: /data/cvs/libvirt/docs/libvir.html,v retrieving revision 1.109 diff -u -r1.109 libvir.html --- docs/libvir.html 3 Mar 2008 14:42:37 -0000 1.109 +++ docs/libvir.html 7 Mar 2008 09:41:16 -0000 @@ -4119,7 +4119,7 @@
/dev/
may seem
like the logical choice, however, devices nodes there are not
guarenteed stable across reboots, since they are allocated on
@@ -4209,7 +4209,7 @@
/dev/
may seem
like the logical choice, however, devices nodes there are not
guarenteed stable across reboots, since they are allocated on
Index: docs/storage.html
===================================================================
RCS file: /data/cvs/libvirt/docs/storage.html,v
retrieving revision 1.3
diff -u -r1.3 storage.html
--- docs/storage.html 3 Mar 2008 14:42:37 -0000 1.3
+++ docs/storage.html 7 Mar 2008 09:41:16 -0000
@@ -84,7 +84,7 @@
is not applicable when creating a pool./dev/
may seem
like the logical choice, however, devices nodes there are not
-guarenteed stable across reboots, since they are allocated on
-demand. It is preferrable to use a stable location such as one
+guaranteed stable across reboots, since they are allocated on
+demand. It is preferable to use a stable location such as one
of the /dev/disk/by-{path,id,uuid,label
locations.
device
element
within the source
element may contain information
-about its avilable extents. Some pools have a constraint that
+about its available extents. Some pools have a constraint that
a volume must be allocated entirely within a single constraint
(eg disk partition pools). Thus the extent information allows an
application to determine the maximum possible size for a new
@@ -212,10 +212,10 @@
/dev/
may seem
like the logical choice, however, devices nodes there are not
-guarenteed stable across reboots, since they are allocated on
+guaranteed stable across reboots, since they are allocated on
demand. It is preferrable to use a stable location such as one
of the /dev/disk/by-{path,id,uuid,label
locations.
When listing existing volumes all these formats are supported
natively. When creating new volumes, only a subset may be
-available. The raw
type is guarenteed always
+available. The raw
type is guaranteed always
available. The qcow2
type can be created if
either qemu-img
or qcow-create
tools
-are present. The others are dependant on support of the
+are present. The others are dependent on support of the
qemu-img
tool.
-The fileystem pool supports the following formats: +The filesystem pool supports the following formats:
auto
- automatically determine format-The network fileystem pool supports the following formats: +The network filesystem pool supports the following formats:
auto
- automatically determine format