coder
diff --git a/‎docs/admin/networking/README.md
+9-9 b/‎docs/admin/networking/README.md
+9-9
diff --git a/‎docs/architecture/1k-users.md
-51 b/‎docs/architecture/1k-users.md
-51
diff --git a/‎docs/architecture/2k-users.md
-59 b/‎docs/architecture/2k-users.md
-59
diff --git a/‎docs/architecture/3k-users.md
-62 b/‎docs/architecture/3k-users.md
-62
@@ -29,28 +29,28 @@ In order for clients to be able to establish direct connections:
 > **Note:** Direct connections via the web browser are not supported. To improve
 > latency for browser-based applications running inside Coder workspaces in
 > regions far from the Coder control plane, consider deploying one or more
-> [workspace proxies](../admin/workspace-proxies.md).
+> [workspace proxies](./workspace-proxies.md).
 
 - The client is connecting using the CLI (e.g. `coder ssh` or
   `coder port-forward`). Note that the
   [VSCode extension](https://marketplace.visualstudio.com/items?itemName=coder.coder-remote)
   and [JetBrains Plugin](https://plugins.jetbrains.com/plugin/19620-coder/), and
-  [`ssh coder.<workspace>`](../cli/config-ssh.md) all utilize the CLI to
+  [`ssh coder.<workspace>`](../../reference/cli/config-ssh.md) all utilize the CLI to
   establish a workspace connection.
 - Either the client or workspace agent are able to discover a reachable
   `ip:port` of their counterpart. If the agent and client are able to
   communicate with each other using their locally assigned IP addresses, then a
   direct connection can be established immediately. Otherwise, the client and
   agent will contact
-  [the configured STUN servers](../cli/server.md#derp-server-stun-addresses) to
+  [the configured STUN servers](../../reference/cli/server.md#derp-server-stun-addresses) to
   try and determine which `ip:port` can be used to communicate with their
   counterpart. See [STUN and NAT](./stun.md) for more details on how this
   process works.
 - All outbound UDP traffic must be allowed for both the client and the agent on
   **all ports** to each others' respective networks.
   - To establish a direct connection, both agent and client use STUN. This
     involves sending UDP packets outbound on `udp/3478` to the configured
-    [STUN server](../cli/server.md#--derp-server-stun-addresses). If either the
+    [STUN server](../../reference/cli/server.md#--derp-server-stun-addresses). If either the
     agent or the client are unable to send and receive UDP packets to a STUN
     server, then direct connections will not be possible.
   - Both agents and clients will then establish a
@@ -61,7 +61,7 @@ In order for clients to be able to establish direct connections:
 ## coder server
 
 Workspaces connect to the coder server via the server's external address, set
-via [`ACCESS_URL`](../admin/configure.md#access-url). There must not be a NAT
+via [`ACCESS_URL`](../../admin/configure.md#access-url). There must not be a NAT
 between workspaces and coder server.
 
 Users connect to the coder server's dashboard and API through its `ACCESS_URL`
@@ -105,14 +105,14 @@ for more information on how this process works.
 
 If a direct connection is not available (e.g. client or server is behind NAT),
 Coder will use a relayed connection. By default,
-[Coder uses Google's public STUN server](../cli/server.md#--derp-server-stun-addresses),
+[Coder uses Google's public STUN server](../../reference/cli/server.md#--derp-server-stun-addresses),
 but this can be disabled or changed for
-[offline deployments](../install/offline.md).
+[offline deployments](../../install/offline.md).
 
 ### Relayed connections
 
 By default, your Coder server also runs a built-in DERP relay which can be used
-for both public and [offline deployments](../install/offline.md).
+for both public and [offline deployments](../../install/offline.md).
 
 However, Tailscale has graciously allowed us to use
 [their global DERP relays](https://tailscale.com/kb/1118/custom-derp-servers/#what-are-derp-servers).
@@ -169,7 +169,7 @@ with security policies. In these cases, pass the `--browser-only` flag to
 `coder server` or set `CODER_BROWSER_ONLY=true`.
 
 With browser-only connections, developers can only connect to their workspaces
-via the web terminal and [web IDEs](../ides/web-ides.md).
+via the web terminal and [web IDEs](../../user-guides/workspace-access/web-ides.md).
 
 ## Troubleshooting