X-Git-Url: https://git.grml.org/?a=blobdiff_plain;f=grml-crypt.8.txt;h=6cf20fd53b486427fc45b70a3ecffead3bd39aa8;hb=567a1357c27177cc302202d0feb78881a0922b34;hp=301237f9c3460cdfde8947ddb014ad72d97b6e52;hpb=dcc4d6d5646bc6591e90e0c12c85bb9f3ba78deb;p=grml-crypt.git

diff --git a/grml-crypt.8.txt b/grml-crypt.8.txt
index 301237f..6cf20fd 100644
--- a/grml-crypt.8.txt
+++ b/grml-crypt.8.txt
@@ -5,18 +5,18 @@ Michael Gebetsroither <michael.geb@gmx.at>
 
 NAME
 ----
-grml-crypt - Wrapper arround cryptsetup/losetup/mkfs/mount
+grml-crypt - Wrapper around cryptsetup/losetup/mkfs/mount
 
 
 SYNOPSIS
 --------
-*grml-vpn* [OPTIONS] 'action' <device/file> '[mountpoint]'
+*grml-crypt* [OPTIONS] 'action' <device/file> '[mountpoint]'
 
 
 DESCRIPTION
 -----------
 *grml-crypt* is a program that
-provides an easy wrapper arround cryptsetup, mkfs, losetup and mount. You
+provides an easy wrapper around cryptsetup, mkfs, losetup and mount. You
 could create a loopback mountet crypted filesystem with only one command, but
 grml-crypt works for normal devices also.
 
@@ -25,12 +25,12 @@ ACTIONS
 -------
 *format <device/file> [mountpoint]*::
     This command "formats" a device/file. If the second parameter is not a
-    blockdevice grml-crupt assumes that it should operate in file modus. If the
-    file does not allready exist it will be created with the given size. The
+    blockdevice grml-crypt assumes that it should operate in file modus. If 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]
 
@@ -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)*::