Fix spelling errors

Found by codespell.

4 files changed, 6 insertions, 6 deletions

diff --git a/doc/Doxyfile.in b/doc/Doxyfile.in
index 27be8415f..7a144d7d1 100644
--- a/doc/Doxyfile.in
+++ b/doc/Doxyfile.in
@@ -282,7 +282,7 @@ TYPEDEF_HIDES_STRUCT   = NO
 # causing a significant performance penality.
 # If the system has enough physical memory increasing the cache will improve the
 # performance by keeping more symbols in memory. Note that the value works on
-# a logarithmic scale so increasing the size by one will rougly double the
+# a logarithmic scale so increasing the size by one will roughly double the
 # memory usage. The cache size is given by this formula:
 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
 # corresponding to a cache size of 2^16 = 65536 symbols
diff --git a/doc/README.feature-removal-schedule b/doc/README.feature-removal-schedule
index 2ce6506a2..a085ac95a 100644
--- a/doc/README.feature-removal-schedule
+++ b/doc/README.feature-removal-schedule
@@ -7,7 +7,7 @@ Warning: program and lintian (missing-debian-source-format)
 Why:
  With the support of multiple source formats, the user should be explicit
  about the desired source format. The fallback to "1.0" is there only for
- backwards compatiblity but will be removed once all packages have the
+ backwards compatibility but will be removed once all packages have the
  debian/source/format file. This is unlikely to happen before 1.17.x.
 
 What: Source-Version (substvar)
diff --git a/doc/coding-style.txt b/doc/coding-style.txt
index ca360fa1f..edc5a2500 100644
--- a/doc/coding-style.txt
+++ b/doc/coding-style.txt
@@ -64,7 +64,7 @@ function(void *ptr, int value)
 	                     "extra-string");
 }
 
-When wrapping, logical operators should be kept on the preceeding line:
+When wrapping, logical operators should be kept on the preceding line:
 
 	if (really_long_variable_to_be_checked_against_a &&
 	    really_long_variable_to_be_checked_against_b)
diff --git a/doc/triggers.txt b/doc/triggers.txt
index 75579fa80..2d891ff54 100644
--- a/doc/triggers.txt
+++ b/doc/triggers.txt
@@ -126,7 +126,7 @@ reasonable states by default.
 
 If the `postinst triggered' run fails the package goes to
 `config-failed', so that the trigger processing will not be attempted
-again until explictly requested.
+again until explicitly requested.
 
 
              |
@@ -175,7 +175,7 @@ that T may automatically go from `triggers-awaited' to `installed'.
 Or to put it another way, triggered actions are considered irrelevant
 if the interested package I is not configured.  When I's postinst is
 called with `configure', it must do whatever actions are necessary to
-deal with any trigger activations which might have occured while it
+deal with any trigger activations which might have occurred while it
 was not configured, just as if the package was being configured for
 the first time.
 
@@ -264,7 +264,7 @@ dpkg during package unpack or removal.  The pathname must be absolute.
 File triggers should not generally be used without mutual consent.
 The use of a file trigger, and the name of the trigger used, should be
 stated in policy, so that a package which creates a relevant file in a
-maintainer script can activate the trigger explictly.
+maintainer script can activate the trigger explicitly.
 
 File triggers must definitely not be used as an escalation tool in
 disagreements between different packages as to the desired contents of