diff --git a/docs/in-depth/acme-certificates.md b/docs/in-depth/acme-certificates.md
index 78ea08e..4fc1a3d 100644
--- a/docs/in-depth/acme-certificates.md
+++ b/docs/in-depth/acme-certificates.md
@@ -4,10 +4,10 @@ WildDuck is able to manage SNI certificates with Let's Encrypt or any other ACME
 
 Requirements to use auto-renewing SNI certificates:
 
--   SNI certificates are used by IMAP, POP3, WildDudk API and SMTP servers. MX and Webmail servers are not covered by this.
--   Each server that a SNI hostname resolves to must have either WildDuck API or [ACME agent](https://github.com/nodemailer/wildduck/blob/14ecd5cf904377e2f6e1cefaa1a3052e2cfbb82f/config/acme.toml#L21) running on port 80
+-   SNI certificates are used by IMAP, POP3, WildDuck API, and SMTP servers. MX and Webmail servers are not covered by this.
+-   Each server that a SNI hostname resolves to must have either WildDuck API or [ACME agent](https://github.com/nodemailer/wildduck/blob/b46293aba8a112842431336f9c62557b6c66d971/config/acme.toml#L23) running on port 80
 -   When using SNI you still have to set up some default certificates in the config file. These could be self-signed though as WildDuck prefers SNI certs whenever possible
--   You must register such certificates via [/certs](https://docs.wildduck.email/api/#operation/updateTLSCertificate) API endpoint with the following configuration:
+-   You must register ACME SNI certificates via [/certs](https://docs.wildduck.email/api/#operation/updateTLSCertificate) API endpoint with the following configuration:
 
 ```js
 curl -XPOST http://localhost:8080/certs -H 'content-type:application/json' -d'{
@@ -16,4 +16,4 @@ curl -XPOST http://localhost:8080/certs -H 'content-type:application/json' -d'{
 }'
 ```
 
-> the example above expects WildDuck ACME agent running on port 80 in every IP address that _imap.example.com_ resolves to
+> The example above expects WildDuck ACME agent running on port 80 in every IP address that _imap.example.com_ resolves to