From f01daa30f155859e83013f4c840d64ddcf735b39 Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Tue, 25 Nov 2025 22:51:25 +0900 Subject: [PATCH] docs/MOUNT_REQUIREMENTS: fix typo Follow-ups for 3e94ae6f1e2bac0c6be2817ab419123ea37d8e4a. --- docs/MOUNT_REQUIREMENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/MOUNT_REQUIREMENTS.md b/docs/MOUNT_REQUIREMENTS.md index 6ca7bf7cc81..3780882deb0 100644 --- 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. -- 2.47.3