summaryrefslogtreecommitdiff
path: root/apt-inst/extract.cc
diff options
context:
space:
mode:
authorMichael Vogt <mvo@debian.org>2014-02-22 18:34:33 +0100
committerMichael Vogt <mvo@debian.org>2014-02-22 18:34:33 +0100
commit1e3f4083db29bba600b9725e9456b0e140975c99 (patch)
tree620d9e1b3072aba9fa65d45342aa4043e79975a7 /apt-inst/extract.cc
parent5077916ef802948e6a3faab95b2d2a975438ec26 (diff)
Fix typos in documentation (codespell)
Diffstat (limited to 'apt-inst/extract.cc')
-rw-r--r--apt-inst/extract.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/apt-inst/extract.cc b/apt-inst/extract.cc
index 2c95fba92..b3dfccfc6 100644
--- a/apt-inst/extract.cc
+++ b/apt-inst/extract.cc
@@ -10,7 +10,7 @@
object is unpacked to '.dpkg.new' then the original is hardlinked to
'.dpkg.tmp' and finally the new object is renamed to overwrite the old
one. From an external perspective the file never ceased to exist.
- After the archive has been sucessfully unpacked the .dpkg.tmp files
+ After the archive has been successfully unpacked the .dpkg.tmp files
are erased. A failure causes all the .dpkg.tmp files to be restored.
Decisions about unpacking go like this:
@@ -22,7 +22,7 @@
[Note, this is reduced to only check if a file was expected to be
there]
- If the existing link/file is not a directory then it is replaced
- irregardless
+ regardless
- If the existing link/directory is being replaced by a directory then
absolutely nothing happens.
- If the existing link/directory is being replaced by a link then