Fix PVE API URL

[pve-docs.git] / pve-storage-dir.adoc

diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc
index acfe7c66811b57a78d5f277315d9a8a64815168d..99f61cbcfbf10400fa72da59c528c0afdd97cb0d 100644 (file)
--- a/pve-storage-dir.adoc
+++ b/pve-storage-dir.adoc
@@ -1,5 +1,6 @@
 Directory Backend
 -----------------
+include::attributes.txt[]
 
 Storage pool type: `dir`
 
@@ -14,16 +15,16 @@ can use any file system supported by Linux.
 
 This backend assumes that the underlying directory is POSIX
 compatible, but nothing else. This implies that you cannot create
-snapshots at the storage level. But there exists a woraround for VM
+snapshots at the storage level. But there exists a workaround for VM
 images using the `qcow2` file format, because that format supports
 snapshots internally.
 
-TIP: Some storage types does not support `O_DIRECT`, so you can't use
+TIP: Some storage types do not support `O_DIRECT`, so you can't use
 cache mode `none` with such storages. Simply use cache mode
 `writeback` instead.
 
 We use a predefined directory layout to store different content types
-into different sub-directories. This layout is use by all file level
+into different sub-directories. This layout is used by all file level
 storage backends.
 
 .Directory layout
@@ -69,8 +70,8 @@ This specifies the owner VM.
 
 `<NAME>`::
 
-This scan be an arbitrary name (`ascii`) without white spaces. The
-backend uses `disk[N]` as default, where `[N]` is replaced by an
+This can be an arbitrary name (`ascii`) without white spaces. The
+backend uses `disk-[N]` as default, where `[N]` is replaced by an
 integer to make the name unique.
 
 `<FORMAT>`::
@@ -78,19 +79,19 @@ integer to make the name unique.
 Species the image format (`raw|qcow2|vmdk`).
 
 When you create a VM template, all VM images are renamed to indicate
-that they are now read-only, and can be uses as base image for clones:
+that they are now read-only, and can be uses as a base image for clones:
 
  base-<VMID>-<NAME>.<FORMAT>
 
 NOTE: Such base images are used to generate cloned images. So it is
-important that those files are read-only, and never gets modified. The
-backend changes access mode to `0444`, and sets the immutable flag
+important that those files are read-only, and never get modified. The
+backend changes the access mode to `0444`, and sets the immutable flag
 (`chattr +i`) if the storage supports that.
 
 Storage Features
 ~~~~~~~~~~~~~~~~
 
-As mentioned above, most file systems does not support snapshots out
+As mentioned above, most file systems do not support snapshots out
 of the box. To workaround that problem, this backend is able to use
 `qcow2` internal snapshot capabilities.
 
@@ -112,7 +113,7 @@ Please use the following command to allocate a 4GB image on storage `local`:
 
  # pvesm alloc local 100 vm-100-disk10.raw 4G
  Formatting '/var/lib/vz/images/100/vm-100-disk10.raw', fmt=raw size=4294967296
- sucessfuly created 'local:100/vm-100-disk10.raw'
+ successfully created 'local:100/vm-100-disk10.raw'
 
 NOTE: The image name must conform to above naming conventions.
 
@@ -125,3 +126,14 @@ And you can remove the image with:
 
  # pvesm free local:100/vm-100-disk10.raw
 
+
+ifdef::wiki[]
+
+See Also
+~~~~~~~~
+
+* link:/wiki/Storage[Storage]
+
+endif::wiki[]
+
+