synced with Wiki (typo fix)

[platform/upstream/cryptsetup.git] / FAQ

diff --git a/FAQ b/FAQ
index dce3d55..a3f5b0f 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -983,7 +983,7 @@ A. Contributors
 
   Second, for LUKS, if anything damages the LUKS header or the
   key-stripe area then decrypting the LUKS device can become
-  impossible. This is a frequent occuurence. For example an
+  impossible. This is a frequent occurrence. For example an
   accidental format as FAT or some software overwriting the first
   sector where it suspects a partition boot sector typically makes a
   LUKS partition permanently inacessible. See more below on LUKS
@@ -1131,7 +1131,7 @@ A. Contributors
   In both cases, there is an additional (usually small) risk with
   binary backups: An attacker can see how many sectors and which
   ones have been changed since the backup. To prevent this, use a
-  filesystem level backup methid that encrypts the whole backup in
+  filesystem level backup method that encrypts the whole backup in
   one go, e.g. as described above with tar and GnuPG.
 
   My personal advice is to use one USB disk (low value data) or