Fix docs/configuring-well-known.md and add a comment

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

docs/configuring-playbook-bot-postmoogle.md

@@ -71,7 +71,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
 To use the bot, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox.
 
-Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.domain`. Emails sent to that email address will be forwarded to the room.
+Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room.
 
 Send `!pm help` to the room to see the bot's help menu for additional commands.
 

docs/configuring-playbook-email.md

@@ -5,7 +5,7 @@ By default, this playbook sets up an [Exim](https://www.exim.org/) email server
 The email server would attempt to deliver emails directly to their final destination.
 This may or may not work, depending on your domain configuration (SPF settings, etc.)
 
-By default, emails are sent from `matrix@example.com` (as specified by the `exim_relay_sender_address` playbook variable).
+By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable.
 
 **Note**: If you are using a Google Cloud instance, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so you need to relay email through another SMTP server as described below.
 

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:
 
@@ -99,7 +99,7 @@ aux_file_definitions:
       http:
         routers:
           webserver-router:
-            rule: Host(`my_fancy_website.example.com`)
+            rule: Host(`my-fancy-website.example.net`)
             service: webserver-service
             tls:
               certResolver: default
@@ -122,7 +122,7 @@ aux_file_definitions:
       tcp:
         routers:
           webserver-router:
-            rule: Host(`my_fancy_website.example.com`)
+            rule: Host(`my-fancy-website.example.net`)
             service: webserver-service
             tls:
               passthrough: true

docs/configuring-well-known.md

@@ -58,7 +58,8 @@ matrix_static_files_file_matrix_support_property_m_contacts:
   - email_address: security@example.com
     role: m.role.security
 
-matrix_static_files_file_matrix_support_property_m_support_page: "https://matrix.example.com/support"
+# Your organization's support page on the base (or another) domain, if any
+matrix_static_files_file_matrix_support_property_m_support_page: "https://example.com/support"
 ```
 
 To learn how to set up `/.well-known/matrix/support` for the base domain, read the Installing section below.

examples/vars.yml

@@ -3,7 +3,7 @@
 # Matrix user ids for your server will be of the form (`@user:example.com`).
 #
 # Note: this playbook does not touch the server referenced here.
-# Installation happens on another server ("matrix.example.com").
+# Installation happens on another server ("matrix.example.com", see `matrix_server_fqn_matrix`).
 #
 # If you've deployed using the wrong domain, you'll have to run the Uninstalling step,
 # because you can't change the Domain after deployment.