cluster manager: reword node limit, as there's not a real one

[pve-docs.git] / local-zfs.adoc

diff --git a/local-zfs.adoc b/local-zfs.adoc
index 5474b88b2afce82d2b18cd16b0a915bc588ea920..e794286d68050621d8512359a486458cd0807118 100644 (file)
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -42,8 +42,6 @@ management.
 
 * Designed for high storage capacities
 
-* Protection against data corruption
-
 * Asynchronous replication over network
 
 * Open Source
@@ -242,7 +240,7 @@ Using `ashift=9` when creating the pool can lead to bad
 performance, depending on the disks underneath, and cannot be changed later on.
 
 Mirror vdevs (RAID1, RAID10) have favorable behavior for VM workloads. Use
-them, unless your environmanet has specific needs and charactersitics where
+them, unless your environment has specific needs and characteristics where
 RAIDZ performance characteristics are acceptable.
 
 
@@ -564,10 +562,10 @@ All guest volumes/disks create on this storage will be encrypted with the
 shared key material of the parent dataset.
 
 To actually use the storage, the associated key material needs to be loaded
-with `zfs load-key`:
+and the dataset needs to be mounted. This can be done in one step with:
 
 ----
-# zfs load-key tank/encrypted_data
+# zfs mount -l tank/encrypted_data
 Enter passphrase for 'tank/encrypted_data':
 ----