Rearrange admin API fs heirarchy to match sidebar

I've kept the RST redirect file in-place though

2 files changed, 5 insertions, 5 deletions

diff --git a/docs/usage/configuration/config_documentation.md b/docs/usage/configuration/config_documentation.md

index 20ed41e16a..5b66be0918 100644
--- a/docs/usage/configuration/config_documentation.md
+++ b/docs/usage/configuration/config_documentation.md
@@ -1702,9 +1702,9 @@ and the original media will be removed. If either of these options are unset,
 then media of that type will not be purged.
 
 Local or cached remote media that has been
-[quarantined](../../admin_api/media_admin_api.md#quarantining-media-in-a-room)
+[quarantined](../../administration/admin_api/media_admin_api.md#quarantining-media-in-a-room)
 will not be deleted. Similarly, local media that has been marked as
-[protected from quarantine](../../admin_api/media_admin_api.md#protecting-media-from-being-quarantined)
+[protected from quarantine](../../administration/admin_api/media_admin_api.md#protecting-media-from-being-quarantined)
 will not be deleted.
 
 Example configuration:
@@ -2068,7 +2068,7 @@ enable_3pid_lookup: false
 ### `registration_requires_token`
 
 Require users to submit a token during registration.
-Tokens can be managed using the admin [API](../administration/admin_api/registration_tokens.md).
+Tokens can be managed using the admin [API](../../administration/admin_api/registration_tokens.md).
 Disabling this option will not delete any tokens previously generated.
 Defaults to `false`. Set to `true` to enable.
 
@@ -3425,7 +3425,7 @@ This option has the following sub-options:
     
     These indexes are built the first time Synapse starts; admins can
     manually trigger a rebuild via the API following the instructions
-    [for running background updates](../administration/admin_api/background_updates.md#run),
+    [for running background updates](../../administration/admin_api/background_updates.md#run),
     set to true to return search results containing all known users, even if that
     user does not share a room with the requester.
 * `prefer_local_users`: Defines whether to prefer local users in search query results.
diff --git a/docs/usage/configuration/user_directory.md b/docs/usage/configuration/user_directory.md

index 31da9fd4b3..5fa6079ba7 100644
--- a/docs/usage/configuration/user_directory.md
+++ b/docs/usage/configuration/user_directory.md
@@ -7,7 +7,7 @@ who are present in a publicly viewable room present on the server.
 
 The directory info is stored in various tables, which can (typically after
 DB corruption) get stale or out of sync. If this happens, for now the
-solution to fix it is to use the [admin API](../administration/admin_api/background_updates.md#run)
+solution to fix it is to use the [admin API](../../administration/admin_api/background_updates.md#run)
 and execute the job `regenerate_directory`. This should then start a background task to
 flush the current tables and regenerate the directory.