From: Michael Kerrisk (man-pages) Date: Thu, 28 May 2020 14:58:23 +0000 (+0200) Subject: Manual pages: umount.8: use "filesystem" consistently X-Git-Tag: v2.36-rc1~34 X-Git-Url: http://git.ipfire.org/?p=thirdparty%2Futil-linux.git;a=commitdiff_plain;h=79eab6383f78ad9fbab06b17aca11a4861abbaf7 Manual pages: umount.8: use "filesystem" consistently Currently, this page has a mix of "filesystem" and file system", with the former being predominant. Let's settle on one. Signed-off-by: Michael Kerrisk (man-pages) --- diff --git a/sys-utils/umount.8 b/sys-utils/umount.8 index c56e51e183..f04746211e 100644 --- a/sys-utils/umount.8 +++ b/sys-utils/umount.8 @@ -24,7 +24,7 @@ .\" .TH UMOUNT 8 "July 2014" "util-linux" "System Administration" .SH NAME -umount \- unmount file systems +umount \- unmount filesystems .SH SYNOPSIS .B umount \-a .RB [ \-dflnrv ] @@ -43,13 +43,13 @@ umount \- unmount file systems .SH DESCRIPTION The .B umount -command detaches the mentioned file system(s) from the file hierarchy. A -file system is specified by giving the directory where it has been -mounted. Giving the special device on which the file system lives may +command detaches the mentioned filesystem(s) from the file hierarchy. A +filesystem is specified by giving the directory where it has been +mounted. Giving the special device on which the filesystem lives may also work, but is obsolete, mainly because it will fail in case this device was mounted on more than one directory. .PP -Note that a file system cannot be unmounted when it is 'busy' - for +Note that a filesystem cannot be unmounted when it is 'busy' - for example, when there are open files on it, or when some process has its working directory there, or when a swap file on it is in use. The offending process could even be