Fix typos

Author: localden

docs/community/feature-lifecycle.mdx

@@ -16,8 +16,8 @@ This policy was adopted via
 
 This policy governs **features** of the MCP core specification: protocol
 messages, capabilities, transports, schema types, and normative behavioral
-requirements. Tthe revision lifecycle of the specification document itself
-(Draft, Current, Final), is defined in the [versioning guide](/docs/learn/versioning).
+requirements. The revision lifecycle of the specification document itself
+(Draft, Current, Final) is defined in the [versioning guide](/docs/learn/versioning).
 
 ## Feature States
 
@@ -43,14 +43,14 @@ releases. That timeline is governed by the SDK's own revision-support policy.
 
 ## Deprecating a Feature
 
-A feature may be proposed for deprecation due to
+A feature may be proposed for deprecation when:
 
 - it has been superseded by another feature that covers the same use cases,
 - it presents a security, privacy, or interoperability risk that cannot be
   mitigated in place,
 - ecosystem telemetry or SDK maintainer consensus indicates negligible adoption
   relative to its maintenance cost,
-- or any other reasons the Core Maintainers seem to deem appropriate.
+- or any other reasons the Core Maintainers deem appropriate.
 
 Deprecation is a specification change and therefore requires a SEP per the
 [SEP guidelines](/community/sep-guidelines). The deprecation SEP must:
@@ -92,7 +92,7 @@ The minimum deprecation window is counted from that release.
 ## The Deprecated Registry
 
 [`docs/specification/draft/deprecated.mdx`](/specification/draft/deprecated) is
-a single page listing every feature Deprecated or Removed state. It is
+a single page listing every feature in a Deprecated or Removed state. It is
 the canonical answer to "what is on its way out, and by when," so that an
 implementer does not have to reconstruct that picture from deprecation entries
 spread across revision changelogs.
@@ -116,7 +116,7 @@ released as Current, Tier 1 SDKs:
 
 1. Once a feature is set for removal, the removal is executed at the discretion
    of the Core Maintainers after the minimum deprecation window has elapsed.
-2. The removal needs to be documented in the `changelog.mdx` and [registry](#the-deprecated-regsitry)
+2. The removal needs to be documented in the `changelog.mdx` and [registry](#the-deprecated-registry).
 3. A SEP is required for any change to the original deprecation or removal SEP, for
    example extending or shortening the timeline
    ([Expedited removal](#expedited-removal)) or restoring the feature to Active

docs/docs/learn/versioning.mdx

@@ -35,8 +35,8 @@ the feature remains part of the specification, but is scheduled for removal.
 Deprecated features document a migration path (or state that none is required)
 and remain in the specification for at least twelve months, or at least
 ninety days under the policy's
-[expedited-removal exception](/community/feature-lifecycle#expedited-removal)
-, before they become eligible for removal, after which they may be **Removed**
+[expedited-removal exception](/community/feature-lifecycle#expedited-removal),
+before they become eligible for removal, after which they may be **Removed**
 in a future revision.
 
 Features that are currently Deprecated are listed in the

docs/specification/draft/basic/transports.mdx

@@ -145,8 +145,8 @@ for the [HTTP+SSE transport][http-sse] from protocol version 2024-11-05.
 Revision 2026-07-28 changed the behavior of Streamable HTTP. Clients must
 ensure they handle backwards compatibility correctly. Changes included:
 
-- Removal of the GET stream endpoint
-- Removal of protocol-level session.
+- Removal of the GET stream endpoint.
+- Removal of protocol-level sessions.
 
 See the [changelog](/specification/draft/changelog) and
 [Backward Compatibility](#backward-compatibility-1) below.
@@ -698,7 +698,7 @@ See [Lifecycle: Backward Compatibility][lifecycle-compat] for details.
 
 #### Earlier Streamable HTTP Revisions
 
-Protocol versions `2025-03-26` through [`2025-11-25`](./docs/specification/2025-11-25/basic/transports.mdx)
+Protocol versions `2025-03-26` through [`2025-11-25`](/specification/2025-11-25/basic/transports)
 also used the Streamable HTTP transport, but in a different shape: servers could assign a session via
 the `Mcp-Session-Id` header (terminated with HTTP DELETE), clients could open
 a standalone SSE stream with HTTP GET to receive server-initiated messages,
@@ -727,7 +727,7 @@ in addition to the version-negotiation fallback described above.
   **Deprecated**: The [HTTP+SSE transport][http-sse] from protocol version
   2024-11-05 has been deprecated since protocol version `2025-03-26` and is
   classified as Deprecated under the [feature lifecycle
-  policy](/community/feature-lifecycle#transition)
+  policy](/community/feature-lifecycle#deprecating-a-feature)
   ([SEP-2596](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2596)).
   New implementations **SHOULD NOT** adopt it; existing implementations
   **SHOULD** migrate to [Streamable HTTP](#streamable-http). It is eligible for

docs/specification/draft/client/sampling.mdx

@@ -93,7 +93,7 @@ Clients that support sampling **MUST** declare the `sampling` capability in
 <Note>
   The `includeContext` parameter values `"thisServer"` and `"allServers"` are
   deprecated under the [feature lifecycle
-  policy](/community/feature-lifecycle#transition)
+  policy](/community/feature-lifecycle#deprecating-a-feature)
   ([SEP-2596](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2596));
   they will be removed no later than the Sampling feature itself. Servers
   **SHOULD** avoid using these values (e.g. can just omit `includeContext` since

docs/specification/draft/deprecated.mdx

@@ -31,7 +31,7 @@ deprecation notices and changelog entries, which are the normative records.
 
 The HTTP+SSE transport and the `includeContext` values were already described
 as deprecated before the lifecycle policy existed; SEP-2596 reclassifies them
-as Deprecated under its [transition provisions](/community/feature-lifecycle#transition).
+as Deprecated under its [transition provisions](/community/feature-lifecycle).
 
 ## Removed