From d1e8666ac88ad2b732c7f6ca274d856e6c3bef86 Mon Sep 17 00:00:00 2001
From: babolivier <babolivier@users.noreply.github.com>
Date: Mon, 21 Nov 2022 11:41:11 +0000
Subject: deploy: 640cb3c81c927535a18b85c49a1cc2d856d03c2e

---
 develop/usage/administration/admin_api/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'develop/usage/administration/admin_api/index.html')

diff --git a/develop/usage/administration/admin_api/index.html b/develop/usage/administration/admin_api/index.html
index 2b6447abc1..0d5587271d 100644
--- a/develop/usage/administration/admin_api/index.html
+++ b/develop/usage/administration/admin_api/index.html
@@ -159,7 +159,7 @@ command. This is a script that is distributed as part of synapse. It is possibly
 already on your <code>$PATH</code> depending on how Synapse was installed.</p>
 <p>Finding your user's <code>access_token</code> is client-dependent, but will usually be shown in the client's settings.</p>
 <h2 id="making-an-admin-api-request"><a class="header" href="#making-an-admin-api-request">Making an Admin API request</a></h2>
-<p>For security reasons, we <a href="reverse_proxy.html#synapse-administration-endpoints">recommend</a>
+<p>For security reasons, we <a href="../../../reverse_proxy.html#synapse-administration-endpoints">recommend</a>
 that the Admin API (<code>/_synapse/admin/...</code>) should be hidden from public view using a
 reverse proxy. This means you should typically query the Admin API from a terminal on
 the machine which runs Synapse.</p>
-- 
cgit 1.5.1