summary refs log tree commit diff
diff options
context:
space:
mode:
authorNeil Johnson <neil@matrix.org>2019-06-11 11:11:50 +0100
committerGitHub <noreply@github.com>2019-06-11 11:11:50 +0100
commit0fd8414df199d06209c8c4cb13b5fc7a5d7ef1fb (patch)
tree0c2f85b8c05f2723f27e1909375c526524586759
parentMerge branch 'neilj/improve-federation-docs' of github.com:matrix-org/synapse... (diff)
downloadsynapse-0fd8414df199d06209c8c4cb13b5fc7a5d7ef1fb.tar.xz
Update docs/federate.md
Co-Authored-By: Brendan Abolivier <github@brendanabolivier.com>
-rw-r--r--docs/federate.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/federate.md b/docs/federate.md
index 52e9c63b64..35d214e2f7 100644
--- a/docs/federate.md
+++ b/docs/federate.md
@@ -105,7 +105,7 @@ If your homeserver listens on the default federation port (8448), and your
 `server_name` points to the host that your homeserver runs on, you do not need an SRV record or `.well-known/matrix/server` URI.
 
 For instance, if you registered `example.com` and pointed its DNS A record at a
-fresh Upcloud VPS or similar, you could install Synapse on that host,
+fresh server, you could install Synapse on that host,
 giving it a server_name of `example.com`, and it would automatically generate a
 valid TLS certificate for you via Let's Encrypt and no SRV record or
 `.well-known` URI would be needed.