backup: Fix wrong unit for bandwidth limit

The correct unit for the bwlimit is actually Kibibyte per second
rather than Kibibit per second.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>

diff --git a/vzdump.adoc b/vzdump.adoc
index ce465295f8d375d5e210d149e989cadaf2bee434..f3eadcdd14e571ef4bd974d2cda1662934ee70ee 100644 (file)
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -398,7 +398,7 @@ limit. A bigger per-job limit will only overwrite the per-storage limit if
 you have `Data.Allocate' permissions on the affected storage.
 
 You can use the `--bwlimit <integer>` option from the restore CLI commands
-to set up a restore job specific bandwidth limit.  Kibit/s is used as unit
+to set up a restore job specific bandwidth limit. KiB/s is used as unit
 for the limit, this means passing `10240' will limit the read speed of the
 backup to 10 MiB/s, ensuring that the rest of the possible storage bandwidth
 is available for the already running virtual guests, and thus the backup