Apply patch-bomb by ft, thanks a lot

[grml-crypt.git] / grml-crypt.8.txt

diff --git a/grml-crypt.8.txt b/grml-crypt.8.txt
index 27ccf29..6b246b2 100644 (file)
--- a/grml-crypt.8.txt
+++ b/grml-crypt.8.txt
@@ -17,7 +17,7 @@ DESCRIPTION
 -----------
 *grml-crypt* is a program that
 provides an easy wrapper around cryptsetup, mkfs, losetup and mount. You
-could create a loopback mountet crypted filesystem with only one command, but
+could create a loopback mounted crypted filesystem with only one command, but
 grml-crypt works for normal devices also.
 
 
@@ -26,20 +26,20 @@ ACTIONS
 *format <device/file> [mountpoint]*::
     This command "formats" a device/file. If the second parameter is not a
     blockdevice grml-crypt assumes that it should operate in file modus. If the
-    file does not allready exist it will be created with the given size. The
+    file does not already exist it will be created with the given size. The
     first 2MB of a device (luks header) are initialised with /dev/urandom, the
     other space is initialised with the given initialisation. If grml-crypt is
     in file modus the first 2MB of the loop file are also initialised with
-    /dev/urandom except where the file allready exist (with -f vor
+    /dev/urandom except where the file already exist (with -f vor
     overwriting). Commands: [losetup], dd, cryptsetup luksFormat, cryptsetup
     luksOpen, [dd], mkfs, [mount]
 
 *start <device/file> <mountpoint>*::
-    This command starts a encrypted device/file and mounts it to the given
+    This command starts an encrypted device/file and mounts it to the given
     mountpoint. Commands: [losetup], cryptsetup luksOpen, mount
 
 *stop <mountpoint>*::
-    This command stops a encrypted filesystem mountet at mountpoint. Even the
+    This command stops an encrypted filesystem mounted at mountpoint. Even the
     loopdevice gets destroyed with this command. Commands: mount, dmsetup info,
     cryptsetup status, umount, cryptsetup luksClose, [losetup -d]
 
@@ -110,7 +110,7 @@ INITIALISATION MODES
 
 *Default/Secure mode (no -o or -z given)*::
     This mode is the default. It should be quite secure. The device/file gets
-    initialised with /dev/urandom. Except with an allready existing file and
+    initialised with /dev/urandom. Except with an already existing file and
     -f, where NO initialisation will be done (all other modes behave as usual).
 
 *Optimized secure mode (-o)*::
@@ -166,7 +166,7 @@ ENCRYPTED LOOPFILESYSTEM ON USBSTICK
 *mount /mnt/external1*::
     To mount your usb-stick on /mnt/external1 (please verify!!).
 
-*grml-crypt -o -t vfat -s 50 /mnt/external1/secure.img /mnt/tmp*::
+*grml-crypt -o -t vfat -s 50 format /mnt/external1/secure.img /mnt/tmp*::
     This command creates a 50MB big file, encrypted with the default options
     and with vfat (also known as fat32). The optimized initialisation mode will
     be used for this file (without -o this could take REALLY LONG).  This