summary refs log tree commit diff
path: root/docs/reverse_proxy.rst
diff options
context:
space:
mode:
authorMichael Kaye <1917473+michaelkaye@users.noreply.github.com>2019-03-19 10:37:18 +0000
committerRichard van der Hoff <1389908+richvdh@users.noreply.github.com>2019-03-19 10:37:18 +0000
commit9482a84c0a12abeae40119da2f78e84908a1591b (patch)
treeac20bbb046f41320f50d4746d5d319a93c46c6f0 /docs/reverse_proxy.rst
parentfix some typos in federate.md (diff)
downloadsynapse-9482a84c0a12abeae40119da2f78e84908a1591b.tar.xz
Repoint docs for federation (#4881)
Diffstat (limited to '')
-rw-r--r--docs/reverse_proxy.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reverse_proxy.rst b/docs/reverse_proxy.rst
index 4706061eba..cc6e66a8f3 100644
--- a/docs/reverse_proxy.rst
+++ b/docs/reverse_proxy.rst
@@ -18,7 +18,7 @@ servers do not necessarily need to connect to your server via the same server
 name or port. Indeed, clients will use port 443 by default, whereas servers
 default to port 8448. Where these are different, we refer to the 'client port'
 and the 'federation port'. See `Setting up federation
-<../README.rst#setting-up-federation>`_ for more details of the algorithm used for
+<federate.md>`_ for more details of the algorithm used for
 federation connections.
 
 Let's assume that we expect clients to connect to our server at