18 files changed, 44 insertions, 44 deletions
diff --git a/share/man/man4/ccd.4 b/share/man/man4/ccd.4
index 0a0f0a6..b385af9 100644
--- a/share/man/man4/ccd.4
+++ b/share/man/man4/ccd.4
@@ -175,7 +175,7 @@ Note that a one-disk
 .Nm
 is not the same as the original partition.
 In particular, this means
-if you have a filesystem on a two-disk mirrored
+if you have a file system on a two-disk mirrored
 .Nm
 and one of the disks fail, you cannot mount and use the remaining
 partition as itself; you have to configure it as a one-disk
@@ -188,7 +188,7 @@ then restoring the partition.
 If just one (or more) of the disks in a
 .Nm
 fails, the entire
-filesystem will be lost unless you are mirroring the disks.
+file system will be lost unless you are mirroring the disks.
 .Pp
 If one of the disks in a mirror is lost, you should still
 be able to back up your data.
diff --git a/share/man/man4/da.4 b/share/man/man4/da.4
index a11cfed..d337ee1 100644
--- a/share/man/man4/da.4
+++ b/share/man/man4/da.4
@@ -67,7 +67,7 @@ partitioning scheme,
 .Xr disklabel 5 ,
 which is used to subdivide the
 .Fx
-slices into areas for individual filesystems and swap spaces.
+slices into areas for individual file systems and swap spaces.
 For more information, see
 .Xr fdisk 8
 and
@@ -105,7 +105,7 @@ and allows the device to reorganize writes to increase efficiency and
 performance.  This performance gain comes at a price.  Should the device
 lose power while its cache contains uncommitted write operations, these
 writes will be lost.  The effect of a loss of write transactions on
-a filesystem is non-deterministic and can cause corruption.  Most
+a file system is non-deterministic and can cause corruption.  Most
 devices age write transactions to limit vulnerability to a few transactions
 recently reported as complete, but it is none-the-less recommended that
 systems with write cache enabled devices reside on an Uninterruptible
diff --git a/share/man/man4/gbde.4 b/share/man/man4/gbde.4
index c851484..97f8fe6 100644
--- a/share/man/man4/gbde.4
+++ b/share/man/man4/gbde.4
@@ -225,7 +225,7 @@ some kind of structure or identifying byte sequences.
 .Pp
 Certain file formats like ELF contain multiple distinct sections, and it
 would be possible to locate things just right in such a way that a device
-contains a partition with a filesystem with a large executable,
+contains a partition with a file system with a large executable,
 .Pq Dq "a backup copy of my kernel"
 where a non-loaded ELF section is laid out
 consecutively on the device and thereby could be used to contain a
diff --git a/share/man/man4/geom.4 b/share/man/man4/geom.4
index 5b5d4fb..03e58e1 100644
--- a/share/man/man4/geom.4
+++ b/share/man/man4/geom.4
@@ -236,7 +236,7 @@ to be instantiated between a consumer and a provider attached to
 each other and to remove it again.
 .Pp
 To understand the utility of this, imagine a provider with
-being mounted as a filesystem.
+being mounted as a file system.
 Between the DEVFS geoms consumer and its provider we insert
 a mirror module which configures itself with one mirror
 copy and consequently is transparent to the I/O requests
@@ -244,7 +244,7 @@ on the path.
 We can now configure yet a mirror copy on the mirror geom,
 request a synchronization, and finally drop the first mirror
 copy.
-We have now in essence moved a mounted filesystem from one
+We have now in essence moved a mounted file system from one
 disk to another while it was being used.
 At this point the mirror geom can be deleted from the path
 again, it has served its purpose.
diff --git a/share/man/man4/intro.4 b/share/man/man4/intro.4
index 56cb049..8912544 100644
--- a/share/man/man4/intro.4
+++ b/share/man/man4/intro.4
@@ -71,7 +71,7 @@ sometimes also called
 .Em special files .
 They are usually located under the directory
 .Pa /dev
-in the filesystem hierarchy
+in the file system hierarchy
 (see also
 .Xr hier 7 ) .
 .Pp
@@ -106,7 +106,7 @@ and
 as the file type identification in the output of
 .Ql ls -l .
 Buffered devices are being accessed through the buffer cache of the
