Fix broken links and update diagram

Author: danbarr

docs/toolhive/guides-cli/custom-permissions.mdx

@@ -231,13 +231,13 @@ architecture-beta
     service mcp_client(server)[MCP client]
     service toolhive_proxy(server)[ToolHive HTTP proxy process]
 
-    group container_runtime(server)[Container runtime]
-    group thv_internal(server)[Isolated network] in container_runtime
+    group container_runtime[Container runtime]
+    group thv_internal[Isolated network] in container_runtime
     service egress(server)[Egress proxy container] in container_runtime
     service mcp_server(server)[MCP server container] in thv_internal
     service dns_container(server)[DNS container] in container_runtime
 
-    group external(internet)[External Resources]
+    group external[External Resources]
     service external_service(internet)[External service] in external
     service external_dns(internet)[External DNS] in external
 

docs/toolhive/guides-cli/registry.md

@@ -119,9 +119,9 @@ and security profile before running it.
 - **Tools list** (line 8): The list of tools this MCP server provides
 - **Configuration** (line 16): Required and optional environment variables
   needed to run the server
-- **Permissions** (line 21): The permissions profile applied to the server,
+- **Permissions** (line 21): The permission profile applied to the server,
   including file system and network access (see
-  [Custom permissions](./custom-permissions.md))
+  [Custom permissions](./custom-permissions.mdx))
 
 ## Use a remote registry
 

docs/toolhive/guides-cli/run-mcp-servers.mdx

@@ -110,7 +110,7 @@ The optional `:ro` suffix makes the volume read-only in the container. This is
 useful for sharing files without letting the MCP server modify them.
 
 ToolHive automatically adds mounted paths to the MCP server's
-[permissions profile](./custom-permissions.md).
+[permission profile](./custom-permissions.mdx).
 
 For example, to mount a local directory to the Filesystem MCP server:
 
@@ -371,7 +371,7 @@ control your servers.
 - [`thv run` command reference](../reference/cli/thv_run.md)
 - [Client configuration](client-configuration.md)
 - [Secrets management](secrets-management.mdx)
-- [Custom permissions](custom-permissions.md)
+- [Custom permissions](custom-permissions.mdx)
 
 ## Troubleshooting
 

docs/toolhive/guides-k8s/run-mcp-k8s.md

@@ -412,7 +412,7 @@ Permission profiles can be configured in two ways:
    ```
 
 The ConfigMap should contain a JSON
-[permissions profile](../guides-cli/custom-permissions.md#create-a-custom-permissions-profile).
+[permission profile](../guides-cli/custom-permissions.mdx#create-a-custom-permission-profile).
 
 :::important
 
@@ -434,7 +434,7 @@ to learn how to connect to MCP servers using different clients.
 
 - [Deploy the operator using Helm](./deploy-operator-helm.md) - Install the
   ToolHive operator
-- [Custom permissions](../guides-cli/custom-permissions.md) - Configure
+- [Custom permissions](../guides-cli/custom-permissions.mdx) - Configure
   permission profiles
 
 ## Troubleshooting

docs/toolhive/tutorials/quickstart.mdx

@@ -276,7 +276,7 @@ server. Here are some next steps to explore:
   [`thv run <server-name>`](../reference/cli/thv_run.md)
 - Learn about [secrets management](../guides-cli/secrets-management.mdx) for MCP
   servers that require authentication
-- Explore [custom permissions](../guides-cli/custom-permissions.md) for MCP
+- Explore [custom permissions](../guides-cli/custom-permissions.mdx) for MCP
   servers
 - Set up [shell completion](../guides-cli/install.mdx#enable-shell-completion)
   to make ToolHive commands easier to use