Fix images

Author: ConradIrwin

docs/overview/architecture.mdx

@@ -19,16 +19,16 @@ When the user tries to connect to an agent, the editor boots the agent sub-proce
 
 Each connection can suppport several concurrent sessions, so you can have multiple trains of thought going on at once.
 
-![Server Client setup](./images/server-client.svg)
+![Server Client setup](../images/server-client.svg)
 
 ACP makes heavy use of JSON-RPC notifications to allow the agent to stream updates to the UI in real-time. It also uses JSON-RPC's bidrectional requests to allow the agent to make requests of the code editor: for example to request permissions for a tool call.
 
 ## MCP
 
 Commonly the code editor will have user-configured MCP servers. When forwarding the prompt from the user, it passes configuration for these to the agent. This allows the agent to connect directly to the MCP server.
 
-![MCP Server connection](./images/mcp.svg)
+![MCP Server connection](../images/mcp.svg)
 
 The code editor may itself also wish to export MCP based tools. Instead of trying to run MCP and ACP on the same socket, the code editor can provide its own MCP server as configuration. As agents may only support MCP over stdio, the code editor can provide a small proxy that tunnels requests back to itself:
 
-![MCP connection to self](./images/mcp-proxy.svg)
+![MCP connection to self](../images/mcp-proxy.svg)