-operating system, and they are solely intended to layer a filesystem
+operating system, and they are solely intended to layer a file system
 on top of them.  They are normally implemented for disks and disk-like
 devices only and, for historical reasons, for tape devices.
 .Pp
@@ -121,7 +121,7 @@ denotes the raw device for the first SCSI disk, while
 is the corresponding device node for the buffered device.
 .Pp
 Unbuffered devices should be used for all actions that are not related
-to filesystem operations, even if the device in question is a disk
+to file system operations, even if the device in question is a disk
 device.  This includes making backups of entire disk partitions, or
 to
 .Em raw
diff --git a/share/man/man4/kld.4 b/share/man/man4/kld.4
index 2714cb0..0aec4f9 100644
--- a/share/man/man4/kld.4
+++ b/share/man/man4/kld.4
@@ -52,7 +52,7 @@ unloading.
 The
 .Fx
 system makes extensive use of loadable kernel modules, and provides loadable
-versions of most filesystems, the
+versions of most file systems, the
 .Tn NFS
 client and server, all the screen-savers, and the
 .Tn iBCS2
diff --git a/share/man/man4/lomac.4 b/share/man/man4/lomac.4
index fcadb5e..fa6403e 100644
--- a/share/man/man4/lomac.4
+++ b/share/man/man4/lomac.4
@@ -61,7 +61,7 @@ or
 .Dq low
 security level, attached to it,
 and these labels of integrity will be managed with a system cognizant
-of IPC (signals, debugging, sockets, pipes), path-based filesystem
+of IPC (signals, debugging, sockets, pipes), path-based file system
 labels, virtual memory objects, and privileged system calls.
 A process (or set of vmspace-sharing processes) will initially inherit
 the integrity level of its parent, which, at the point of
@@ -84,8 +84,8 @@ operation performed after it has been initialized.
 Pre-existing jail or chroot environments may not necessarily work
 completely.
 .Nm Ns 's
-filesystem should correctly respect the caching behavior of any of the
-system's filesystems, and so work for any
+file system should correctly respect the caching behavior of any of the
+system's file systems, and so work for any
 .Dq normal
 or
 .Dq synthetic
@@ -99,7 +99,7 @@ See
 .Pa /sys/security/lomac/policy_plm.h
 for specific information on exactly how
 .Nm
-has been compiled to control access to the filesystem.
+has been compiled to control access to the file system.
 .Sh COMPATIBILITY
 Some programs, for example
 .Xr syslogd 8 ,
diff --git a/share/man/man4/man4.alpha/linux.4 b/share/man/man4/man4.alpha/linux.4
index 591553f..9ff8a0d 100644
--- a/share/man/man4/man4.alpha/linux.4
+++ b/share/man/man4/man4.alpha/linux.4
@@ -113,7 +113,7 @@ or loaded as a module.
 .It Pa /compat/linux
 minimal Linux run-time environment
 .It Pa /compat/linux/proc
-limited Linux process filesystem
+limited Linux process file system
 .El
 .Sh SEE ALSO
 .Xr brandelf 1 ,
diff --git a/share/man/man4/man4.i386/linux.4 b/share/man/man4/man4.i386/linux.4
index 5f08ac1c..926b4ab 100644
--- a/share/man/man4/man4.i386/linux.4
+++ b/share/man/man4/man4.i386/linux.4
@@ -113,7 +113,7 @@ or loaded as a module.
 .It Pa /compat/linux
 minimal Linux run-time environment
 .It Pa /compat/linux/proc
-limited Linux process filesystem
+limited Linux process file system
 .El
 .Sh SEE ALSO
 .Xr brandelf 1 ,
diff --git a/share/man/man4/man4.i386/mcd.4 b/share/man/man4/man4.i386/mcd.4
index 09fede1..8793083 100644
--- a/share/man/man4/man4.i386/mcd.4
+++ b/share/man/man4/man4.i386/mcd.4
@@ -132,7 +132,7 @@ accesses
 .Bx
 partition on the disc.
 Normally, there is only
-one filesystem on a CD-ROM disc.
+one file system on a CD-ROM disc.
 .It Pa /dev/(r)mcd0c
 accesses raw device.
 .El
