shorten links

Author: timdeschryver

aspnetcore/performance/caching/hybrid.md

@@ -142,8 +142,8 @@ The `GetOrCreateAsync` method can also take a `HybridCacheEntryOptions` object t
 
 For more information about the options, see the source code:
 
-* [HybridCacheOptions](xref:Microsoft.Extensions.Caching.Hybrid.HybridCacheOptions) class.
-* [HybridCacheEntryOptions](xref:Microsoft.Extensions.Caching.Hybrid.HybridCacheEntryOptions) class.
+* <xref:Microsoft.Extensions.Caching.Hybrid.HybridCacheOptions> class.
+* <xref:Microsoft.Extensions.Caching.Hybrid.HybridCacheEntryOptions> class.
 
 ## Limits
 
@@ -217,7 +217,7 @@ In such cases, inform `HybridCache` that it's safe to reuse instances by:
 
 ### Avoid `byte[]` allocations
 
-`HybridCache` also provides optional APIs for `IDistributedCache` implementations, to avoid `byte[]` allocations. This feature is implemented by the preview versions of the `Microsoft.Extensions.Caching.StackExchangeRedis` and `Microsoft.Extensions.Caching.SqlServer` packages. For more information, see [IBufferDistributedCache](xref:Microsoft.Extensions.Caching.Distributed.IBufferDistributedCache)
+`HybridCache` also provides optional APIs for `IDistributedCache` implementations, to avoid `byte[]` allocations. This feature is implemented by the preview versions of the `Microsoft.Extensions.Caching.StackExchangeRedis` and `Microsoft.Extensions.Caching.SqlServer` packages. For more information, see <xref:Microsoft.Extensions.Caching.Distributed.IBufferDistributedCache>.
 Here are the .NET CLI commands to install the packages:
 
 ```dotnetcli

aspnetcore/release-notes/aspnetcore-8.0.md

@@ -957,7 +957,7 @@ Metrics have been added for ASP.NET Core hosting, Kestrel, and SignalR. For more
 
 ### IExceptionHandler
 
-[IExceptionHandler](xref:Microsoft.AspNetCore.Diagnostics.IExceptionHandler) is a new interface that gives the developer a callback for handling known exceptions in a central location.
+<xref:Microsoft.AspNetCore.Diagnostics.IExceptionHandler> is a new interface that gives the developer a callback for handling known exceptions in a central location.
 
 `IExceptionHandler` implementations are registered by calling [`IServiceCollection.AddExceptionHandler<T>`](xref:Microsoft.Extensions.DependencyInjection.ExceptionHandlerServiceCollectionExtensions.AddExceptionHandler%2A). Multiple implementations can be added, and they're called in the order registered. If an exception handler handles a request, it can return `true` to stop processing. If an exception isn't handled by any exception handler, then control falls back to the default behavior and options from the middleware.
 

aspnetcore/release-notes/aspnetcore-9/includes/openAPI_completion.md

@@ -4,7 +4,7 @@ ASP.NET Core's OpenAPI support is now more accessible and user-friendly. The Ope
 
 Recognizing this gap, we have introduced a new completion provider and code fixer. These tools are designed to facilitate the discovery and use of OpenAPI APIs, making it easier for developers to integrate OpenAPI into their projects. The completion provider offers real-time code suggestions, while the code fixer assists in correcting common mistakes and improving API usage. This enhancement is part of our ongoing commitment to improve the developer experience and streamline API-related workflows.
 
-When a user types a statement where an OpenAPI-related API is available, the completion provider displays a recommendation for the API. For example, in the following screenshots, completions for [AddOpenApi](xref:Microsoft.Extensions.DependencyInjection.OpenApiServiceCollectionExtensions.AddOpenApi) and [MapOpenApi](xref:Microsoft.AspNetCore.Builder.OpenApiEndpointRouteBuilderExtensions.MapOpenApi) are provided when a user is entering an invocation statement on a supported type, such as [IEndpointConventionBuilder](/dotnet/api/microsoft.aspnetcore.builder.iendpointconventionbuilder):
+When a user types a statement where an OpenAPI-related API is available, the completion provider displays a recommendation for the API. For example, in the following screenshots, completions for <xref:Microsoft.Extensions.DependencyInjection.OpenApiServiceCollectionExtensions.AddOpenApi> and <xref:Microsoft.AspNetCore.Builder.OpenApiEndpointRouteBuilderExtensions.MapOpenApi> are provided when a user is entering an invocation statement on a supported type, such as [IEndpointConventionBuilder](/dotnet/api/microsoft.aspnetcore.builder.iendpointconventionbuilder):
 
 <img width="508" alt="OpenAPI completions" src="https://github.com/dotnet/AspNetCore.Docs/assets/1857993/1ed9fcb9-7ab7-4239-b7c8-d323724e7222">
 
@@ -78,7 +78,7 @@ class Todo
 
 ### Support for schema transformers on OpenAPI documents
 
-Built-in OpenAPI support now ships with support for schema transformers that can be used to modify schemas generated by [System.Text.Json](/dotnet/api/system.text.json) and the OpenAPI implementation. Like document and operation transformers, schema transformers can be registered on the [OpenApiOptions](xref:Microsoft.AspNetCore.OpenApi.OpenApiOptions) object. For example, the following code sample demonstrates using a schema transformer to add an example to a type's schema.
+Built-in OpenAPI support now ships with support for schema transformers that can be used to modify schemas generated by [System.Text.Json](/dotnet/api/system.text.json) and the OpenAPI implementation. Like document and operation transformers, schema transformers can be registered on the <xref:Microsoft.AspNetCore.OpenApi.OpenApiOptions> object. For example, the following code sample demonstrates using a schema transformer to add an example to a type's schema.
 
 ```csharp
 using System.ComponentModel;

