Merge pull request #587 from cuu508/master

Fix typos

Author: foxcpp

contrib/kubernetes/chart/README.md

@@ -9,7 +9,7 @@ load balancer in front of the nodes.
 
 ## Requirement
 
-In order to run maddy properly, you need to have TLS secret undet name maddy present in the cluster. If you have commercial
+In order to run maddy properly, you need to have TLS secret under name maddy present in the cluster. If you have commercial
 certificate, you can create it by the following command:
 
 ```sh
@@ -20,9 +20,9 @@ If you use cert-manager, just create the secret under name maddy.
 
 ## Replication
 
-Default for this chart is 1 replica of maddy. If you try to increse this, you will probably get an error because of
+Default for this chart is 1 replica of maddy. If you try to increase this, you will probably get an error because of
 the busy ports 25, 143, 587, etc. We do not support this feature at the moment, so please use just 1 replica. Like said
-at the begining of this document, multiple replicas would probably require to switch do DaemonSet which would further require
+at the beginning of this document, multiple replicas would probably require to switch do DaemonSet which would further require
 to have TCP load balancer and shared storage between all replicas. This is not supported by this chart, sorry.
 This chart is used on one node cluster and then installation is straight forward, like described bellow, but if you have
 multiple node cluster, please use taints and tolerations to select the desired node. This chart supports tolerations to

dist/README.md

@@ -22,7 +22,7 @@ Additionally, unit files apply strict sandboxing, limiting maddy permissions on
 the system to a bare minimum. Subset of these options makes it impossible for
 privileged authentication helper binaries to gain required permissions, so you
 may have to disable it when using system account-based authentication with
-maddy running as a unprivilieged user.
+maddy running as a unprivileged user.
 
 ## fail2ban configuration
 

docs/internals/unicode.md

@@ -93,4 +93,4 @@ mentioned above).
 
 Clients that want to implement proper handling for Unicode strings may assume
 maddy does not handle them properly in e.g. SEARCH commands and so such clients
-may download messsages and process them locally.
+may download messages and process them locally.

docs/multiple-domains.md

@@ -28,7 +28,7 @@ the [introduction tutorial](tutorials/setting-up.md).
 
 Also note that you do not really need a separate TLS certificate for each
 managed domain. You can have one hostname e.g. mail.example.org set as an MX
-record for mulitple domains.
+record for multiple domains.
 
 **If you want multiple domains to share username namespace**, you should change
 several more options.
@@ -53,7 +53,7 @@ maddy imap-acct create [email protected]
 "user"**, you can set `storage_map` in IMAP endpoint and `delivery_map` in
 storage backend to use `email_locapart`:
 ```
-straoge.imapsql local_mailboxes {
+storage.imapsql local_mailboxes {
    ...
    delivery_map email_localpart # deliver "user@*" to "user"
 }

docs/reference/auth/netauth.md

@@ -37,7 +37,7 @@ auth.netauth {}
 
 OPTIONAL.
 
-Group that entities must posess to be able to use maddy services.
+Group that entities must possess to be able to use maddy services.
 This can be used to provide email to just a subset of the entities
 present in NetAuth.
 

docs/reference/checks/authorize_sender.md

@@ -94,7 +94,8 @@ Normalization function to apply to authorization username before
 further processing.
 
 Available options:
-- `auto`                    `precis_casefold_email` for valid emails, `precise_casefold` otherwise.
+
+- `auto`                    `precis_casefold_email` for valid emails, `precis_casefold` otherwise.
 - `precis_casefold_email`   PRECIS UsernameCaseMapped profile + U-labels form for domain
 - `precis_casefold`         PRECIS UsernameCaseMapped profile for the entire string
 - `precis_email`            PRECIS UsernameCasePreserved profile + U-labels form for domain

docs/reference/checks/command.md

@@ -127,5 +127,5 @@ the message pipeline action.
 
 Two codes are defined implicitly, exit code 1 causes the message to be rejected
 with a permanent error, exit code 2 causes the message to be quarantined. Both
-action can be overriden using the 'code' directive.
+action can be overridden using the 'code' directive.
 

docs/reference/checks/dkim.md

@@ -19,7 +19,7 @@ check.dkim {
 **Syntax**: debug _boolean_ <br>
 **Default**: global directive value
 
-Log both successfull and unsuccessful check executions instead of just
+Log both successful and unsuccessful check executions instead of just
 unsuccessful.
 
 **Syntax**: required\_fields _string..._ <br>

docs/reference/checks/dnsbl.md

@@ -4,7 +4,7 @@ The check.dnsbl module implements checking of source IP and hostnames against a
 of DNS-based Blackhole lists (DNSBLs).
 
 Its configuration consists of module configuration directives and a set
-of blocks specifing lists to use and kind of lookups to perform on them.
+of blocks specifying lists to use and kind of lookups to perform on them.
 
 ```
 check.dnsbl {

docs/reference/checks/misc.md

@@ -15,8 +15,8 @@ Action to take when check fails. See Check actions for details.
 **Syntax**: debug _boolean_ <br>
 **Default**: global directive value
 
-Log both sucessfull and unsucessfull check executions instead of just
-unsucessfull.
+Log both successful and unsuccessful check executions instead of just
+unsuccessful.
 
 ## require\_mx\_record