diff options
author | Michael Vogt <mvo@debian.org> | 2014-02-22 18:34:33 +0100 |
---|---|---|
committer | Michael Vogt <mvo@debian.org> | 2014-02-22 18:34:33 +0100 |
commit | 1e3f4083db29bba600b9725e9456b0e140975c99 (patch) | |
tree | 620d9e1b3072aba9fa65d45342aa4043e79975a7 /apt-inst/contrib | |
parent | 5077916ef802948e6a3faab95b2d2a975438ec26 (diff) |
Fix typos in documentation (codespell)
Diffstat (limited to 'apt-inst/contrib')
-rw-r--r-- | apt-inst/contrib/arfile.cc | 2 | ||||
-rw-r--r-- | apt-inst/contrib/extracttar.cc | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/apt-inst/contrib/arfile.cc b/apt-inst/contrib/arfile.cc index 9d84c1784..77dbc55d6 100644 --- a/apt-inst/contrib/arfile.cc +++ b/apt-inst/contrib/arfile.cc @@ -6,7 +6,7 @@ AR File - Handle an 'AR' archive AR Archives have plain text headers at the start of each file - section. The headers are aligned on a 2 byte boundry. + section. The headers are aligned on a 2 byte boundary. Information about the structure of AR files can be found in ar(5) on a BSD system, or in the binutils source. diff --git a/apt-inst/contrib/extracttar.cc b/apt-inst/contrib/extracttar.cc index fb4db42f8..2437c9749 100644 --- a/apt-inst/contrib/extracttar.cc +++ b/apt-inst/contrib/extracttar.cc @@ -6,7 +6,7 @@ Extract a Tar - Tar Extractor Some performance measurements showed that zlib performed quite poorly - in comparision to a forked gzip process. This tar extractor makes use + in comparison to a forked gzip process. This tar extractor makes use of the fact that dup'd file descriptors have the same seek pointer and that gzip will not read past the end of a compressed stream, even if there is more data. We use the dup property to track extraction |