Update README.md

README.md

@@ -95,4 +95,4 @@ Both of the above issues are readily resolved by hopefully reading /etc/os-relea
 
 Because this is implemented as a full kernel and initramfs, it doesn't really fit into the way your distribution ships/installs packages. It doesn't make any sense for your OS to install these two files into `/boot`. They need to be placed in an implementation-dependenant location so that GRUB, EFI, etc can read them. This makes updating the boot menu on an installed system slightly more burdensome, since your normal package update process won't see updates.
 
-If you have native ZFS encryption enabled, you're likely going to be entering a passphrase twice. Once in the boot menu when it needs to load the kernel / initramfs, and once again in your boot environment when it needs to mount / and finish booting the OS. A basic [patch](blob/master/mount-zfs.sh.diff) for the Dracut ZFS module is included here to look for a passphrase in a file contained in your initrams. This file will needed to be added to the initramfs in your boot environment, and then set as a keylocation on the filesystem. Care needs to be taken to leave the keyformat to `passphrase`, otherwise you'll be unable to input the required passphrase in the boot menu.
+If you have native ZFS encryption enabled, you're likely going to be entering a passphrase twice. Once in the boot menu when it needs to load the kernel / initramfs, and once again in your boot environment when it needs to mount / and finish booting the OS. A basic [patch](mount-zfs.sh.diff) for the Dracut ZFS module is included here to look for a passphrase in a file contained in your initramfs. This file will needed to be added to the initramfs in your boot environment, and then set as a keylocation on the filesystem. Care needs to be taken to leave the keyformat to `passphrase`, otherwise you'll be unable to input the required passphrase in the boot menu.