2 files changed, 4 insertions, 4 deletions

diff --git a/lib/libarchive/libarchive-formats.5 b/lib/libarchive/libarchive-formats.5
index abded0fda129..c4ee23b93329 100644
--- a/lib/libarchive/libarchive-formats.5
+++ b/lib/libarchive/libarchive-formats.5
@@ -36,7 +36,7 @@ The
 library reads and writes a variety of streaming archive formats.
 Generally speaking, all of these archive formats consist of a series of
 .Dq entries .
-Each entry stores a single filesystem object, such as a file, directory,
+Each entry stores a single file system object, such as a file, directory,
 or symbolic link.
 .Pp
 The following provides a brief description of each format supported
@@ -196,7 +196,7 @@ implementations.
 A
 .Dq shell archive
 is a shell script that, when executed on a POSIX-compliant
-system, will recreate a collection of filesystem objects.
+system, will recreate a collection of file system objects.
 The libarchive library can write two different kinds of shar archives:
 .Bl -tag -width indent
 .It Cm shar
diff --git a/lib/libarchive/tar.5 b/lib/libarchive/tar.5
index e8aaa37c9d86..163aac4a35aa 100644
--- a/lib/libarchive/tar.5
+++ b/lib/libarchive/tar.5
@@ -34,7 +34,7 @@
 The
 .Nm
 archive format collects any number of files, directories, and other
-filesystem objects (symbolic links, device nodes, etc.) into a single
+file system objects (symbolic links, device nodes, etc.) into a single
 stream of bytes.
 The format was originally designed to be used with
 tape drives that operate with fixed-size blocks, but is widely used as
@@ -43,7 +43,7 @@ a general packaging mechanism.
 A
 .Nm
 archive consists of a series of 512-byte records.
-Each filesystem object requires a header record which stores basic metadata
+Each file system object requires a header record which stores basic metadata
 (pathname, owner, permissions, etc.) and zero or more records containing any
 file data.
 The end of the archive is indicated by two records consisting