5 files changed, 23 insertions, 23 deletions
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 3165d951b8..62ee5acd24 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -168,7 +168,7 @@ to use Linux.
 .TP
 .B "'root=...'"
 This argument tells the kernel what device is to be used as the root
-filesystem while booting.
+file system while booting.
 The default of this setting is determined
 at compile time, and usually is the value of the root device of the
 system that the kernel was built on.
@@ -203,16 +203,16 @@ possible root devices in major/minor format is also accepted.
 alternative.)
 .TP
 .BR 'ro' " and " 'rw'
-The 'ro' option tells the kernel to mount the root filesystem
-as 'readonly' so that filesystem consistency check programs (fsck)
+The 'ro' option tells the kernel to mount the root file system
+as 'readonly' so that file system consistency check programs (fsck)
 can do their work on a quiescent file system.
 No processes can
-write to files on the filesystem in question until it is 'remounted'
+write to files on the file system in question until it is 'remounted'
 as read/write capable, for example, by 'mount \-w \-n \-o remount /'.
 (See also
 .BR mount (8).)
 
-The 'rw' option tells the kernel to mount the root filesystem read/write.
+The 'rw' option tells the kernel to mount the root file system read/write.
 This is the default.
 
 The choice between read-only and read/write can also be set using
@@ -369,7 +369,7 @@ But while booting (or while constructing boot floppies)
 it is often useful to load the floppy contents into a
 ramdisk.
 One might also have a system in which first
-some modules (for filesystem or hardware) must be loaded
+some modules (for file system or hardware) must be loaded
 before the main disk can be accessed.
 
 In Linux 1.3.48, ramdisk handling was changed drastically.
@@ -416,7 +416,7 @@ When this feature is enabled, the boot process will load the kernel
 and an initial ramdisk; then the kernel converts initrd into
 a "normal" ramdisk, which is mounted read-write as root device;
 then /linuxrc is executed; afterwards the "real" root file system is mounted,
-and the initrd filesystem is moved over to /initrd; finally
+and the initrd file system is moved over to /initrd; finally
 the usual boot sequence (e.g., invocation of /sbin/init) is performed.
 
 For a detailed description of the initrd feature, see
diff --git a/man7/hier.7 b/man7/hier.7
index 81a0549a90..755ffae472 100644
--- a/man7/hier.7
+++ b/man7/hier.7
@@ -91,18 +91,18 @@ depends on local administration decisions.
 .TP
 .I /lib
 This directory should hold those shared libraries that are necessary
-to boot the system and to run the commands in the root filesystem.
+to boot the system and to run the commands in the root file system.
 .TP
 .I /media
 This directory contains mount points for removable media such as CD
 and DVD disks or USB sticks.
 .TP
 .I /mnt
-This directory is a mount point for a temporarily mounted filesystem.
+This directory is a mount point for a temporarily mounted file system.
 In some distributions,
 .I /mnt
 contains subdirectories intended to be used as mount points for several
-temporary filesystems.
+temporary file systems.
 .TP
 .I /opt
 This directory should contain add-on packages that contain static files.
@@ -110,7 +110,7 @@ This directory should contain add-on packages that contain static files.
 .I /proc
 This is a mount point for the
 .I proc
-filesystem, which provides information about running processes and
+file system, which provides information about running processes and
 the kernel.
 This pseudo-file system is described in more detail in
 .BR proc (5).
@@ -413,7 +413,7 @@ device lock files is
 .I LCK..<device>
 where
 .I <device>
-is the device's name in the filesystem.
+is the device's name in the file system.
 The format used is that of HDU UUCP lock files, that is, lock files
 contain a PID as a 10-byte ASCII decimal number, followed by a newline
 character.
diff --git a/man7/path_resolution.7 b/man7/path_resolution.7
index 99f2cb2e2c..1b4d840c34 100644
--- a/man7/path_resolution.7
+++ b/man7/path_resolution.7
@@ -123,17 +123,17 @@ respectively.
 
 The path resolution process will assume that these entries have
 their conventional meanings, regardless of whether they are
-actually present in the physical filesystem.
+actually present in the physical file system.
 
 One cannot walk down past the root: "/.." is the same as "/".
 .SS "Mount points"
 After a "mount dev path" command, the pathname "path" refers to
-the root of the filesystem hierarchy on the device "dev", and no
+the root of the file system hierarchy on the device "dev", and no
 longer to whatever it referred to earlier.
 
-One can walk out of a mounted filesystem: "path/.." refers to
+One can walk out of a mounted file system: "path/.." refers to
 the parent directory of "path",
-outside of the filesystem hierarchy on "dev".
+outside of the file system hierarchy on "dev".
 .SS "Trailing slashes"
 If a pathname ends in a '/', that forces resolution of the preceding
 component as in Step 2: it has to exist and resolve to a directory.
@@ -198,7 +198,7 @@ Similarly, Linux uses the fsgid ("file system group ID")
 instead of the effective group ID.
 See
 .BR setfsgid (2).
-.\" FIXME say something about filesystem mounted read-only ?
+.\" FIXME say something about file system mounted read-only ?
 .SS "Bypassing permission checks: superuser and capabilities"
 On a traditional Unix system, the superuser
 .RI ( root ,
diff --git a/man7/unix.7 b/man7/unix.7
index f6988ae184..57a7383934 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -49,7 +49,7 @@ and delivers messages in the order that they were sent.
 Unix sockets support passing file descriptors or process credentials
 to other processes using ancillary data.
 .SS Address Format
-A Unix address is defined as a filename in the filesystem or
+A Unix address is defined as a filename in the file system or
 as a unique string in the abstract namespace.
 Sockets created by
 .BR socketpair (2)
@@ -199,7 +199,7 @@ option must be enabled on the socket.
 .SH ERRORS
 .TP
 .B EADDRINUSE
-Selected local address is already taken or filesystem socket
+Selected local address is already taken or file system socket
 object already exists.
 .TP
 .B ECONNREFUSED
@@ -266,7 +266,7 @@ vs.
 Unknown socket type.
 .PP
 Other errors can be generated by the generic socket layer or
-by the filesystem while generating a filesystem socket object.
+by the file system while generating a file system socket object.
 See the appropriate manual pages for more information.
 .SH VERSIONS
 .B SCM_CREDENTIALS
@@ -276,7 +276,7 @@ be used in portable programs.
 but the implementation details differ.)
 .SH NOTES
 In the Linux implementation, sockets which are visible in the
-filesystem honor the permissions of the directory they are in.
+file system honor the permissions of the directory they are in.
 Their owner, group and their permissions can be changed.
 Creation of a new socket will fail if the process does not have write and
 search (execute) permission on the directory the socket is created in.
diff --git a/man7/uri.7 b/man7/uri.7
index e540e55481..cb901ab6d3 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -678,11 +678,11 @@ Also, the directory ZZZ usually changes when a version changes
 (though filename globbing could partially overcome this).
 Finally, using the file: scheme doesn't easily support people
 who dynamically load documentation from the Internet (instead of
-loading the files onto a local filesystem).
+loading the files onto a local file system).
 A future URI scheme may be added (e.g., "userdoc:") to permit
 programs to include cross-references to more detailed documentation
 without having to know the exact location of that documentation.
-Alternatively, a future version of the filesystem specification may
+Alternatively, a future version of the file-system specification may
 specify file locations sufficiently so that the file: scheme will
 be able to locate documentation.
 .PP