diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md
index aeab79dbf..f98875aa6 100644
--- a/docs/configuring-playbook-traefik.md
+++ b/docs/configuring-playbook-traefik.md
@@ -57,9 +57,9 @@ However, if your service does not run on a container or runs on another machine,
 
 ## Reverse-proxying a remote HTTP/HTTPS service behind Traefik
 
-If you want to host another webserver would be reachable via `my-fancy-website.example.com` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host.
+If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host.
 
-Prerequisites: DNS and routing for the domain `my-fancy-website.example.com` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.com` would be a CNAME going to `matrix.example.com`.
+Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`.
 
 First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files: