X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=doc%2Fdoc-misc%2FExt-maildir%2B%2B;h=1ee8e981eb6f0ef3988a7516d4feae9dc39d1268;hp=b2fc580455d3b3bd1f602cce32273716913e5b53;hb=ac4d558b5e07523392bab2b4468b4c9f73745af9;hpb=e05f33e0b79c14608757a60f2f3f8588008355f7;ds=sidebyside

diff --git a/doc/doc-misc/Ext-maildir++ b/doc/doc-misc/Ext-maildir++
index b2fc58045..1ee8e981e 100644
--- a/doc/doc-misc/Ext-maildir++
+++ b/doc/doc-misc/Ext-maildir++
@@ -41,7 +41,7 @@ HOWTO.maildirquota
 
    Furthermore, this quota mechanism is not 100% effective. It is
    possible to have a situation where someone may go over quota. This
-   quota implementation uses a deliverate trade-off. It is necessary to
+   quota implementation uses a deliberate trade-off. It is necessary to
    use some form of locking in order to have a complete bulletproof quota
    enforcement, but maildirs mail stores were explicitly designed to
    avoid any kind of locking. This quota approach does not use locking,
@@ -330,7 +330,7 @@ Calculating the quota for a Maildir++
        quota recalculation ended up removing maildirsize due to a race
        condition, so the caller may or may not get a file descriptor
        together with the Maildir++ size.
-    4. If the numbers we got indicated that the Maidlir++ is over quota,
+    4. If the numbers we got indicated that the Maildir++ is over quota,
        some additional logic is in order: if we did not recalculate
        maildirsize, if the numbers in maildirsize indicated that we are
        over quota, then if maildirsize was more than one line long, or if