Enhance documentation readability.

docs/user-guide/docker-and-lets-encrypt.md

@@ -1,19 +1,24 @@
 # Docker & Traefik
 
 In this use case, we want to use Traefik as a _layer-7_ load balancer with SSL termination for a set of micro-services used to run a web application.
+
 We also want to automatically _discover any services_ on the Docker host and let Traefik reconfigure itself automatically when containers get created (or shut down) so HTTP traffic can be routed accordingly.
+
 In addition, we want to use Let's Encrypt to automatically generate and renew SSL certificates per hostname.
 
 ## Setting Up
 
 In order for this to work, you'll need a server with a public IP address, with Docker installed on it.
+
 In this example, we're using the fictitious domain _my-awesome-app.org_.
+
 In real-life, you'll want to use your own domain and have the DNS configured accordingly so the hostname records you'll want to use point to the aforementioned public IP address.
 
 ## Networking
 
 Docker containers can only communicate with each other over TCP when they share at least one network.
 This makes sense from a topological point of view in the context of networking, since Docker under the hood creates IPTable rules so containers can't reach other containers _unless you'd want to_.
+
 In this example, we're going to use a single network called `web` where all containers that are handling HTTP traffic (including Traefik) will reside in.
 
 On the Docker host, run the following command:
@@ -37,6 +42,7 @@ touch /opt/traefik/traefik.toml
 ```
 
 The `docker-compose.yml` file will provide us with a simple, consistent and more importantly, a deterministic way to create Traefik.
+
 The contents of the file is as follows:
 
 ```yaml
@@ -62,10 +68,10 @@ networks:
     external: true
 ```
 
-As you can see, we're mounting the `traefik.toml` file as well as the (empty) `acme.json` file in the container.
-Also, we're mounting the `/var/run/docker.sock` Docker socket in the container as well, so Traefik can listen to Docker events and reconfigure it's own internal configuration when containers are created (or shut down).
+As you can see, we're mounting the `traefik.toml` file as well as the (empty) `acme.json` file in the container.  
+Also, we're mounting the `/var/run/docker.sock` Docker socket in the container as well, so Traefik can listen to Docker events and reconfigure it's own internal configuration when containers are created (or shut down).  
 Also, we're making sure the container is automatically restarted by the Docker engine in case of problems (or: if the server is rebooted).
-We're publishing the default HTTP ports `80` and `443` on the host, and making sure the container is placed within the `web` network we've created earlier on.
+We're publishing the default HTTP ports `80` and `443` on the host, and making sure the container is placed within the `web` network we've created earlier on.  
 Finally, we're giving this container a static name called `traefik`.
 
 Let's take a look at a simply `traefik.toml` configuration as well before we'll create the Traefik container:
@@ -106,7 +112,8 @@ This is the minimum configuration required to do the following:
 - Check for new versions of Traefik periodically
 - Create two entry points, namely an `HTTP` endpoint on port `80`, and an `HTTPS` endpoint on port `443` where all incoming traffic on port `80` will immediately get redirected to `HTTPS`.
 - Enable the Docker configuration backend and listen for container events on the Docker unix socket we've mounted earlier. However, **new containers will not be exposed by Traefik by default, we'll get into this in a bit!**
-- Enable automatic request and configuration of SSL certificates using Let's Encrypt. These certificates will be stored in the `acme.json` file, which you can back-up yourself and store off-premises.
+- Enable automatic request and configuration of SSL certificates using Let's Encrypt.
+    These certificates will be stored in the `acme.json` file, which you can back-up yourself and store off-premises.
 
 Alright, let's boot the container. From the `/opt/traefik` directory, run `docker-compose up -d` which will create and start the Traefik container.
 
@@ -114,7 +121,9 @@ Alright, let's boot the container. From the `/opt/traefik` directory, run `docke
 
 Now that we've fully configured and started Traefik, it's time to get our applications running!
 
-Let's take a simple example of a micro-service project consisting of various services, where some will be exposed to the outside world and some will not. The `docker-compose.yml` of our project looks like this:
+Let's take a simple example of a micro-service project consisting of various services, where some will be exposed to the outside world and some will not. 
+
+The `docker-compose.yml` of our project looks like this:
 
 ```yaml
 version: "2.1"
@@ -173,16 +182,19 @@ networks:
     external: true
 ```
 
-Here, we can see a set of services with two applications that we're actually exposing to the outside world.
-Notice how there isn't a single container that has any published ports to the host -- everything is routed through Docker networks.
+Here, we can see a set of services with two applications that we're actually exposing to the outside world.  
+Notice how there isn't a single container that has any published ports to the host -- everything is routed through Docker networks.  
 Also, only the containers that we want traffic to get routed to are attached to the `web` network we created at the start of this document.
+
 Since the `traefik` container we've created and started earlier is also attached to this network, HTTP requests can now get routed to these containers.
 
 ### Labels
 
 As mentioned earlier, we don't want containers exposed automatically by Traefik.
+
 The reason behind this is simple: we want to have control over this process ourselves.
 Thanks to Docker labels, we can tell Traefik how to create it's internal routing configuration.
+
 Let's take a look at the labels themselves for the `app` service, which is a HTTP webservice listing on port 9000:
 
 ```yaml
@@ -194,14 +206,17 @@ Let's take a look at the labels themselves for the `app` service, which is a HTT
 ```
 
 First, we specify the `backend` name which corresponds to the actual service we're routing **to**.
-We also tell Traefik to use the `web` network to route HTTP traffic to this container. With the `frontend.rule` label, we tell Traefik that we want to route to this container if the incoming HTTP request contains the `Host` `app.my-awesome-app.org`.
-Essentially, this is the actual rule used for Layer-7 load balancing.
+
+We also tell Traefik to use the `web` network to route HTTP traffic to this container.  
+With the `frontend.rule` label, we tell Traefik that we want to route to this container if the incoming HTTP request contains the `Host` `app.my-awesome-app.org`.
+Essentially, this is the actual rule used for Layer-7 load balancing.  
 With the `traefik.enable` label, we tell Traefik to include this container in it's internal configuration.
+
 Finally but not unimportantly, we tell Traefik to route **to** port `9000`, since that is the actual TCP/IP port the container actually listens on.
 
 #### Gotchas and tips
 
-- Always specify the correct port where the container expects HTTP traffic using `traefik.port` label.
+- Always specify the correct port where the container expects HTTP traffic using `traefik.port` label.  
     If a container exposes multiple ports, Traefik may forward traffic to the wrong port.
     Even if a container only exposes one port, you should always write configuration defensively and explicitly.
 - Should you choose to enable the `exposedbydefault` flag in the `traefik.toml` configuration, be aware that all containers that are placed in the same network as Traefik will automatically be reachable from the outside world, for everyone and everyone to see.
@@ -213,5 +228,6 @@ Finally but not unimportantly, we tell Traefik to route **to** port `9000`, sinc
 
 ### Final thoughts
 
-Using Traefik as a Layer-7 load balancer in combination with both Docker and Let's Encrypt provides you with an extremely flexible, performant and self-configuring solution for your projects.
+Using Traefik as a Layer-7 load balancer in combination with both Docker and Let's Encrypt provides you with an extremely flexible, powerful and self-configuring solution for your projects.
+
 With Let's Encrypt, your endpoints are automatically secured with production-ready SSL certificates that are renewed automatically as well.