s/filesystem/file system/ as discussed on -developers

2 files changed, 5 insertions, 5 deletions

diff --git a/bin/ln/ln.1 b/bin/ln/ln.1
index 637867b..0854e91 100644
--- a/bin/ln/ln.1
+++ b/bin/ln/ln.1
@@ -124,7 +124,7 @@ links.
 A hard link to a file is indistinguishable from the original directory entry;
 any changes to a file are effectively independent of the name used to reference
 the file.
-Hard links may not normally refer to directories and may not span filesystems.
+Hard links may not normally refer to directories and may not span file systems.
 .Pp
 A symbolic link contains the name of the file to
 which it is linked.  The referenced file is used when an
@@ -138,7 +138,7 @@ must be done to obtain information about the link.
 The
 .Xr readlink  2
 call may be used to read the contents of a symbolic link.
-Symbolic links may span filesystems and may refer to directories.
+Symbolic links may span file systems and may refer to directories.
 .Pp
 Given one or two arguments,
 .Nm
diff --git a/bin/ln/symlink.7 b/bin/ln/symlink.7
index bfc0537..2a0a082 100644
--- a/bin/ln/symlink.7
+++ b/bin/ln/symlink.7
@@ -47,13 +47,13 @@ it is a reference to the object underlying the original file name.
 Changes to a file are independent of the name used to reference the
 file.
 Hard links may not refer to directories and may not reference files
-on different filesystems.
+on different file systems.
 A symbolic link contains the name of the file to which it is linked,
 i.e. it is a pointer to another name, and not to an underlying object.
 For this reason, symbolic links may reference directories and may span
-filesystems.
+file systems.
 .Pp
-Because a symbolic link and its referenced object coexist in the filesystem
+Because a symbolic link and its referenced object coexist in the file system
 name space, confusion can arise in distinguishing between the link itself
 and the referenced object.
 Historically, commands and system calls have adopted their own link