summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthew Hodgson <matthew@matrix.org>2019-02-05 17:02:52 +0000
committerMatthew Hodgson <matthew@matrix.org>2019-02-05 17:02:52 +0000
commite15936b5ce9385575dd3558cf52a902bff82b5f4 (patch)
tree9969ef6b844b5c87586e5f5776cc46d81cba2618
parentMD tweaks (diff)
downloadsynapse-e15936b5ce9385575dd3558cf52a902bff82b5f4.tar.xz
MD tweaks
-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 b3726df54b..097503e579 100644
--- a/docs/MSC1711_certificates_FAQ.md
+++ b/docs/MSC1711_certificates_FAQ.md
@@ -228,7 +228,7 @@ find it easier to direct federation traffic to a reverse-proxy and manage their
 own TLS certificates, and this is a supported configuration.
 
 ### Do I still need to give my TLS certificates to Synapse if I am using a
-reverse-proxy?
+### reverse-proxy?
 
 Practically speaking, this is no longer necessary.