diff --git a/README.md b/README.md
index c060ff6..1ce0a8c 100644
--- a/README.md
+++ b/README.md
@@ -306,7 +306,7 @@ The ZFS pool and dataset setup that makes this tick, explained in plain English.
         1. In effect this `zpool/data/home` dataset is subject to `zfs mount -a` and will happily automount into `/home`.
 1. We export the zpool once, we then reimport it by scanning only inside `/dev/disk/by-partuuid`, again setting `-R /mnt` as we did during pool creation a moment ago and we do not mount any file systems.
 1. We `zfs load-key <encryptionroot>` which will load the key from `keylocation` after which the `keystatus` property for `<encryptionroot>` and all child datasets will change from `unavailable` to `available`.
-1. We mount our Arch Linux boot environment dataset. It automatically get prepended with `-R /mnt` since that's how we imported the pool.
+1. We mount our Arch Linux boot environment dataset. It automatically gets prefixed with `-R /mnt` since that's how we imported the pool.
 1. We `zfs mount -a` which automounts `zpool/data/home` into `/home`, which again gets auto-prepended by `/mnt`. 
 1. We lastly mount our EFI partition into `/mnt/efi`.
 1. We instruct ZFS to save its pool configuration via `zpool set cachefile=/etc/zfs/zpool.cache zpool`.