totp: fix copy/paste mistake

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

diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index 72083b5abc3833c107712d8446a43f71bd4f036a..487aac61a60f5888d71245eb2a449e7ed1dc654d 100644 (file)
--- a/pve-storage-lvm.adoc
+++ b/pve-storage-lvm.adoc
@@ -1,3 +1,4 @@
+[[storage_lvm]]
 LVM Backend
 -----------
 ifdef::wiki[]
@@ -36,8 +37,11 @@ on a remote iSCSI server.
 
 `saferemove`::
 
-Zero-out data when removing LVs. When removing a volume, this makes
-sure that all data gets erased.
+Called "Wipe Removed Volumes" in the web UI. Zero-out data when removing LVs.
+When removing a volume, this makes sure that all data gets erased and cannot be
+accessed by other LVs created later (which happen to be assigned the same
+physical extents). This is a costly operation, but may be required as a security
+measure in certain environments.
 
 `saferemove_throughput`::
 
@@ -62,15 +66,15 @@ Storage Features
 ~~~~~~~~~~~~~~~~
 
 LVM is a typical block storage, but this backend does not support
-snapshot and clones. Unfortunately, normal LVM snapshots are quite
-inefficient, because they interfere all writes on the whole volume
+snapshots and clones. Unfortunately, normal LVM snapshots are quite
+inefficient, because they interfere with all writes on the entire volume
 group during snapshot time.
 
 One big advantage is that you can use it on top of a shared storage,
-for example an iSCSI LUN. The backend itself implement proper cluster
-wide locking.
+for example, an iSCSI LUN. The backend itself implements proper cluster-wide
+locking.
 
-TIP: The newer LVM-thin backend allows snapshot and clones, but does
+TIP: The newer LVM-thin backend allows snapshots and clones, but does
 not support shared storage.