[doc] fixing typos in diverse files (#292)

Author: didier-durand

docs/guides/agent-development.md

@@ -15,7 +15,7 @@ Building an A2UI agent:
 
 We will use the ADK to build a simple agent.  We will start with text and eventually upgrade it to A2UI.
 
-See step by step instructions at the [ADK quickstart](https://google.github.io/adk-docs/get-started/python/).
+See step-by-step instructions at the [ADK quickstart](https://google.github.io/adk-docs/get-started/python/).
 
 ```bash
 pip install google-adk
@@ -88,7 +88,7 @@ You can test out this agent with the ADK web interface:
 adk web
 ```
 
-Select `my_agent` from the list, and ask questions about restaurants in new york.  You should see a list of restaurants in the UI as plain text.
+Select `my_agent` from the list, and ask questions about restaurants in New York.  You should see a list of restaurants in the UI as plain text.
 
 ## Generating A2UI Messages
 

docs/index.md

@@ -146,7 +146,7 @@ and [transports](/transports.md) (eg: A2A, etc.) which communicate A2UI messages
     </video>
   </div>
   <p style="text-align: center; margin-top: 1rem; opacity: 0.8;">
-    Watch an agent chose to respond with a chart component to answer a numberical summary quesiton.  Then the agent chooses a Google Map component to answer a location question.  Both are custom components offered by the client.
+    Watch an agent chose to respond with a chart component to answer a numerical summary question.  Then the agent chooses a Google Map component to answer a location question.  Both are custom components offered by the client.
   </p>
 </div>
 

docs/introduction/who-is-it-for.md

@@ -38,7 +38,7 @@ Build agent orchestration platforms, frameworks, or UI integrations.
 
 Do you bring remote agents into your app?
 
-Do you ship your agent into other apps you don't necissarily control?
+Do you ship your agent into other apps you don't necessarily control?
 
 **Why A2UI:**
 

samples/agent/adk/orchestrator/README.md

@@ -4,7 +4,7 @@ This sample uses the Agent Development Kit (ADK) along with the A2A protocol to
 
 The orchestrator agent needs the A2UI extension enabled by adding the header X-A2A-Extensions=https://a2ui.org/a2a-extension/a2ui/v0.8 to requests, however it is hardcoded to true for this sample to simplify inspection.
 
-The orchestrator does an inference call on every request to decide which agent to route to, and then uses transfer_to_agent in ADK to pass the original message to the subagent. This routing is done on subsequent calls including on A2UI userAction, and a future version could optimize this by programatically routing userAction to the agent that created the surface using before_model_callback to shortcut the orchestrator LLM.
+The orchestrator does an inference call on every request to decide which agent to route to, and then uses transfer_to_agent in ADK to pass the original message to the subagent. This routing is done on subsequent calls including on A2UI userAction, and a future version could optimize this by programmatically routing userAction to the agent that created the surface using before_model_callback to shortcut the orchestrator LLM.
 
 Subagents are configured using RemoteA2aAgent which translates ADK events to A2A messages that are sent to the subagent's A2A server. The HTTP header X-A2A-Extensions=https://a2ui.org/a2a-extension/a2ui/v0.8 is added to requests from the RemoteA2aAgent to enable the A2UI extension.