Fix invalid xref cross-references in documentation

Co-authored-by: eiriktsarpalis <[email protected]>

Author: Copilot

docs/concepts/elicitation/elicitation.md

@@ -15,7 +15,7 @@ Servers request structured data from users with the [ElicitAsync] extension meth
 The C# SDK registers an instance of [IMcpServer] with the dependency injection container,
 so tools can simply add a parameter of type [IMcpServer] to their method signature to access it.
 
-[ElicitAsync]: xref:ModelContextProtocol.Server.McpServerExtensions.ElicitAsync*
+[ElicitAsync]: xref:ModelContextProtocol.Server.McpServer.ElicitAsync*
 [IMcpServer]: xref:ModelContextProtocol.Server.McpServer
 
 The MCP Server must specify the schema of each input value it is requesting from the user.
@@ -33,7 +33,7 @@ The following example demonstrates how a server could request a boolean response
 
 Elicitation is an optional feature so clients declare their support for it in their capabilities as part of the `initialize` request. In the MCP C# SDK, this is done by configuring an [ElicitationHandler] in the [McpClientOptions]:
 
-[ElicitationHandler]: xref:ModelContextProtocol.Protocol.ElicitationCapability.ElicitationHandler
+[ElicitationHandler]: xref:ModelContextProtocol.Client.McpClientHandlers.ElicitationHandler
 [McpClientOptions]: xref:ModelContextProtocol.Client.McpClientOptions
 
 [!code-csharp[](samples/client/Program.cs?name=snippet_McpInitialize)]

docs/concepts/logging/logging.md

@@ -65,7 +65,7 @@ and from that can create an [ILogger] instance for logging messages that should
 [!code-csharp[](samples/server/Tools/LoggingTools.cs?name=snippet_LoggingConfiguration)]
 
 [ILoggerProvider]: https://learn.microsoft.com/dotnet/api/microsoft.extensions.logging.iloggerprovider
-[AsClientLoggerProvider]: xref:ModelContextProtocol.Server.McpServerExtensions.AsClientLoggerProvider*
+[AsClientLoggerProvider]: xref:ModelContextProtocol.Server.McpServer.AsClientLoggerProvider*
 [ILogger]: https://learn.microsoft.com/dotnet/api/microsoft.extensions.logging.ilogger
 
 ### Client support for logging
@@ -89,7 +89,7 @@ sets a logging level to ensure it receives the desired log messages and only tho
 The `loggingLevel` set by the client is an MCP logging level.
 See the [Logging Levels](#logging-levels) section above for the mapping between MCP and .NET logging levels.
 
-[SetLoggingLevel]: xref:ModelContextProtocol.Client.McpClientExtensions.SetLoggingLevel*
+[SetLoggingLevel]: xref:ModelContextProtocol.Client.McpClient.SetLoggingLevel*
 
 [!code-csharp[](samples/client/Program.cs?name=snippet_LoggingLevel)]
 

docs/concepts/progress/progress.md

@@ -63,7 +63,7 @@ The MCP C# SDK will automatically handle progress notifications and report them
 This notification handler will only receive progress updates for the specific request that was made,
 rather than all progress notifications from the server.
 
-[Progress`<T>`]: xref:System.Progress`1
+[Progress`<T>`]: https://learn.microsoft.com/dotnet/api/system.progress-1
 [ProgressNotificationValue]: xref:ModelContextProtocol.ProgressNotificationValue
 
 [!code-csharp[](samples/client/Program.cs?name=snippet_ProgressHandler)]