diff --git a/Arch.md b/Arch.md
index 48b188b..adae0f3 100644
--- a/Arch.md
+++ b/Arch.md
@@ -14,7 +14,7 @@ tags:
 - It's worth checking the [Arch News](https://archlinux.org/news/) before running an update, or if you have any issues with an update. The Arch maintainers will always put known update issues there and how to resolve them.
 - Due to the fast moving pace of Arch you should aim to update your system at least once per week
   - It shouldn't be a problem if you take longer, but it helps minimize risk.
-  - It's usually smart to not do system updates right before you need the computer for an important
+  - It's usually smart to not do system updates right before you need the computer for an important task.
     - [System Snapshots](ArchSetup.md#bootable-system-snapshots) can help reduce this issue by having the option to just rollback
 
 #### Usage
@@ -74,7 +74,7 @@ In the case where a system is no longer bootable, it is possible to access and h
 3. From the console run `lsblk` to get a list of device and partition names names (sda, nvme0n1, ect with a trailing number for the partition number)
 4. Determine your system partitions and mount them manually, in the case of Endeavour's btrfs install it would be done like so:
    1. `mount -o subvol=@ /dev/nvme0n1p2 /mnt` (adjust to your actual disk name if different)
-   2. `mount -o subvol=@home /dev/nvme0n1p2 /mnt`
+   2. `mount -o subvol=@home /dev/nvme0n1p2 /mnt/home`
    3. `arch-chroot /mnt`
    4. `mount /efi` or `mount /boot/efi` depending on where your efi partition is
 5. Begin to fix issues.