From 5807ffab042fcc7645ae2af9cf9eb7a8763322f6 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Sun, 10 Nov 2024 02:37:30 +0900 Subject: [PATCH] Update docs/configuring-dns.md: replace "may be necessary" with "is necessary" as Element Web is installed by default Signed-off-by: Suguru Hirahara --- docs/configuring-dns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md index 2ed642469..4ff1be848 100644 --- a/docs/configuring-dns.md +++ b/docs/configuring-dns.md @@ -32,7 +32,7 @@ To serve the base domain (`example.com`) and [Element Web](configuring-playbook- As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine). -The `element.example.com` subdomain may be necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record. +The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record. Be mindful as to how long it will take for the DNS records to propagate.