summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorklemens <ka7@github.com>2017-04-16 20:49:32 +0200
committerHeiko Schlittermann (HS12-RIPE) <hs@schlittermann.de>2018-12-20 22:29:09 +0100
commitaded22555eeb31bc032f9bc58a83762981a58391 (patch)
tree801b3a8f5b247a7690149ca2c0f3c9130f4ef249 /doc
parentaa6e77afb5ba7df42fcff06cac744b1f4a4105d2 (diff)
spelling fixes
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-docbook/Makefile2
-rw-r--r--doc/doc-misc/Ext-mbx-locking2
-rw-r--r--doc/doc-src/FAQ.src10
-rw-r--r--doc/doc-txt/NewStuff2
-rw-r--r--doc/doc-txt/dbm.discuss.txt2
5 files changed, 9 insertions, 9 deletions
diff --git a/doc/doc-docbook/Makefile b/doc/doc-docbook/Makefile
index ee97257b6..10df9180a 100644
--- a/doc/doc-docbook/Makefile
+++ b/doc/doc-docbook/Makefile
@@ -11,7 +11,7 @@ notarget:; @echo "** You must specify a target, in the form x.y, where x is '
# Generate all the documentation files...
#
## removed info files as I cannot generate them - spec.info filter.info
-## removed html files as superceded by new website code
+## removed html files as superseded by new website code
everything: spec.pdf spec.ps spec.txt \
filter.pdf filter.ps filter.txt \
exim.8
diff --git a/doc/doc-misc/Ext-mbx-locking b/doc/doc-misc/Ext-mbx-locking
index 9ef684026..30a547f63 100644
--- a/doc/doc-misc/Ext-mbx-locking
+++ b/doc/doc-misc/Ext-mbx-locking
@@ -228,7 +228,7 @@ BEZERK AND MMDF
Locking in the traditional UNIX formats was largely dictated by
the status quo in other applications; however, additional protection
-is added against inadvertantly running multiple instances of a
+is added against inadvertently running multiple instances of a
c-client application on the same mail file.
(1) c-client attempts to create a .lock file (mail file name with
diff --git a/doc/doc-src/FAQ.src b/doc/doc-src/FAQ.src
index 47b810e5d..c83c339d7 100644
--- a/doc/doc-src/FAQ.src
+++ b/doc/doc-src/FAQ.src
@@ -408,7 +408,7 @@ A0018: Recall that Exim does not keep separate queues for each domain, but
a temporary error. Here are some possibilities:
(1) The messages to \(aol.com)\ got put in your queue, but no previous
- delivery attempt occured before you did the \-R-\. This might have been
+ delivery attempt occurred before you did the \-R-\. This might have been
because of your settings of \queue_only_load\, \smtp_accept_queue\, or any
other option that caused no immediate delivery attempt on arrival. If
this is the case, you can try using \-qqR-\ instead of \-R-\.
@@ -1538,7 +1538,7 @@ A0089: This was a bad interaction between a change to the Linux kernel and some
taken from Exim's change log:
When Exim is receiving multiple messages on a single connection, and
- spinning off delivery processess, it sets the SIGCHLD signal handling to
+ spinning off delivery processes, it sets the SIGCHLD signal handling to
SIG_IGN, because it doesn't want to wait for these processes. However,
because on some OS this didn't work, it also has a paranoid call to
\^waitpid()^\ in the loop to reap any children that have finished. Some
@@ -2917,7 +2917,7 @@ Q0419: I have some obsolete domains which people have been warned not to use
any more. How can I arrange to delete any mail that is sent to them?
A0419: To reject them at SMTP time, with a customized error message, place
- statments like this in the ACL:
+ statements like this in the ACL:
==> deny message = The domain $domain is obsolete
domains = lsearch;/etc/exim/obsolete.domains
@@ -5122,7 +5122,7 @@ A1001: Splitting the spool directory has most benefit if there are times when
up earlier on some types of file system, compared with others.
Exim was not designed for handling large queues. If you are in an
- enviroment where lots of messages remain on the queue for long periods
+ environment where lots of messages remain on the queue for long periods
of time, consider implementing a back up host to which you pass these
messages, so that the main host's queue remains short. You can use
\fallback_hosts\ to do this, or a router that is conditional on
@@ -6544,7 +6544,7 @@ Q9604: I get the \*too many open files*\ error especially when a lot of messages
land for Majordomo at the same time.
A9604: The problem appears to be the number of open files the system can
- handle. This is changable by using the proc filesystem. To your
+ handle. This is changeable by using the proc filesystem. To your
\(/etc/rc.d/rc.local)\ file append something like the following:
==> # Now System is up, Modify kernel parameters for max open etc.
diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index fb336b8af..c3c69ebc5 100644
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -950,7 +950,7 @@ Version 4.68
longest line that was received as part of the message, not counting the
line termination character(s).
- 7. Host lists can now include +ignore_defer and +include_defer, analagous to
+ 7. Host lists can now include +ignore_defer and +include_defer, analogous to
+ignore_unknown and +include_unknown. These options should be used with
care, probably only in non-critical host lists such as whitelists.
diff --git a/doc/doc-txt/dbm.discuss.txt b/doc/doc-txt/dbm.discuss.txt
index 4de57735e..7df044e82 100644
--- a/doc/doc-txt/dbm.discuss.txt
+++ b/doc/doc-txt/dbm.discuss.txt
@@ -223,7 +223,7 @@ files in other formats that are created by other programs.
Berkeley DB 4.x
---------------
-The 4.x series is a developement of the 2.x and 3.x series, and the above
+The 4.x series is a development of the 2.x and 3.x series, and the above
comments apply.