summary refs log tree commit diff
path: root/docs
diff options
context:
space:
mode:
authorNeil Johnson <neil@matrix.org>2019-06-11 11:12:07 +0100
committerGitHub <noreply@github.com>2019-06-11 11:12:07 +0100
commitba5422601b140e65a4d93a490882bd0752ce311f (patch)
treecc5cbf7e3dd0bc7a1f89fccd02048d9e37c0be2a /docs
parentUpdate docs/federate.md (diff)
downloadsynapse-ba5422601b140e65a4d93a490882bd0752ce311f.tar.xz
Update docs/federate.md
Co-Authored-By: Brendan Abolivier <github@brendanabolivier.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/federate.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/federate.md b/docs/federate.md
index 87d59d5088..5068583854 100644
--- a/docs/federate.md
+++ b/docs/federate.md
@@ -155,7 +155,7 @@ Practically speaking, this is no longer necessary.
 
 If you are using a reverse proxy for all of your TLS traffic, then you can set
 `no_tls: True`. In that case, the only reason Synapse needs the certificate is
-to populate a legacy 'tls_fingerprints' field in the federation API. This is
+to populate a legacy `tls_fingerprints` field in the federation API. This is
 ignored by Synapse 0.99.0 and later, and the only time pre-0.99 Synapses will
 check it is when attempting to fetch the server keys - and generally this is
 delegated via `matrix.org`, which is on 0.99.0.