Apply suggestions from reviews

Co-authored-by: Eirik Tsarpalis <eirik.tsarpalis@gmail.com>
Co-authored-by: Mike Kistler <mikekistler@microsoft.com>

Author: 3 people

docs/toc.yml

@@ -3,7 +3,7 @@ items:
   href: concepts/index.md
 - name: API Reference
   href: api/ModelContextProtocol.yml
-- name: C# SDK Versioning
+- name: Versioning
   href: versioning.md
 - name: GitHub
   href: https://github.com/ModelContextProtocol/csharp-sdk

docs/versioning.md

@@ -4,7 +4,7 @@ author: jeffhandley
 description: ModelContextProtocol C# SDK approach to versioning, breaking changes, and support
 uid: versioning
 ---
-The ModelContextProtocol specification continues to evolve rapidly, and it's important for the C# SDK to remain current with specification additions and updates. To enable this, all NuGet packages that compose the SDK will follow [Semantic Versioning](https://semver.org) with MAJOR.MINOR.PATCH version numbers, and optional pre-release versions.
+The ModelContextProtocol specification continues to evolve rapidly, and it's important for the C# SDK to remain current with specification additions and updates. To enable this, all NuGet packages that compose the SDK will follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) with MAJOR.MINOR.PATCH version numbers, and optional pre-release versions.
 
 Given a version number MAJOR.MINOR.PATCH, the package versions will increment the:
 
@@ -31,11 +31,11 @@ Beginning with the 1.0.0 release, the following support policy will be applied f
 
 MAJOR or MINOR version updates might introduce or alter APIs annotated as [`[Experimental]`](https://learn.microsoft.com/dotnet/api/system.diagnostics.codeanalysis.experimentalattribute). This attribute indicates that an API is experimental and it may change at any time--including within PATCH or MINOR version updates.
 
-Experimental APIs require suppression of diagnostic codes specific to the MCP SDK APIs.
+Experimental APIs require suppression of diagnostic codes specific to the MCP SDK APIs, using an `MCPEXP` prefix.
 
 ## Breaking changes
 
-Prior to the release of a stable 1.0.0 set of NuGet packages, the SDK remains in preview and breaking changes can be introduced without prior notice. All versions beginning with the stable 1.0.0 release will follow semantic versioning. Bugs will be fixed in PATCH versions; new APIs will be added in MINOR versions, and breaking changes will require increments to the MAJOR version.
+Prior to the release of a stable 1.0.0 set of NuGet packages, the SDK remains in preview and breaking changes can be introduced without prior notice. All versions beginning with the stable 1.0.0 release will follow semantic versioning, and breaking changes will require increments to the MAJOR version.
 
 If feasible, the SDK will support all versions of the MCP spec. However, if breaking changes to the spec make this infeasible, preference will be given to the most recent version of the MCP spec, and this would be considered a breaking change necessitating a new MAJOR version.
 
@@ -58,4 +58,4 @@ If APIs within the SDK become obsolete due to changes in the MCP spec or other e
 2. Within a MAJOR version update, APIs may be marked as `[Obsolete]` to produce _build errors_ indicating the API is no longer functional and always throws exceptions. The build errors will provide guidance specific to the affected APIs.
 3. Within a MAJOR version update, obsolete APIs may be removed. API removals are expected to be rare and avoided wherever possible, and `[Obsolete]` attributes will be applied ahead of the API removal.
 
-Beginning with the 1.0.0 release, all obsoletions will use diagnostic codes specific to the MCP SDK APIs.
+Beginning with the 1.0.0 release, all obsoletions will use diagnostic codes specific to the MCP SDK APIs, using an `MCPOBS` prefix.