Formatting

docs/dns.md

@@ -1,11 +1,12 @@
 Below you can find a list of **recommended DNS records**. While some are mandatory for a mail server (A, MX), others are recommended to build a good reputation score (TXT/SPF) or used for auto-configuration of mail clients (SRV).
 
 ## References
-* A good article covering all relevant topics:
+
+- A good article covering all relevant topics:
   ["3 DNS Records Every Email Marketer Must Know"](https://www.rackaid.com/blog/email-dns-records)      
-* Another great one, but Zimbra as an example platform:
+- Another great one, but Zimbra as an example platform:
   ["Best Practices on Email Protection: SPF, DKIM and DMARC"](https://wiki.zimbra.com/wiki/Best_Practices_on_Email_Protection:_SPF,_DKIM_and_DMARC)       
-* An in-depth discussion of SPF, DKIM and DMARC:
+- An in-depth discussion of SPF, DKIM and DMARC:
   ["How to eliminate spam and protect your name with DMARC"](https://www.skelleton.net/2015/03/21/how-to-eliminate-spam-and-protect-your-name-with-dmarc/)
 
 ## Reverse DNS of your IP
@@ -14,9 +15,10 @@ Make sure that the PTR record of your IP matches the FQDN hostname of your mailc
 
 ## The minimal DNS configuration
 
-This example shows you a set of records for one domain. Each domain that is added to mailcow needs at least this set or records.
+This example shows you a set of records for one domain managed by mailcow. Each domain that is added to mailcow needs at least this set or records to function correctly.
 
 ```
+# Name              Type       Value
 mail                IN A       1.2.3.4
 autodiscover        IN A       1.2.3.4
 autoconfig          IN A       1.2.3.4
@@ -58,9 +60,10 @@ _autoconfig._tcp    IN SRV     0 1 443 autoconfig.example.org.
 _autodiscover._tcp  IN SRV     0 1 443 autodiscover.example.org.
 ```
 
-
 ## Testing
+
 Here are some tools you can use to verify your DNS configuration:
+
 - [MX Toolbox](https://mxtoolbox.com/SuperTool.aspx) (DNS, SMTP, RBL)
 - [port25.com](https://www.port25.com/dkim-wizard/) (DKIM, SPF)
 - [HAD Pilot](https://www.had-pilot.com/testdetails.html) (DKIM, DMARC, SPF)

docs/requirements.md

@@ -5,7 +5,7 @@ Before you run **mailcow: dockerized**, there are a few requirements that you sh
   Fore more details read: [github.com/docker/docker/issues/30402](https://github.com/docker/docker/issues/30402) and [forum.mailcow.email/t/solved-mailcow-docker-causes-kernel-panic-edit/448](https://forum.mailcow.email/t/solved-mailcow-docker-causes-kernel-panic-edit/448)
 - Mailcow: dockerized requires [some ports](#default-ports) to be open for incomming connections, so make sure that your firewall is not bloking these. Also make sure that no other application is interferring with mailcow's configuration.
 - A correct DNS setup is crucial to every good mailserver setup, so please make sure you got at least the [basics](dns/#the-minimal-dns-configuration) covered bevore you begin!
-- Make sure that your system has a correct date and time setup. This is crucial for stuff like two factor TOTP authentication.
+- Make sure that your system has a correct date and [time setup](#date-and-time). This is crucial for stuff like two factor TOTP authentication.
 
 ## Minimum System Resources
 
@@ -44,11 +44,11 @@ If you have a firewall already up and running please make sure that these ports
 | Dovecot ManageSieve | TCP      | 4190   | dovecot-mailcow | `${SIEVE_PORT}`                |
 | HTTP(S)             | TCP      | 80/443 | nginx-mailcow   | `${HTTP_PORT}`/`${HTTPS_PORT}` |
 
-## Enabling NTP services
+## Date and Time
 
 To ensure that you have the correct date and time setup on your system, please check the output of `timedatectl status`:
 
-```bash
+```
 $ timedatectl status
       Local time: Sat 2017-05-06 02:12:33 CEST
   Universal time: Sat 2017-05-06 00:12:33 UTC