diff --git a/collections/_posts/2018-05-03-lvm-in-luks-with-encrypted-boot-partition-and-suspend-to-disk.md b/collections/_posts/2018-05-03-lvm-in-luks-with-encrypted-boot-partition-and-suspend-to-disk.md
index 812f237..fd5b53f 100644
--- a/collections/_posts/2018-05-03-lvm-in-luks-with-encrypted-boot-partition-and-suspend-to-disk.md
+++ b/collections/_posts/2018-05-03-lvm-in-luks-with-encrypted-boot-partition-and-suspend-to-disk.md
@@ -386,7 +386,7 @@ initially when creating the LUKS container **can optionally** be removed
 from the device. If this is done, unlocking the boot partition is the **only
 way** to recover the key-file used to unlock the LVM partition.
 **Use the below command with caution**. Depending on your security
-threat-model, this might be unecessary.
+threat-model, this might be unnecessary.
 
     # # Skip this step if you don't understand the risks.
     # cryptsetup luksKillSlot /dev/nvme0n1p3 0 --key-file /etc/initcpio/keys/encrypted-lvm.key