readme: fix typos

[pve-docs.git] / pct.adoc

diff --git a/pct.adoc b/pct.adoc
index 14e2d3781b577ab3f3b26ff5966baa1cd24f9b13..9983ba8e03544ed2823100dce28b220438b968c2 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -391,7 +391,7 @@ inside a container. Some potential use cases are:
 
 - Accessing your home directory in the guest
 - Accessing an USB device directory in the guest
-- Accessing an NFS mount from in the host in the guest
+- Accessing an NFS mount from the host in the guest
 
 Bind mounts are considered to not be managed by the storage subsystem, so you
 cannot make snapshots or deal with quotas from inside the container. With
@@ -418,8 +418,15 @@ achieve the same result.
 Device mount points
 ^^^^^^^^^^^^^^^^^^^
 
-Similar to bind mounts, device mounts are not managed by the storage, but for
-these the `quota` and `acl` options will be honored.
+Device mount points allow to mount block devices of the host directly into the
+container. Similar to bind mounts, device mounts are not managed by {PVE}'s
+storage subsystem, but the `quota` and `acl` options will be honored.
+
+NOTE: Device mount points should only be used under special circumstances. In
+most cases a storage backed mount point offers the same performance and a lot
+more features.
+
+NOTE: The contents of device mount points are not backed up when using 'vzdump'.
 
 
 FUSE mounts