summary refs log tree commit diff
diff options
context:
space:
mode:
authorRichard van der Hoff <1389908+richvdh@users.noreply.github.com>2019-02-07 18:46:02 +0000
committerGitHub <noreply@github.com>2019-02-07 18:46:02 +0000
commit9b7aa543d9fc90d3a754ab129a619cfff6a71355 (patch)
tree1314922b142bd0ac0cd80601e44a74220d8ec2a1
parentFix docker upload job to push -py2 images (#4576) (diff)
downloadsynapse-9b7aa543d9fc90d3a754ab129a619cfff6a71355.tar.xz
clarify option 1
-rw-r--r--docs/MSC1711_certificates_FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/MSC1711_certificates_FAQ.md b/docs/MSC1711_certificates_FAQ.md
index eee37d9457..414af96ef3 100644
--- a/docs/MSC1711_certificates_FAQ.md
+++ b/docs/MSC1711_certificates_FAQ.md
@@ -112,7 +112,7 @@ _matrix._tcp.example.com. IN SRV 10 5 443 customer.example.net.
 
 In this situation, you have two choices for how to proceed:
 
-#### Option 1: give Synapse a certificate for your matrix domain
+#### Option 1: give Synapse (or a reverse-proxy) a certificate for your matrix domain
 
 Synapse 1.0 will expect your server to present a TLS certificate for your
 `server_name` (`example.com` in the above example). You can achieve this by