diff --git a/share/man/man4/man4.i386/scd.4 b/share/man/man4/man4.i386/scd.4
index eff4b15..ad8456d 100644
--- a/share/man/man4/man4.i386/scd.4
+++ b/share/man/man4/man4.i386/scd.4
@@ -52,7 +52,7 @@ accesses
 .Bx
 partition on the disc.
 Normally, there is only
-one filesystem on a CDROM disc.
+one file system on a CDROM disc.
 .It Pa /dev/[r]scd0c
 accesses the raw device.
 .El
diff --git a/share/man/man4/md.4 b/share/man/man4/md.4
index fe1edbf..0e966ff 100644
--- a/share/man/man4/md.4
+++ b/share/man/man4/md.4
@@ -44,7 +44,7 @@ For backwards compatibility the type
 is also recognized.
 If the kernel is created with option
 .Dv MD_ROOT
-the first preloaded image found will become the root filesystem.
+the first preloaded image found will become the root file system.
 .It Cm vnode
 A regular file is used as backing store.
 This allows for mounting ISO images without the tedious
diff --git a/share/man/man4/raid.4 b/share/man/man4/raid.4
index 54c8b77..dd5cfb8 100644
--- a/share/man/man4/raid.4
+++ b/share/man/man4/raid.4
@@ -136,21 +136,21 @@ will configure normally.
 Component labels are also used to support the auto-detection and
 auto-configuration of RAID sets.  A RAID set can be flagged as
 auto-configurable, in which case it will be configured automatically
-during the kernel boot process.  RAID filesystems which are
-automatically configured are also eligible to be the root filesystem.
+during the kernel boot process.  RAID file systems which are
+automatically configured are also eligible to be the root file system.
 There is currently only limited support (alpha and pmax architectures)
 for booting a kernel directly from a RAID 1 set, and no support for
 booting from any other RAID sets.  To use a RAID set as the root
-filesystem, a kernel is usually obtained from a small non-RAID
+file system, a kernel is usually obtained from a small non-RAID
 partition, after which any auto-configuring RAID set can be used for the
-root filesystem.  See
+root file system.  See
 .Xr raidctl 8
 for more information on auto-configuration of RAID sets.
 .Pp
 The driver supports 
 .Sq hot spares , 
 disks which are on-line, but are not
-actively used in an existing filesystem.  Should a disk fail, the
+actively used in an existing file system.  Should a disk fail, the
 driver is capable of reconstructing the failed disk onto a hot spare
 or back onto a replacement drive.
 If the components are hot swapable, the failed disk can then be
@@ -185,10 +185,10 @@ before doing a
 .Xr fsck 8
 or a
 .Xr newfs 8 ,
-filesystem integrity and parity integrity can be ensured.  It bears
+file system integrity and parity integrity can be ensured.  It bears
 repeating again that parity recomputation is 
 .Ar required
-before any filesystems are created or used on the RAID device.  If the
+before any file systems are created or used on the RAID device.  If the
 parity is not correct, then missing data cannot be correctly recovered.
 .Pp
 RAID levels may be combined in a hierarchical fashion.  For example, a RAID 0 
@@ -259,7 +259,7 @@ result in data loss.
 Certain RAID levels (1, 4, 5, 6, and others) can protect against some
 data loss due to component failure.  However the loss of two
 components of a RAID 4 or 5 system, or the loss of a single component
-of a RAID 0 system, will result in the entire filesystems on that RAID
+of a RAID 0 system, will result in the entire file systems on that RAID
 device being lost.
 RAID is 
 .Ar NOT
diff --git a/share/man/man4/syncer.4 b/share/man/man4/syncer.4
index ee425f1..bff7a77 100644
--- a/share/man/man4/syncer.4
+++ b/share/man/man4/syncer.4
@@ -29,14 +29,14 @@
 .Os
 .Sh NAME
 .Nm syncer
-.Nd filesystem synchronizer kernel process
+.Nd file system synchronizer kernel process
 .Sh SYNOPSIS
 .Nm
 .Sh DESCRIPTION
 The
 .Nm
 kernel process helps protect the integrity of disk volumes
-by flushing volatile cached filesystem data to disk.
+by flushing volatile cached file system data to disk.
 .Pp
 The kernel places all
 .Xr vnode 9 Ns 's
