docs/MOUNT_REQUIREMENTS: fix typo

Follow-ups for 3e94ae6f1e2bac0c6be2817ab419123ea37d8e4a.

diff --git a/docs/MOUNT_REQUIREMENTS.md b/docs/MOUNT_REQUIREMENTS.md
index 6ca7bf7cc8178d147bf95e36c62c39f065ca4ccc..3780882deb09d2653d59735ced62b30a2baab37a 100644 (file)
--- a/docs/MOUNT_REQUIREMENTS.md
+++ b/docs/MOUNT_REQUIREMENTS.md
@@ -44,12 +44,12 @@ if a mount point is *not* split out,
 but a given subtree is part of the parent mount,
 the requirements for that subtree are trivially satisfied by the parent.
 
-A "mount point" in this document means the whole subtree of the hierachy,
+A "mount point" in this document means the whole subtree of the hierarchy,
 until a mountpoint lower in the hierarchy which is conceptually separate.
 For example, on a system with a custom mount point located below `/var/spool/`,
 most of `/var/` would be in category 2/early,
 but the additional mount would be in category 3/regular.
-Conversly, if some part of `/usr/` that is normally part of that subtree
+Conversely, if some part of `/usr/` that is normally part of that subtree
 was split out to a separate mount,
 this mount point would fall into category 1/initrd
 and configuration would need to be provided for it to be mounted in the initrd.