Fix key-certificate pair names and paths

docs/reverse.rst

@@ -182,16 +182,17 @@ One such example is ``mailu/traefik-certdumper``, which has been adapted for use
       - "/data/traefik/certs:/output"
 
 
-Assuming you have ``volume-mounted`` your ``acme.json`` put to ``/data/traefik`` on your host. The dumper will then write out ``/data/traefik/certs/your.doma.in.crt``
+Assuming you have ``volume-mounted`` your ``acme.json`` put to ``/data/traefik`` on your host. The dumper will then write out ``/data/traefik/certs/cert.pem`` and ``/data/traefik/certs/key.pem`` whenever ``acme.json`` is updated.
-and ``/data/traefik/certs/your.doma.in.key`` whenever ``acme.json`` is updated. Yay! Now let’s mount this to our ``front`` container like:
+Yay! Now let’s mount this to our ``front`` container like:
 
 .. code-block:: yaml
 
     volumes:
-      - "$ROOT/overrides/nginx:/overrides"
       - /data/traefik/certs/$TRAEFIK_DOMAIN.crt:/certs/cert.pem
       - /data/traefik/certs/$TRAEFIK_DOMAIN.key:/certs/key.pem
 
+This works, because we set ``TLS_FLAVOR=mail``, which picks up the key-certificate pair (e.g., ``cert.pem`` and ``key.pem``) from the certs folder in the root path (``/certs/``).
+
 .. _`Traefik`: https://traefik.io/
 
 Override Mailu configuration