aspnetcore/security/anti-request-forgery.md

@@ -277,11 +277,11 @@ Call [AddAntiforgery](/dotnet/api/microsoft.extensions.dependencyinjection.antif
 The antiforgery middleware:
 
 * Does ***not*** short-circuit the execution of the rest of the request pipeline.
-* Sets the [IAntiforgeryValidationFeature](xref:Microsoft.AspNetCore.Antiforgery.IAntiforgeryValidationFeature) in the [HttpContext.Features](xref:Microsoft.AspNetCore.Http.HttpContext.Features) of the current request.
+* Sets the <xref:Microsoft.AspNetCore.Antiforgery.IAntiforgeryValidationFeature> in the [HttpContext.Features](xref:Microsoft.AspNetCore.Http.HttpContext.Features) of the current request.
 
 The antiforgery token is only validated if:
 
-* The endpoint contains metadata implementing [IAntiforgeryMetadata](xref:Microsoft.AspNetCore.Antiforgery.IAntiforgeryMetadata) where `RequiresValidation=true`.
+* The endpoint contains metadata implementing <xref:Microsoft.AspNetCore.Antiforgery.IAntiforgeryMetadata> where `RequiresValidation=true`.
 * The HTTP method associated with the endpoint is a relevant [HTTP method](https://developer.mozilla.org/docs/Web/HTTP/Methods). The relevant methods are all [HTTP methods](https://developer.mozilla.org/docs/Web/HTTP/Methods) except for TRACE, OPTIONS, HEAD, and GET.
 * The request is associated with a valid endpoint.
 

aspnetcore/security/authentication/claims.md

@@ -43,7 +43,7 @@ Another way to get the user claims is to use the OpenID Connect User Info API. T
 
 :::code language="csharp" source="~/release-notes/aspnetcore-9/samples/PAR/Program.cs" id="snippet_1" highlight="8-99":::
 
-To ensure that authentication only succeeds if PAR is used, use [PushedAuthorizationBehavior.Require](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.PushedAuthorizationBehavior) instead. This change also introduces a new [OnPushAuthorization](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectEvents.OnPushAuthorization) event to [OpenIdConnectEvents](/dotnet/api/microsoft.aspnetcore.authentication.openidconnect.openidconnectevents) which can be used to customize the pushed authorization request or handle it manually. See the [API proposal](https://github.com/dotnet/aspnetcore/issues/51686) for more details.
+To ensure that authentication only succeeds if PAR is used, use [PushedAuthorizationBehavior.Require](xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.PushedAuthorizationBehavior) instead. This change also introduces a new <xref:Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectEvents.OnPushAuthorization> event to [OpenIdConnectEvents](/dotnet/api/microsoft.aspnetcore.authentication.openidconnect.openidconnectevents) which can be used to customize the pushed authorization request or handle it manually. See the [API proposal](https://github.com/dotnet/aspnetcore/issues/51686) for more details.
 
 :::moniker-end
 

aspnetcore/security/authentication/mfa.md

@@ -507,7 +507,7 @@ Alternatively, logging in using OTP with Identity:
 
 ### OIDC and OAuth Parameter Customization
 
-The OAuth and OIDC authentication handlers  [`AdditionalAuthorizationParameters`](xref:Microsoft.AspNetCore.Authentication.OAuth.OAuthOptions.AdditionalAuthorizationParameters) option allows customization of authorization message parameters that are usually included as part of the redirect query string:
+The OAuth and OIDC authentication handlers <xref:Microsoft.AspNetCore.Authentication.OAuth.OAuthOptions.AdditionalAuthorizationParameters> option allows customization of authorization message parameters that are usually included as part of the redirect query string:
 
 :::code language="csharp" source="~/security/authentication/mfa/samples9/WebAddOpenIdConnect/Program.cs" id="snippet_1" :::