summaryrefslogtreecommitdiff
path: root/imap/docs/locking.txt
diff options
context:
space:
mode:
authorEduardo Chappa <chappa@washington.edu>2020-01-15 21:41:39 -0700
committerEduardo Chappa <chappa@washington.edu>2020-01-15 21:41:39 -0700
commit06c6ab430b223f6923fe74a4b8d11f3e626848a8 (patch)
tree2b483acf3ec2da573992c20b766a480e22f4c45a /imap/docs/locking.txt
parent9822842646bc2b940d4b98a260ee4e3ac26fce57 (diff)
downloadalpine-06c6ab430b223f6923fe74a4b8d11f3e626848a8.tar.xz
* Fix a number of misspellings in the source code of Alpine. I hav only
fixed those that belong to the source code of Alpine and do not come from an external source. List contributed by Jens Schleusener.
Diffstat (limited to 'imap/docs/locking.txt')
-rw-r--r--imap/docs/locking.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/imap/docs/locking.txt b/imap/docs/locking.txt
index 32ff6c66..eb165647 100644
--- a/imap/docs/locking.txt
+++ b/imap/docs/locking.txt
@@ -61,7 +61,7 @@ writeable memory between such processes.
A means of communicating this is by use of a file with a mutually
agreed upon name. A binary semaphore can be passed by means of the
-existance or non-existance of that file, provided that there is an
+existence or non-existance of that file, provided that there is an
atomic means to create a file if and only if that file does not exist.
In C terms:
@@ -245,7 +245,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