Skip to content

[doc] fixing typos in diverse files #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jacobsimionato merged 1 commit into from
Dec 17, 2025
Merged

[doc] fixing typos in diverse files #292

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/guides/agent-development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down
2 changes: 1 addition & 1 deletion docs/introduction/who-is-it-for.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:**

Expand Down
2 changes: 1 addition & 1 deletion samples/agent/adk/orchestrator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down