X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=doc%2Fdoc-misc%2FExt-mbx-locking;h=9ef684026338f95cff98736d0c4982ec557f05cb;hp=f1b0523f69f35d928ebca7e005df0301c6c801df;hb=77c27011669fef957e1b70877dbd3612a8b1014e;hpb=e05f33e0b79c14608757a60f2f3f8588008355f7

diff --git a/doc/doc-misc/Ext-mbx-locking b/doc/doc-misc/Ext-mbx-locking
index f1b0523f6..9ef684026 100644
--- a/doc/doc-misc/Ext-mbx-locking
+++ b/doc/doc-misc/Ext-mbx-locking
@@ -43,7 +43,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-existence 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:
 
@@ -81,7 +81,7 @@ locks held by that process when it terminates.
 exclusive (provided there are no other shared users of the lock) and
 to downgrade an exclusive lock to shared.  It is important that at no
 time is the lock ever removed; a process upgrading to exclusive must
-not relenquish its shared lock.
+not relinquish its shared lock.
 
      Most commonly, the resources being locked are files.  Shared
 locks are particularly important with files; multiple simultaneous