@@ -87,5 +87,5 @@ process first appeared in
 It is possible on some systems that a
 .Xr sync 2
 occurring simultaneously with a crash may cause
-filesystem damage.  See
+file system damage.  See
 .Xr fsck 8 .
diff --git a/share/man/man4/umass.4 b/share/man/man4/umass.4
index 7c1a2e4..9673cd7 100644
--- a/share/man/man4/umass.4
+++ b/share/man/man4/umass.4
@@ -98,11 +98,11 @@ Write a disklabel to the Zip drive (see
 .Nm vpo
 for the
 .Nm disktab
-entry), creates the filesystem and mounts the new filesystem on /mnt.
+entry), creates the file system and mounts the new file system on /mnt.
 .Pp
 .Dl newfs_msdos /dev/da0
 .Pp
-Create a new FAT type filesystem.
+Create a new FAT type file system.
 .Sh SEE ALSO
 .Xr ohci 4 ,
 .Xr uhci 4 ,
diff --git a/share/man/man4/unix.4 b/share/man/man4/unix.4
index c6d227b..a2e9356 100644
--- a/share/man/man4/unix.4
+++ b/share/man/man4/unix.4
@@ -56,10 +56,10 @@ family supports the
 and
 .Dv SOCK_DGRAM
 socket types and uses
-filesystem pathnames for addressing.
+file system pathnames for addressing.
 .Sh ADDRESSING
 .Ux Ns -domain
-addresses are variable-length filesystem pathnames of
+addresses are variable-length file system pathnames of
 at most 104 characters.
 The include file
 .Aq Pa sys/un.h
@@ -76,7 +76,7 @@ Binding a name to a
 .Ux Ns -domain
 socket with
 .Xr bind 2
-causes a socket file to be created in the filesystem.
+causes a socket file to be created in the file system.
 This file is
 .Em not
 removed when the socket is closed \(em
@@ -93,7 +93,7 @@ All addresses are absolute- or relative-pathnames
 of other
 .Ux Ns -domain
 sockets.
-Normal filesystem access-control mechanisms are also
+Normal file system access-control mechanisms are also
 applied when referencing pathnames; e.g., the destination
 of a
 .Xr connect 2
diff --git a/share/man/man4/vinum.4 b/share/man/man4/vinum.4
index c43048d..c5fadfc 100644
--- a/share/man/man4/vinum.4
+++ b/share/man/man4/vinum.4
@@ -85,10 +85,10 @@ By attaching an
 additional plex and subsequently detaching one of the older plexes, data can be
 moved on-line without compromising access.
 .It
-An additional plex can be used to obtain a consistent dump of a filesystem.
+An additional plex can be used to obtain a consistent dump of a file system.
 By
 attaching an additional plex and detaching at a specific time, the detached plex
-becomes an accurate snapshot of the filesystem at the time of detachment.
+becomes an accurate snapshot of the file system at the time of detachment.
 .\" Make sure to flush!
 .El
 .It
@@ -163,7 +163,7 @@ devices.
 offers automatic startup.
 Unlike
 .Ux
-filesystems,
+file systems,
 .Nm
 volumes contain all the configuration information needed to ensure that they are
 started correctly when the subsystem is enabled.
@@ -385,7 +385,7 @@ flag to
 .Xr newfs 8 .
 For example, if you have a volume
 .Pa concat ,
-use the following command to create a UFS filesystem on it:
+use the following command to create a UFS file system on it:
 .Pp
 .Dl "newfs -v /dev/vinum/concat"
 .Sh OBJECT NAMING
diff --git a/share/man/man4/vpo.4 b/share/man/man4/vpo.4
index 36385d0..f156f69 100644
--- a/share/man/man4/vpo.4
+++ b/share/man/man4/vpo.4
@@ -51,11 +51,11 @@ transferring data.
 .Pp
 DOS and
 .Fx
-filesystems are supported.
-When mounting a DOS filesystem or
+file systems are supported.
+When mounting a DOS file system or
 formating a
 .Fx
-filesystem, check the slice of the disk with the
+file system, check the slice of the disk with the
 .Xr fdisk 8
 utility.
 .Pp