haproxy-letsencrypt-docker.md
... ...
@@ -89,9 +89,9 @@ Things of note:
89 89
1. certbot listens on port 8000, which docker is mapping to port 80 and making available to the outside world for Let's Encrypt to talk to. We don't need port 443 mapped, because this is an initial request and Let's Encrypt should be fine with just port 80.
90 90
2. We're attaching a Volume to /etc/letsencrypt - that's where the certs end up, and that's how we'll make them available to haproxy.
91 91
3. The command concatenates the cert chain and private key into a format that haproxy understands, and dumps it out into the mounted /etc/letsencrypt volume.
92
-4. The certs are named after the first domain specified, so that ends up in the paths under /etc/letsencrypt. You might be able to change that, but see [rule 1](/rules#love-thy-defaults).
92
+4. certbot names the certs for the first domain specified, so that ends up in all of the paths under /etc/letsencrypt. You might be able to change that, but see [rule 1](/rules#love-thy-defaults).
93 93
94
-With all three files in your current dir, run: `docker-compose -f docker-compose-stage1.yml up` and you should hopefully see a message like:
94
+With all three files in your current directory, run: `docker-compose -f docker-compose-stage1.yml up` and you should hopefully see a message like the following after a couple of seconds:
95 95
96 96
```text
97 97
IMPORTANT NOTES: