Fix typos in docs

Author: agu-z

docs/overview/architecture.mdx

@@ -17,11 +17,11 @@ The protocol architecture follows several key principles:
 
 When the user tries to connect to an agent, the editor boots the agent sub-process on demand, and all communication happens over stdin/stdout.
 
-Each connection can suppport several concurrent sessions, so you can have multiple trains of thought going on at once.
+Each connection can support several concurrent sessions, so you can have multiple trains of thought going on at once.
 
 ![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.
+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 bidirectional requests to allow the agent to make requests of the code editor: for example to request permissions for a tool call.
 
 ## MCP
 

docs/protocol/extensibility.mdx

@@ -55,7 +55,7 @@ In addition to the requests specified by the protocol, implementations **MAY** e
 }
 ```
 
-Upon receiveing a custom request, implementations **MUST** respond accordingly with the provided `id`:
+Upon receiving a custom request, implementations **MUST** respond accordingly with the provided `id`:
 
 ```json
 {
@@ -70,7 +70,7 @@ Upon receiveing a custom request, implementations **MUST** respond accordingly w
 }
 ```
 
-If the receiveing end doesn't recognize the custom method name, it should respond with the standard "Method not found" error:
+If the receiving end doesn't recognize the custom method name, it should respond with the standard "Method not found" error:
 
 ```json
 {