diff --git a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
index f9a1b666a..3fcc06eac 100644
--- a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
+++ b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
@@ -10,7 +10,7 @@ Aspire provides two complementary sets of certificate APIs:
1. **HTTPS endpoint APIs**: Configure the certificates that resources use for their own HTTPS endpoints (server authentication)
2. **Certificate trust APIs**: Configure which certificates resources trust when making outbound HTTPS connections (client authentication)
-Both sets of APIs work together to enable secure HTTPS communication during local development. For example, a Vite frontend might use `WithHttpsDeveloperCertificate` to serve HTTPS traffic, while also using `WithDeveloperCertificateTrust` to trust the dashboard's OTLP endpoint certificate.
+Both sets of APIs work together to enable secure HTTPS communication during local development. For example, a Vite frontend might use `WithHttpsDeveloperCertificate` to serve HTTPS traffic, while also using `WithDeveloperCertificateTrust` to trust the dashboard's OTLP endpoint certificate.
This page describes manual MCP configuration for Aspire versions 9.0 through 13.0, or for situations where you need more control over the configuration.
diff --git a/src/frontend/src/content/docs/dashboard/overview.mdx b/src/frontend/src/content/docs/dashboard/overview.mdx
index dce258055..1cb5eeda1 100644
--- a/src/frontend/src/content/docs/dashboard/overview.mdx
+++ b/src/frontend/src/content/docs/dashboard/overview.mdx
@@ -64,7 +64,7 @@ For more information, see the [Standalone Aspire dashboard](/dashboard/standalon
## Configuration
-The dashboard is configured when it starts up. Configuration includes frontend and OTLP addresses, the resource service endpoint, authentication, telemetry limits and more.
+The dashboard is configured when it starts up. Configuration includes frontend and OTLP addresses, the resource service endpoint, authentication, telemetry limits and more.
For more information, see [Aspire dashboard configuration](/dashboard/configuration/).
diff --git a/src/frontend/src/content/docs/dashboard/security-considerations.mdx b/src/frontend/src/content/docs/dashboard/security-considerations.mdx
index 250078f33..46e9937b5 100644
--- a/src/frontend/src/content/docs/dashboard/security-considerations.mdx
+++ b/src/frontend/src/content/docs/dashboard/security-considerations.mdx
@@ -35,7 +35,7 @@ The dashboard is shipped as a Docker image and can be used without the rest of A
- Browser frontend authenticated with a browser token.
- Incoming telemetry is unsecured. Warnings are displayed in the console and dashboard UI.
-The telemetry endpoint accepts incoming OTLP data without authentication. When the endpoint is unsecured, the dashboard is open to receiving telemetry from untrusted apps.
+The telemetry endpoint accepts incoming OTLP data without authentication. When the endpoint is unsecured, the dashboard is open to receiving telemetry from untrusted apps.
For information about securing the telemetry when running the dashboard in standalone mode, see [Securing the telemetry endpoint](#secure-telemetry-endpoint).
diff --git a/src/frontend/src/content/docs/dashboard/standalone.mdx b/src/frontend/src/content/docs/dashboard/standalone.mdx
index b10372875..b322e0e23 100644
--- a/src/frontend/src/content/docs/dashboard/standalone.mdx
+++ b/src/frontend/src/content/docs/dashboard/standalone.mdx
@@ -121,7 +121,7 @@ The dashboard has functionality for viewing Aspire resources. The dashboard reso
Apps send telemetry to the dashboard using [OpenTelemetry Protocol (OTLP)](https://opentelemetry.io/docs/specs/otlp/). The dashboard must expose a port for receiving OpenTelemetry data, and apps are configured to send data to that address.
-A Docker command was shown earlier to [start the dashboard](#start-the-dashboard). It configured the container to receive OpenTelemetry data on port `4317` (gRPC) and port `4318` (HTTP). The OTLP endpoint addresses are `http://localhost:4317` for gRPC and `http://localhost:4318` for HTTP.
+A Docker command was shown earlier to [start the dashboard](#start-the-dashboard). It configured the container to receive OpenTelemetry data on port `4317` (gRPC) and port `4318` (HTTP). The OTLP endpoint addresses are `http://localhost:4317` for gRPC and `http://localhost:4318` for HTTP.
### Configure OpenTelemetry SDK
diff --git a/src/frontend/src/content/docs/deployment/javascript-apps.mdx b/src/frontend/src/content/docs/deployment/javascript-apps.mdx
index 6a27023ba..60fd76f98 100644
--- a/src/frontend/src/content/docs/deployment/javascript-apps.mdx
+++ b/src/frontend/src/content/docs/deployment/javascript-apps.mdx
@@ -28,7 +28,7 @@ For deployment, `AddViteApp` and `AddJavaScriptApp` should be treated as fronten
To deploy a JavaScript frontend, you must choose which other resource owns the public HTTP surface in production:
- Use `PublishWithContainerFiles(...)` when your backend or web server will serve the built frontend files.
-- Use `PublishWithStaticFiles(...)` when your reverse proxy, gateway, or BFF will serve the built frontend files.
+- Use `PublishWithStaticFiles(...)` when your reverse proxy, gateway, or BFF will serve the built frontend files.
If you only add a Vite or JavaScript app and reference backend services, Aspire still needs one of these production hosting patterns to know who serves the built frontend in deployment.
diff --git a/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx b/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
index c87cf16e5..423d9691b 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
@@ -12,7 +12,7 @@ import { Badge } from '@astrojs/starlight/components';
class:list={'mb-1'}
/>
-> MCP server types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
+> MCP server types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
This diagnostic warning is reported when using the experimental `WithMcpServer` extension method and related Model Context Protocol (MCP) server APIs. These APIs enable Aspire tooling to discover and proxy MCP servers exposed by resources.
diff --git a/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx b/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
index 0e47ee46e..b4472d6b8 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
@@ -12,7 +12,7 @@ import { Badge } from '@astrojs/starlight/components';
class:list={'mb-1'}
/>
-> The PostgreSQL MCP integration APIs are experimental and subject to change or removal in future updates. Suppress this diagnostic to proceed.
+> The PostgreSQL MCP integration APIs are experimental and subject to change or removal in future updates. Suppress this diagnostic to proceed.
The `WithPostgresMcp` extension method for adding Model Context Protocol (MCP) support to PostgreSQL resources is an experimental feature. This API may change or be removed in future versions.
diff --git a/src/frontend/src/content/docs/diagnostics/overview.mdx b/src/frontend/src/content/docs/diagnostics/overview.mdx
index d1a250185..efa369cf9 100644
--- a/src/frontend/src/content/docs/diagnostics/overview.mdx
+++ b/src/frontend/src/content/docs/diagnostics/overview.mdx
@@ -43,7 +43,7 @@ The following table lists the possible MSBuild and analyzer warnings and errors
| [ASPIREFILESYSTEM001](/diagnostics/aspirefilesystem001/) | (Experimental) Warning | File system service types and members are for evaluation purposes only and are subject to change or removal in future updates. |
| [ASPIREINTERACTION001](/diagnostics/aspireinteraction001/) | (Experimental) Warning | Interaction service types and members are for evaluation purposes only and are subject to change or removal in future updates. |
| [ASPIREHOSTINGPYTHON001](/diagnostics/aspirehostingpython001/) | (Experimental) Error | `AddPythonApp` is for evaluation purposes only and is subject to change or removal in future updates. |
-| [ASPIREMCP001](/diagnostics/aspiremcp001/) | (Experimental) Warning | MCP server types and members are for evaluation purposes only and are subject to change or removal in future updates. |
+| [ASPIREMCP001](/diagnostics/aspiremcp001/) | (Experimental) Warning | MCP server types and members are for evaluation purposes only and are subject to change or removal in future updates. |
| [ASPIREPIPELINES001](/diagnostics/aspirepipelines001/) | (Experimental) Error | Pipeline infrastructure APIs are for evaluation purposes only and are subject to change or removal in future updates. |
| [ASPIREPIPELINES002](/diagnostics/aspirepipelines002/) | (Experimental) Error | Deployment state manager APIs are for evaluation purposes only and are subject to change or removal in future updates. |
| [ASPIREPIPELINES003](/diagnostics/aspirepipelines003/) | (Experimental) Error | Container image build APIs are for evaluation purposes only and are subject to change or removal in future updates. |
diff --git a/src/frontend/src/content/docs/fundamentals/telemetry.mdx b/src/frontend/src/content/docs/fundamentals/telemetry.mdx
index 54943bbdb..b4c579894 100644
--- a/src/frontend/src/content/docs/fundamentals/telemetry.mdx
+++ b/src/frontend/src/content/docs/fundamentals/telemetry.mdx
@@ -42,7 +42,7 @@ For more information, see [OpenTelemetry configuration](/get-started/csharp-serv
OpenTelemetry has a [list of known environment variables](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/) that configure the most important behavior for collecting and exporting telemetry. OpenTelemetry SDKs, including the .NET SDK, support reading these variables.
-Aspire projects launch with environment variables that configure the name and ID of the app in exported telemetry and set the address endpoint of the OTLP server to export data. For example:
+Aspire projects launch with environment variables that configure the name and ID of the app in exported telemetry and set the address endpoint of the OTLP server to export data. For example:
- `OTEL_SERVICE_NAME=myfrontend`
- `OTEL_RESOURCE_ATTRIBUTES=service.instance.id=1a5f9c1e-e5ba-451b-95ee-ced1ee89c168`
diff --git a/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx b/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
index 061599490..4f997baf1 100644
--- a/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
+++ b/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
@@ -610,7 +610,7 @@ For more information, see [Service Defaults](/get-started/csharp-service-default
-If your app includes Node.js or TypeScript services, configure OpenTelemetry inside the service and point it at the Aspire OTLP endpoint.
+If your app includes Node.js or TypeScript services, configure OpenTelemetry inside the service and point it at the Aspire OTLP endpoint.
diff --git a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
index 5f60c4871..d9abb12e5 100644
--- a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
+++ b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
@@ -10,7 +10,7 @@ import AsciinemaPlayer from '@components/AsciinemaPlayer.astro';
import LoopingVideo from '@components/LoopingVideo.astro';
import LearnMore from '@components/LearnMore.astro';
-Aspire provides a first-class setup experience for AI coding agents. Run `aspire agent init` in your project and your AI assistant — whether it's GitHub Copilot, Claude Code, or another MCP-compatible tool — can immediately understand, build, debug, and monitor your distributed applications.
+Aspire provides a first-class setup experience for AI coding agents. Run `aspire agent init` in your project and your AI assistant — whether it's GitHub Copilot, Claude Code, or another MCP-compatible tool — can immediately understand, build, debug, and monitor your distributed applications.
## Why Aspire for coding agents
diff --git a/src/frontend/src/content/docs/get-started/aspire-mcp-server.mdx b/src/frontend/src/content/docs/get-started/aspire-mcp-server.mdx
index 63af887bd..bf0b0bf9c 100644
--- a/src/frontend/src/content/docs/get-started/aspire-mcp-server.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-mcp-server.mdx
@@ -6,7 +6,7 @@ description: Learn about the Aspire MCP server tools, security model, and troubl
import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
import LearnMore from '@components/LearnMore.astro';
-The Aspire MCP server gives AI coding agents direct runtime access to your running Aspire application. Through the Model Context Protocol (MCP), agents can query resource status, read logs, inspect distributed traces, and execute commands — without you copy-pasting terminal output.
+The Aspire MCP server gives AI coding agents direct runtime access to your running Aspire application. Through the Model Context Protocol (MCP), agents can query resource status, read logs, inspect distributed traces, and execute commands — without you copy-pasting terminal output.
The MCP server is configured automatically when you run `aspire agent init` and select **Install Aspire MCP server**.
diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 1ca7fabd2..26eddc06f 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -24,7 +24,7 @@ The official Aspire extension for VS Code. Run, debug, and deploy your Aspire ap
| **Integrations** | Add databases, queues, and cloud services from the Command Palette |
| **Scaffolding** | Create new Aspire projects from templates |
| **Deploy** | Generate deployment artifacts or push to cloud targets |
-| **MCP** | Let AI tools like GitHub Copilot see your running app via the Model Context Protocol |
+| **MCP** | Let AI tools like GitHub Copilot see your running app via the Model Context Protocol |
| **Multi-language** | Debug C#, Python, Node.js, Azure Functions, and browser apps together |
## Prerequisites
diff --git a/src/frontend/src/content/docs/get-started/first-app.mdx b/src/frontend/src/content/docs/get-started/first-app.mdx
index 861aa0ea1..06b12d76d 100644
--- a/src/frontend/src/content/docs/get-started/first-app.mdx
+++ b/src/frontend/src/content/docs/get-started/first-app.mdx
@@ -126,7 +126,7 @@ To create your first Aspire application, use the [Aspire CLI](/get-started/insta
If prompted for additional selections, use the and keys to navigate the options. Press to confirm your selection.
:::note[AI agent environments]
- When prompted "Would you like to configure AI agent environments for this project?", select `y`. This sets up workspace configurations (such as the Aspire skill file and MCP server settings) for your project, enabling a richer experience with AI coding assistants. For more information, see [Use AI coding agents](/get-started/ai-coding-agents/) and the [`aspire agent init`](/reference/cli/commands/aspire-agent-init/) reference.
+ When prompted "Would you like to configure AI agent environments for this project?", select `y`. This sets up workspace configurations (such as the Aspire skill file and MCP server settings) for your project, enabling a richer experience with AI coding assistants. For more information, see [Use AI coding agents](/get-started/ai-coding-agents/) and the [`aspire agent init`](/reference/cli/commands/aspire-agent-init/) reference.
:::
diff --git a/src/frontend/src/content/docs/get-started/glossary.mdx b/src/frontend/src/content/docs/get-started/glossary.mdx
index 34b1e8c22..e1989cf27 100644
--- a/src/frontend/src/content/docs/get-started/glossary.mdx
+++ b/src/frontend/src/content/docs/get-started/glossary.mdx
@@ -269,7 +269,7 @@ Access it at the URL shown when you run `aspire run` (typically `http://localhos
### OpenTelemetry
-**OpenTelemetry** (OTEL) is the observability standard that Aspire uses for:
+**OpenTelemetry** (OTEL) is the observability standard that Aspire uses for:
- **Logs** - Structured logging with context
- **Traces** - Following requests across services
@@ -320,7 +320,7 @@ These terms appear frequently in API documentation and advanced usage:
| Concept | Definition |
|---------|------------|
-| DAG | Directed acyclic graph—the structure of resource dependencies. |
+| DAG | Directed acyclic graph—the structure of resource dependencies. |
| Heterogeneous DAG | DAG containing varied resource types (projects, containers, cloud). |
| Publisher | Component that emits deployment artifacts from the app model. |
| Hoisting | Leaving a value unresolved for later substitution at runtime. |
diff --git a/src/frontend/src/content/docs/get-started/resource-mcp-servers.mdx b/src/frontend/src/content/docs/get-started/resource-mcp-servers.mdx
index 1343416f2..74b06ace2 100644
--- a/src/frontend/src/content/docs/get-started/resource-mcp-servers.mdx
+++ b/src/frontend/src/content/docs/get-started/resource-mcp-servers.mdx
@@ -6,7 +6,7 @@ description: Learn how to expose MCP tools from Aspire resources and interact wi
import { Aside, Code, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
import LearnMore from '@components/LearnMore.astro';
-Aspire resources can expose their own MCP (Model Context Protocol) servers, enabling AI coding agents to interact directly with databases, APIs, and other services. For example, a PostgreSQL resource can expose SQL query tools, allowing an agent to run queries without leaving the conversation.
+Aspire resources can expose their own MCP (Model Context Protocol) servers, enabling AI coding agents to interact directly with databases, APIs, and other services. For example, a PostgreSQL resource can expose SQL query tools, allowing an agent to run queries without leaving the conversation.
## How it works
diff --git a/src/frontend/src/content/docs/get-started/what-is-aspire.mdx b/src/frontend/src/content/docs/get-started/what-is-aspire.mdx
index 6c916281b..c1b2ea1e2 100644
--- a/src/frontend/src/content/docs/get-started/what-is-aspire.mdx
+++ b/src/frontend/src/content/docs/get-started/what-is-aspire.mdx
@@ -15,7 +15,7 @@ Aspire is an agent-ready, code-first tool to compose, debug, and deploy any dist
Picture your app as a set of services, databases, queues, caches, and frontends. In production they work together as one system, but during development they often need to be started separately, configured by hand, and debugged across multiple terminals and dashboards. Aspire gives you one place to define that system, one command to run it, and one toolchain to observe it.
-You describe your architecture in an AppHost, run it locally with `aspire run`, inspect it in the Aspire Dashboard, and deploy the same application model to your target environment. Aspire also works well with AI coding agents through the Aspire CLI, skill files, and MCP server, so agents can understand and operate against the same app model you do.
+You describe your architecture in an AppHost, run it locally with `aspire run`, inspect it in the Aspire Dashboard, and deploy the same application model to your target environment. Aspire also works well with AI coding agents through the Aspire CLI, skill files, and MCP server, so agents can understand and operate against the same app model you do.
## Why Aspire?
diff --git a/src/frontend/src/content/docs/integrations/dotnet/maui.mdx b/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
index fe2455f12..426e95275 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
@@ -325,7 +325,7 @@ Dev Tunnels provide a secure way to expose your local web services to mobile dev
### OpenTelemetry data collection
-The `WithOtlpDevTunnel()` method creates a Dev Tunnel specifically for OpenTelemetry protocol (OTLP) traffic, allowing telemetry data from your iOS and Android apps to reach the Aspire dashboard. This is essential for monitoring and debugging your mobile apps through the Aspire dashboard.
+The `WithOtlpDevTunnel()` method creates a Dev Tunnel specifically for OpenTelemetry protocol (OTLP) traffic, allowing telemetry data from your iOS and Android apps to reach the Aspire dashboard. This is essential for monitoring and debugging your mobile apps through the Aspire dashboard.
### Windows and Mac Catalyst
diff --git a/src/frontend/src/content/docs/integrations/security/keycloak.mdx b/src/frontend/src/content/docs/integrations/security/keycloak.mdx
index ef5d720b6..43a5350e5 100644
--- a/src/frontend/src/content/docs/integrations/security/keycloak.mdx
+++ b/src/frontend/src/content/docs/integrations/security/keycloak.mdx
@@ -157,7 +157,7 @@ var apiService = builder.AddProject("apiservice")
The realm import files are mounted at `/opt/keycloak/data/import` in the Keycloak container. Realm import files are JSON files that represent the realm configuration.
-### Export telemetry to OTLP collector
+### Export telemetry to OTLP collector
Keycloak containers can export telemetry to your OTLP collector using the `WithOtlpExporter` method:
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx
index 364a903fb..489a2ace6 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx
@@ -9,7 +9,7 @@ import Include from '@components/Include.astro';
## Name
-`aspire agent init` - Initialize MCP server configuration for detected agent environments.
+`aspire agent init` - Initialize MCP server configuration for detected agent environments.
## Synopsis
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-mcp.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-mcp.mdx
index caba58836..ea96b88c4 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-mcp.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent-mcp.mdx
@@ -9,7 +9,7 @@ import Include from '@components/Include.astro';
## Name
-`aspire agent mcp` - Start the MCP (Model Context Protocol) server.
+`aspire agent mcp` - Start the MCP (Model Context Protocol) server.
## Synopsis
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent.mdx
index 526db9eb1..fa66d5853 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-agent.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-agent.mdx
@@ -21,7 +21,7 @@ aspire agent [command] [options]
## Description
-The `aspire agent` command manages AI agent integrations for Aspire. This includes starting the MCP (Model Context Protocol) server and initializing agent environment configurations. The MCP server enables AI assistants and development tools to interact with your Aspire AppHost, providing capabilities such as resource management, diagnostics, and observability.
+The `aspire agent` command manages AI agent integrations for Aspire. This includes starting the MCP (Model Context Protocol) server and initializing agent environment configurations. The MCP server enables AI assistants and development tools to interact with your Aspire AppHost, providing capabilities such as resource management, diagnostics, and observability.
## Options
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-call.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-call.mdx
index c727ed970..003d172b1 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-call.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-call.mdx
@@ -8,7 +8,7 @@ import { Steps } from '@astrojs/starlight/components';
## Name
-`aspire mcp call` - Call an MCP tool on a running resource.
+`aspire mcp call` - Call an MCP tool on a running resource.
## Synopsis
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-tools.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-tools.mdx
index d4920a2bb..7834ef51d 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-tools.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp-tools.mdx
@@ -8,7 +8,7 @@ import { Steps } from '@astrojs/starlight/components';
## Name
-`aspire mcp tools` - List MCP tools exposed by running resources.
+`aspire mcp tools` - List MCP tools exposed by running resources.
## Synopsis
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp.mdx
index b52d17a41..6015fbd42 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-mcp.mdx
@@ -8,7 +8,7 @@ import { Aside } from '@astrojs/starlight/components';
## Name
-`aspire mcp` - Interact with MCP tools exposed by Aspire resources.
+`aspire mcp` - Interact with MCP tools exposed by Aspire resources.
## Synopsis
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire.mdx
index 244741302..6b2586155 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire.mdx
@@ -74,7 +74,7 @@ The following commands are available:
| [`aspire config`](../aspire-config/) | Stable | Manage CLI configuration including feature flags. |
| [`aspire docs`](../aspire-docs/) | Stable | Browse and search Aspire documentation from aspire.dev. |
| [`aspire doctor`](../aspire-doctor/) | Stable | Diagnose Aspire environment issues and verify setup. |
-| [`aspire mcp`](../aspire-mcp/) | Stable | Interact with MCP tools exposed by Aspire resources. |
+| [`aspire mcp`](../aspire-mcp/) | Stable | Interact with MCP tools exposed by Aspire resources. |
| [`aspire secret`](../aspire-secret/) | Stable | Manage apphost user secrets. |
## Examples
diff --git a/src/frontend/src/content/docs/reference/cli/overview.mdx b/src/frontend/src/content/docs/reference/cli/overview.mdx
index 000563a80..504bb1007 100644
--- a/src/frontend/src/content/docs/reference/cli/overview.mdx
+++ b/src/frontend/src/content/docs/reference/cli/overview.mdx
@@ -210,7 +210,7 @@ Use `aspire doctor` to verify that your environment is ready for Aspire developm
[Command reference: `aspire doctor`](../commands/aspire-doctor/) and [Command reference: `aspire certs`](../commands/aspire-certs/)
-## Work with MCP tools
+## Work with MCP tools
The `aspire mcp` command lets you list and call MCP tools exposed by running resources. If you need to start the MCP server used by compatible AI agents, use `aspire agent mcp`.
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
index 32dd8e4a7..f2ca35363 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
@@ -17,7 +17,7 @@ import { Code, Tabs, Steps, TabItem, Aside, Icon } from '@astrojs/starlight/comp
import resourcesParametersView from '@assets/whats-new/resources-parameters-view.png';
import genaiVisualizerTooldefinitions from '@assets/whats-new/genai-visualizer-tooldefinitions.png';
-Aspire 13.1 builds on the multi-language foundation established in Aspire 13, delivering significant improvements to the CLI experience, enhanced MCP (Model Context Protocol) support for AI coding agents, dashboard refinements, and streamlined Azure deployments. This release focuses on developer productivity and seamless integration with modern AI-assisted development workflows.
+Aspire 13.1 builds on the multi-language foundation established in Aspire 13, delivering significant improvements to the CLI experience, enhanced MCP (Model Context Protocol) support for AI coding agents, dashboard refinements, and streamlined Azure deployments. This release focuses on developer productivity and seamless integration with modern AI-assisted development workflows.
This release introduces:
@@ -488,7 +488,7 @@ The `WithEndpointProxySupport` API is now stable and no longer requires the expe
### Keycloak improvements
-Keycloak containers can now export telemetry to your OTLP collector:
+Keycloak containers can now export telemetry to your OTLP collector:
```csharp title="C# — Keycloak with OTLP export"
var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
index 73e4b709e..c44afb48b 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
@@ -430,7 +430,7 @@ A new **Getting Started walkthrough** guides new users through installing the CL
- **`publish`, `deploy`, and `do` flows** can now be debugged directly from the extension.
- **Apphost exit messages** now appear in the debug console for easier troubleshooting.
-### `aspire.config.json` and MCP support
+### `aspire.config.json` and MCP support
The extension now reads `aspire.config.json` for apphost discovery instead of relying solely on `.csproj` file detection, making TypeScript apphosts work seamlessly. It can also **auto-register the Aspire MCP server** for AI agent workflows. The CLI is automatically detected at default install paths even when it's not on PATH.
@@ -517,7 +517,7 @@ Export a resource's environment variables directly to a `.env` file format from
The dashboard now exposes an HTTP API for querying telemetry data programmatically. These APIs power the `aspire agent mcp` and `aspire otel` Aspire CLI commands.
-The API is served under `/api/telemetry` and returns data in OTLP JSON format. Available endpoints:
+The API is served under `/api/telemetry` and returns data in OTLP JSON format. Available endpoints:
- `GET /api/telemetry/resources` — List resources that have telemetry data
- `GET /api/telemetry/spans` — Query spans with optional filters
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13.mdx b/src/frontend/src/content/docs/whats-new/aspire-13.mdx
index d217a1f74..24d8cd25c 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13.mdx
@@ -993,7 +993,7 @@ This enables a complete mobile + cloud development experience where you can run
## 📊 Dashboard enhancements
-### Aspire MCP server
+### Aspire MCP server
[The Dashboard now includes an MCP server](/dashboard/mcp-server/) that integrates Aspire into your AI development ecosystem. The MCP server enables AI assistants to query resources, access telemetry data, and execute commands directly from your development environment.
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
index ab0bc49ed..6519fc29a 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
@@ -255,7 +255,7 @@ As of 9.3, filter state is **persisted in local storage**, so your selections st
In 9.3, the dashboard can now **visualize outgoing calls to resources that don't emit their own telemetry**—such as databases, caches, and other infrastructure components that lack built-in tracing.
-Previously, these dependencies were invisible in the **Traces** view unless they were emitting OTLP traces. Now, if your app makes an HTTP, SQL, or Redis call to a **modeled Aspire resource** that doesn't emit spans itself, Aspire still shows it as a **referenced peer** in the trace timeline.
+Previously, these dependencies were invisible in the **Traces** view unless they were emitting OTLP traces. Now, if your app makes an HTTP, SQL, or Redis call to a **modeled Aspire resource** that doesn't emit spans itself, Aspire still shows it as a **referenced peer** in the trace timeline.
This helps you:
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
index 8b63f6475..c71c51d41 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
@@ -197,7 +197,7 @@ Aspire 9.5 introduces the GenAI visualizer, which collates, summarizes, and visu
- 🚀 JSON/XML payloads highlighted and indented.
- 🖼️ Preview Markdown and multimodal content (for example, images).
-If GenAI-specific telemetry is found in an OpenTelemetry (OTEL) span, a sparkle (✨) icon appears next to its name in the Traces view. Clicking the icon launches the visualizer dialog.
+If GenAI-specific telemetry is found in an OpenTelemetry (OTEL) span, a sparkle (✨) icon appears next to its name in the Traces view. Clicking the icon launches the visualizer dialog.
The [GenAI telemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) are evolving rapidly. The visualizer supports multiple versions of the telemetry, and we update it as the conventions move toward a stable release.
@@ -654,7 +654,7 @@ builder.Build().Run();
### Other improvements
- New reference properties have been added to Azure PostgreSQL and Redis resources for custom connection string composition and individual component access.
-- OpenTelemetry Protocols (OTLP) support now has protocol selection capabilities, allowing you to choose between gRPC and HTTP protobuf transports for telemetry data.
+- OpenTelemetry Protocol (OTLP) support now has protocol selection capabilities, allowing you to choose between gRPC and HTTP protobuf transports for telemetry data.
## 🧩 App model enhancements
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9.mdx b/src/frontend/src/content/docs/whats-new/aspire-9.mdx
index 21a25d4ca..2deff50ea 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9.mdx
@@ -100,7 +100,7 @@ When a resource has multiple replicas, you can now filter telemetry to view data
### Browser telemetry support
-The dashboard supports OpenTelemetry Protocol (OTLP) over HTTP and cross-origin resource sharing (CORS). These features unlock the ability to send OpenTelemetry from browser apps to the Aspire dashboard.
+The dashboard supports OpenTelemetry Protocol (OTLP) over HTTP and cross-origin resource sharing (CORS). These features unlock the ability to send OpenTelemetry from browser apps to the Aspire dashboard.
For example, a browser-based single page app (SPA) can configure the [JavaScript OpenTelemetry SDK](https://opentelemetry.io/docs/languages/js/getting-started/browser/) to send structured logs, traces, and metrics created in the browser to the dashboard. Browser telemetry is displayed alongside server telemetry.