typo/grammar pass

Author: betegon

develop-docs/sdk/expected-features/mcp-instrumentation/errors.mdx

@@ -29,13 +29,13 @@ export function captureError(error: Error, errorType?: string): void {
       },
     });
   } catch {
-    // Silently ignore capture errors - never affect MCP operation
+    // Silently ignore capture errors so it never affects MCP operation
   }
 }
 ```
 
-- **Never throws:** All error capture is wrapped in a try/catch and will never throw.
-- **Tags errors:** Errors are tagged with `mcp_error_type` for later filtering.
+- **Never throws an exception:** All error capture is wrapped in a try/catch and will never throw an exception.
+- **Tags errors:** [WIP] will be removed as tags are intended for users.
 
 ## Handler Wrapping for Error Capture
 

develop-docs/sdk/expected-features/mcp-instrumentation/index.mdx

@@ -2,7 +2,7 @@
 title: MCP Instrumentation
 ---
 
-The MCP Server module instruments Anthropic's Model Context Protocol (MCP) SDKs. At the moment it only supports the [MCP typescript sdk](https://github.com/modelcontextprotocol/typescript-sdk/).
+The MCP Server module instruments Anthropic's Model Context Protocol (MCP) SDKs. At the moment it only supports the [MCP Typescript SDK](https://github.com/modelcontextprotocol/typescript-sdk/).
 
 ## Features
 
@@ -13,7 +13,7 @@ The MCP Server module instruments Anthropic's Model Context Protocol (MCP) SDKs.
 
 Currently, it doesn't support automatic instrumentation due to [this issue](https://github.com/getsentry/sentry-javascript/issues/16052) related to `import-in-the-middle`.
 
-Instrumentation has to be done by wrapping the MCP server instance. This is done by the `wrapMcpServerWithSentry` function. For example:
+Instrumentation must be done by wrapping the MCP server instance. This is done by the `wrapMcpServerWithSentry` function. For example:
 
 ```ts
 import * as Sentry from "@sentry/core";

develop-docs/sdk/expected-features/mcp-instrumentation/tracing.mdx

@@ -2,7 +2,7 @@
 title: Tracing
 ---
 
-The MCP Server module is the instrumentation for the anthropic MCP SDKs. At the moment it only supports the [MCP typescript sdk](https://github.com/modelcontextprotocol/typescript-sdk/).
+The MCP Server module is the instrumentation for the anthropic MCP SDKs. At the moment it only supports the [MCP Typescript SDK](https://github.com/modelcontextprotocol/typescript-sdk/).
 
 ## Spans Conventions
 
@@ -18,12 +18,12 @@ All MCP Server spans share common attributes and follow consistent patterns:
 | :-------------------------- | :----- | :---------------- | :---------------------------------------------------------------------------- | :------------------------------------- |
 | `mcp.method.name`           | string | required          | The name of the request or notification method.                               | `"tools/call"`                         |
 | `mcp.request.id`            | string | optional          | A unique identifier for the request.                                          | `"42"`                                 |
-| `mcp.session.id`            | string | optional          | Identifies the MCP session. can be undefined as MCP servers can be stateless. | `"191c4850af6c49..."`   |
+| `mcp.session.id`            | string | optional          | Identifies the MCP session. Can be undefined as MCP servers can be stateless. | `"191c4850af6c49..."`   |
 | `mcp.transport`             | string | required          | The transport method used for MCP communication. **[2]**                      | `"stdio"`                              |
 | `network.transport`         | string | required          | OSI transport layer protocol. **[3]**                                         | `"pipe"`                               |
 | `network.protocol.version`  | string | optional          | The version of JSON RPC protocol used.                                        | `"2.0"`                                |
 
-**[2]** Well defined values for data attribute `mcp.transport`:
+**[2]** Well-defined values for data attribute `mcp.transport`:
 
 | Value        | Description                              |
 | :-------     | :------------------------------------    |
@@ -34,7 +34,7 @@ All MCP Server spans share common attributes and follow consistent patterns:
 
 *`"unknown"` is a placeholder for custom transports. We could try to infer the name from the transport object.
 
-**[3]** Well defined values for data attribute `network.transport`:
+**[3]** Well-defined values for data attribute `network.transport`:
 
 | Value    | Description                           |
 | :------- | :------------------------------------ |