Replace example.tld with example.com

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

examples/reverse-proxies/caddy2-in-container/Caddyfile

@@ -1,4 +1,4 @@
-matrix.example.tld {
+matrix.example.com {
 
   handle {
         encode zstd gzip
@@ -14,7 +14,7 @@ matrix.example.tld {
 }
 
 # Put `https://` at the beginning to enforce https protocol as 8448 is not the default https port (which is 443) 
-https://matrix.example.tld:8448 {
+https://matrix.example.com:8448 {
     handle {
         encode zstd gzip
 
@@ -29,14 +29,14 @@ https://matrix.example.tld:8448 {
 }
 
 
-example.tld {
+example.com {
 # Uncomment this if you are following "(Option 3): Setting up reverse-proxying of the well-known files from the base domain's server to the Matrix server" of https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-well-known.md#option-3-setting-up-reverse-proxying-of-the-well-known-files-from-the-base-domains-server-to-the-matrix-server
     @wellknown {
         path /.well-known/matrix/*
     }
 
     handle @wellknown {
-        reverse_proxy https://matrix.example.tld {
+        reverse_proxy https://matrix.example.com {
             header_up Host {http.reverse_proxy.upstream.hostport}
         }
     }

examples/reverse-proxies/caddy2-in-container/README.md

@@ -14,6 +14,6 @@ Then, adjust your Caddy  `docker-compose.yaml` file (if you're using docker-comp
 ## Using the Caddyfile
 
 You can either just use the [Caddyfile](Caddyfile) directly or append its content to your own Caddyfile.
-In both cases make sure to replace all the `example.tld` domains with your own domain.
+In both cases make sure to replace all the `example.com` domains with your own domain.
 
 This example does not include additional services like Element, but you should be able copy the first block and replace the `matrix.` subdomain with the subdomain of the some other service (e.g. `element.`).

examples/reverse-proxies/caddy2/Caddyfile

@@ -1,4 +1,4 @@
-matrix.example.tld {
+matrix.example.com {
 
   handle {
         encode zstd gzip
@@ -12,7 +12,7 @@ matrix.example.tld {
   }
 }
 
-matrix.example.tld:8448 {
+matrix.example.com:8448 {
     handle {
         encode zstd gzip
 
@@ -26,14 +26,14 @@ matrix.example.tld:8448 {
 }
 
 
-example.tld {
+example.com {
 # Uncomment this if you are following "(Option 3): Setting up reverse-proxying of the well-known files from the base domain's server to the Matrix server" of https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-well-known.md#option-3-setting-up-reverse-proxying-of-the-well-known-files-from-the-base-domains-server-to-the-matrix-server
     @wellknown {
         path /.well-known/matrix/*
     }
 
     handle @wellknown {
-        reverse_proxy https://matrix.example.tld {
+        reverse_proxy https://matrix.example.com {
             header_up Host {http.reverse_proxy.upstream.hostport}
         }
     }

examples/reverse-proxies/caddy2/README.md

@@ -11,6 +11,6 @@ To get started, first follow the [front the integrated reverse-proxy webserver w
 ## Using the Caddyfile
 
 You can either just use the [Caddyfile](Caddyfile) directly or append its content to your own Caddyfile.
-In both cases make sure to replace all the `example.tld` domains with your own domain.
+In both cases make sure to replace all the `example.com` domains with your own domain.
 
 This example does not include additional services like element, but you should be able copy the first block and replace the matrix subdomain with the additional services subdomain. I have not tested this though.