Minor fixes

Author: JakeSCahill

modules/ai-agents/pages/mcp/remote/admin-guide.adoc

@@ -7,44 +7,25 @@ This guide provides an overview of administrative tasks for Remote MCP servers.
 
 You must have an existing MCP server. If you do not have one, see xref:ai-agents:mcp/remote/quickstart.adoc[].
 
-== Administrative tasks
-
-=== Server lifecycle management
+== Server lifecycle management
 
 Manage the basic lifecycle of your MCP servers, including editing configurations, pausing to save costs, and permanent deletion.
 
-See xref:ai-agents:mcp/remote/manage-servers.adoc[] to learn how to:
-
-* Edit an MCP server's configuration, metadata, or tools
-* Stop (pause) an MCP server to release compute resources while preserving configuration
-* Start a stopped MCP server to restore functionality
-* Delete an MCP server permanently
+See xref:ai-agents:mcp/remote/manage-servers.adoc[].
 
-=== Resource scaling
+== Resource scaling
 
 Adjust your MCP server's compute resources to match workload demands and optimize costs. Resource allocation directly affects your billing charges.
 
-See xref:ai-agents:mcp/remote/scale-resources.adoc[] to learn how to:
-
-* Scale resources up during peak usage periods
-* Scale resources down during quieter times to optimize costs
-* Choose the appropriate resource size for your workload (XSmall through XLarge)
-* Use the Cloud UI or Data Plane API to adjust resource allocation
-
-=== Monitoring and observability
+See xref:ai-agents:mcp/remote/scale-resources.adoc[].
 
-Monitor your MCP server's activity using OpenTelemetry traces automatically emitted to the `redpanda.otel_traces` topic. Track tool invocations, measure performance, debug failures, and integrate with observability platforms.
+== Monitoring and observability
 
-See xref:ai-agents:mcp/remote/monitor-activity.adoc[] to learn how to:
+Monitor your MCP server's activity using OpenTelemetry traces. Track tool invocations, measure performance, debug failures, and integrate with observability platforms.
 
-* Consume and analyze trace data from the `redpanda.otel_traces` topic
-* Track which tools are being called and how often
-* Measure tool execution times and identify performance issues
-* Debug failures using error traces and status codes
-* Integrate with Grafana Tempo, Datadog, or custom dashboards
-* Follow best practices for retention, sampling, and alerting
+See xref:ai-agents:mcp/remote/monitor-activity.adoc[].
 
-== Working with the Data Plane API
+== Data Plane API
 
 All administrative tasks can be performed through both the Redpanda Cloud Console UI and the Data Plane API. The Data Plane API is useful for:
 
@@ -58,10 +39,10 @@ To use the Data Plane API:
 . link:/api/doc/cloud-dataplane/topic/topic-quickstart[Authenticate and get the base URL] for the Data Plane API.
 . Use the appropriate endpoint for your task:
 +
-* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_updatemcpserver[`PATCH /v1/redpanda-connect/mcp-servers/\{mcp_server_id}`] - Update configuration
-* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_stopmcpserver[`POST /v1/redpanda-connect/mcp-servers/\{mcp_server_id}:stop`] - Stop server
-* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_startmcpserver[`POST /v1/redpanda-connect/mcp-servers/\{mcp_server_id}:start`] - Start server
-* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_deletemcpserver[`DELETE /v1/redpanda-connect/mcp-servers/\{mcp_server_id}`] - Delete server
+* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_updatemcpserver[`PATCH /v1/redpanda-connect/mcp-servers/\{mcp_server_id}`]: Update configuration
+* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_stopmcpserver[`POST /v1/redpanda-connect/mcp-servers/\{mcp_server_id}:stop`]: Stop server
+* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_startmcpserver[`POST /v1/redpanda-connect/mcp-servers/\{mcp_server_id}:start`]: Start server
+* link:/api/doc/cloud-dataplane/operation/operation-mcpserverservice_deletemcpserver[`DELETE /v1/redpanda-connect/mcp-servers/\{mcp_server_id}`]: Delete server
 
 [NOTE]
 ====

modules/ai-agents/pages/mcp/remote/monitor-activity.adoc

@@ -25,7 +25,7 @@ Each span represents a unit of work performed by your MCP server, such as:
 
 === Topic configuration and lifecycle
 
-The `redpanda.otel_traces` topic is managed automatically by Redpanda and follows a predefined retention policy. Configuration changes to this system-managed topic are not supported and will be reconciled back to the default settings.
+The `redpanda.otel_traces` topic is managed automatically by Redpanda and follows a predefined retention policy. Configuration changes to this topic are not supported. If you modify settings, Redpanda reverts them to the default values.
 
 The topic persists in your cluster even after all MCP servers are deleted, allowing you to retain historical trace data for analysis.
 
@@ -136,9 +136,9 @@ All MCP servers in a cluster write traces to the same `redpanda.otel_traces` top
 
 * When `instrumentationScope.name` is `rpcn-mcp`, the span represents an MCP tool invocation.
 * The `name` field contains the MCP tool name (for example, `weather`, `http_processor`, `generate_input`).
-* Child spans reference their parent via `parentSpanId` and share the same `traceId`
+* Child spans reference their parent using `parentSpanId` and share the same `traceId`
 
-For example, a span with `instrumentationScope.name: "rpcn-mcp"` and `name: "weather"` indicates the `weather` tool was invoked. Child spans created by Redpanda Connect components show `instrumentationScope.name: "benthos"` and represent internal processing steps.
+For example, a span with `instrumentationScope.name: "rpcn-mcp"` and `name: "weather"` indicates the `weather` tool was invoked. Child spans created by Redpanda Connect components show `instrumentationScope.name: "redpanda-connect"` and represent internal processing steps.
 
 === Real trace examples
 
@@ -185,7 +185,7 @@ The parent span (`http_processor`) has child spans showing the processing pipeli
     "attributes": [],
     "endTimeUnixNano": "1765198424659619511",
     "flags": 1,
-    "instrumentationScope": {"name": "benthos"},
+    "instrumentationScope": {"name": "redpanda-connect"},
     "kind": 1,
     "name": "http",
     "parentSpanId": "43ad6bc31a826afd",
@@ -223,7 +223,7 @@ This trace shows an HTTP request that encountered an error during execution:
         }
     ],
     "flags": 1,
-    "instrumentationScope": {"name": "benthos"},
+    "instrumentationScope": {"name": "redpanda-connect"},
     "kind": 1,
     "name": "http_request",
     "parentSpanId": "43ad6bc31a826afd",

modules/ai-agents/pages/mcp/remote/overview.adoc

@@ -1,8 +1,7 @@
 = About Remote MCP Servers for Redpanda Cloud
 :description: Discover how AI assistants can interact with your streaming data and how to connect them to Redpanda Cloud.
 
-
-Remote MCP (Model Context Protocol) servers are managed, hosted MCP servers that you can write and run inside your Redpanda Cloud cluster. They let you expose your data, analytics, and automation pipelines as AI-consumable tools with no custom API code. MCP servers bridge your business logic to AI agents using the open MCP standard, so you can:
+Remote MCP (Model Context Protocol) servers are hosted MCP servers that run inside your Redpanda Cloud cluster. They let you expose your data, analytics, and automation pipelines as AI-consumable tools with no custom API code. MCP servers bridge your business logic to AI agents using the open MCP standard, so you can:
 
 * Make your data and workflows accessible to AI assistants and LLMs, safely and on your terms.
 * Accelerate automation and insight by letting AI trigger real business actions.