summaryrefslogtreecommitdiffstats
path: root/lib/libarchive/tar.5
diff options
context:
space:
mode:
authorcharnier <charnier@FreeBSD.org>2005-01-24 19:58:05 +0000
committercharnier <charnier@FreeBSD.org>2005-01-24 19:58:05 +0000
commitaafdd446f9f6ccafe38a20cdb5232fa6d059f132 (patch)
tree44224c2feece9623da92b0abb8c10829f092eb36 /lib/libarchive/tar.5
parent49eb535a6ca3ef4eba0a3697815d1ba3e8142e5c (diff)
downloadFreeBSD-src-aafdd446f9f6ccafe38a20cdb5232fa6d059f132.zip
FreeBSD-src-aafdd446f9f6ccafe38a20cdb5232fa6d059f132.tar.gz
spell "file system" correctly
Approved by: ru
Diffstat (limited to 'lib/libarchive/tar.5')
-rw-r--r--lib/libarchive/tar.54
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/libarchive/tar.5 b/lib/libarchive/tar.5
index e8aaa37..163aac4 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
OpenPOWER on IntegriCloud