storage: lvm: mention how saferemove setting is called in the UI

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

diff --git a/pve-storage-lvmthin.adoc b/pve-storage-lvmthin.adoc
index be730cf3ab2000e02f6b0dbbf8cdc39201d61845..f18af6365f2506eb2ade291ca2bca2f83a3ebb5d 100644 (file)
--- a/pve-storage-lvmthin.adoc
+++ b/pve-storage-lvmthin.adoc
@@ -1,6 +1,10 @@
+[[storage_lvmthin]]
 LVM thin Backend
 ----------------
-include::attributes.txt[]
+ifdef::wiki[]
+:pve-toplevel:
+:title: Storage: LVM Thin
+endif::wiki[]
 
 Storage pool type: `lvmthin`
 
@@ -9,7 +13,7 @@ instead allocates blocks when they are written. This behaviour is
 called thin-provisioning, because volumes can be much larger than
 physically available space.
 
-You can use the normal LVM command line tools to manage and create LVM
+You can use the normal LVM command-line tools to manage and create LVM
 thin pools (see `man lvmthin` for details). Assuming you already have
 a LVM volume group called `pve`, the following commands create a new
 LVM thin pool (size 100G) called `data`: