Fix typos.

3 files changed, 6 insertions, 6 deletions

diff --git a/man/cryptsetup-reencrypt.8 b/man/cryptsetup-reencrypt.8
index d4ddb1f3..d39fa8fd 100644
--- a/man/cryptsetup-reencrypt.8
+++ b/man/cryptsetup-reencrypt.8
@@ -201,7 +201,7 @@ Print separate line every <seconds> with reencryption progress.
 Use only while encrypting not yet encrypted device (see \-\-new).
 
 Specify LUKS version when performing in-place encryption. If the parameter
-is ommited default value (LUKS1) is used. Type may be one of: \fBluks\fR (default),
+is omitted default value (LUKS1) is used. Type may be one of: \fBluks\fR (default),
 \fBluks1\fR or \fBluks2\fR.
 .TP
 .B "\-\-version"
diff --git a/man/cryptsetup.8 b/man/cryptsetup.8
index 093f81b6..9a4d1c30 100644
--- a/man/cryptsetup.8
+++ b/man/cryptsetup.8
@@ -432,7 +432,7 @@ The \fItoken\fR command is supported only for LUKS2.
 
 For adding new keyring token, option \-\-key\-description is mandatory.
 Also, new token is assigned to key slot specified with \-\-key\-slot option or to all
-active key slots in the case \-\-key\-slot option is ommited.
+active key slots in the case \-\-key\-slot option is omitted.
 
 To remove existing token, specify the token ID which should be removed with
 \-\-token\-id option.
@@ -907,7 +907,7 @@ Set the memory cost for PBKDF (for Argon2i/id the number represents kilobytes).
 Note that it is maximal value, PBKDF benchmark can decrease it.
 This option is not available for PBKDF2.
 .TP
-.B "\-\-pbkdf\-paralell <number>"
+.B "\-\-pbkdf\-parallel <number>"
 Set the parallel cost for PBKDF (number of threads, up to 4).
 Note that it is maximal value, it is decreased automatically if
 CPU online count is lower.
@@ -1347,7 +1347,7 @@ the status command output. Also see losetup(8).
 The LUKS2 on-disk metadata is updated in several steps and
 to achieve proper atomic update, there is a locking mechanism.
 For an image in file, code uses \fIflock(2)\fR system call.
-For a block device, lock is perfomed over a special file stored
+For a block device, lock is performed over a special file stored
 in a locking directory (by default \fI/run/lock/cryptsetup\fR).
 The locking directory should be created with the proper security
 context by the distribution during the boot-up phase.
diff --git a/man/veritysetup.8 b/man/veritysetup.8
index 1b7523f6..72fb6659 100644
--- a/man/veritysetup.8
+++ b/man/veritysetup.8
@@ -120,7 +120,7 @@ Defines what to do if data integrity problem is detected (data corruption).
 
 Without these options kernel fails the IO operation with I/O error.
 With \-\-ignore-corruption option the corruption is only logged.
-With \-\-restart-on-corruption the kernel is restarted immediatelly.
+With \-\-restart-on-corruption the kernel is restarted immediately.
 (You have to provide way how to avoid restart loops.)
 
 \fBWARNING:\fR Use these options only for very specific cases.
@@ -182,7 +182,7 @@ Hash-offset must be greater than number of blocks in data-area.
 
 .B "veritysetup \-\-data-blocks=256 \-\-hash-offset=1052672 create test-device <device> <device> <root_hash>"
 
-Acivatees the verity device named test-device. Options \-\-data-blocks and \-\-hash-offset are the same
+Activates the verity device named test-device. Options \-\-data-blocks and \-\-hash-offset are the same
 as in the format command. The <root_hash> was calculated in format command.
 
 .B "veritysetup \-\-data-blocks=256 \-\-hash-offset=1052672 verify <data_device> <hash_device> <root_hash>"