Fix build suggestions (#46825)

Author: gewarren

.openpublishing.redirection.csharp.json

@@ -22,7 +22,7 @@
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-7.0/pattern-matching.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/patterns.md"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/patterns"
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-7.0/task-types.md",
@@ -110,7 +110,7 @@
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-8.0/nullable-reference-types.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-8.0/nested-stackalloc.md",
@@ -126,11 +126,11 @@
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-8.0/async-streams.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/statements.md#13953-await-foreach"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/statements#13953-await-foreach"
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-9.0/nullable-reference-types-specification.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/redirections/proposals/csharp-10.0/generic-attributes.md",
@@ -1400,27 +1400,27 @@
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-8.0/index.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-8.0/static-local-functions.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/statements.md#1364-local-function-declarations"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/statements#1364-local-function-declarations"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-8.0/nullable-reference-types.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-9.0/nullable-reference-types-specification.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-9.0/nullable-constructor-analysis.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-9.0/nullable-parameter-default-value-analysis.md",
-            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types.md#893-nullable-reference-types"
+            "redirect_url": "/dotnet/csharp/language-reference/language-specification/types#893-nullable-reference-types"
         },
         {
             "source_path_from_root": "/docs/csharp/language-reference/proposals/csharp-9.0/index.md",

docs/architecture/microservices/implement-resilient-applications/index.md

@@ -15,14 +15,12 @@ It's challenging enough to design and deploy a microservices-based application.
 
 The many individual components of your application should also incorporate health monitoring features. By following the guidelines in this chapter, you can create an application that can work smoothly in spite of transient downtime or the normal hiccups that occur in complex and cloud-based deployments.
 
->[!IMPORTANT]
-> eShopOnContainer had been using the [Polly library](https://thepollyproject.azurewebsites.net/) to implement resiliency using [Typed Clients](./use-httpclientfactory-to-implement-resilient-http-requests.md) up until the release 3.0.0.
->
-> Starting with release 3.0.0, the HTTP calls resiliency is implemented using a [Linkerd mesh](https://linkerd.io/), that handles retries in a transparent and configurable fashion, within a Kubernetes cluster, without having to handle those concerns in the code.
+> [!IMPORTANT]
+> eShopOnContainer had been using the [Polly library](https://www.pollydocs.org/) to implement resiliency using [Typed Clients](./use-httpclientfactory-to-implement-resilient-http-requests.md) up until the release 3.0.0. Starting with release 3.0.0, the HTTP calls resiliency is implemented using a [Linkerd mesh](https://linkerd.io/), which handles retries in a transparent and configurable fashion within a Kubernetes cluster, without having to handle those concerns in the code.
 >
 > The Polly library is still used to add resilience to database connections, specially while starting up the services.
 
->[!WARNING]
+> [!WARNING]
 > All code samples and images in this section were valid before using Linkerd and are not updated to reflect the current actual code. So they make sense in the context of this section.
 
 >[!div class="step-by-step"]

docs/architecture/microservices/implement-resilient-applications/partial-failure-strategies.md

@@ -19,7 +19,7 @@ To deal with partial failures, use one of the strategies described here.
 
 **Provide fallbacks**. In this approach, the client process performs fallback logic when a request fails, such as returning cached data or a default value. This is an approach suitable for queries, and is more complex for updates or commands.
 
-**Limit the number of queued requests**. Clients should also impose an upper bound on the number of outstanding requests that a client microservice can send to a particular service. If the limit has been reached, it's probably pointless to make additional requests, and those attempts should fail immediately. In terms of implementation, the Polly [Bulkhead Isolation](https://github.com/App-vNext/Polly/wiki/Bulkhead) policy can be used to fulfill this requirement. This approach is essentially a parallelization throttle with <xref:System.Threading.SemaphoreSlim> as the implementation. It also permits a "queue" outside the bulkhead. You can proactively shed excess load even before execution (for example, because capacity is deemed full). This makes its response to certain failure scenarios faster than a circuit breaker would be, since the circuit breaker waits for the failures. The BulkheadPolicy object in [Polly](https://thepollyproject.azurewebsites.net/) exposes how full the bulkhead and queue are, and offers events on overflow so can also be used to drive automated horizontal scaling.
+**Limit the number of queued requests**. Clients should also impose an upper bound on the number of outstanding requests that a client microservice can send to a particular service. If the limit has been reached, it's probably pointless to make additional requests, and those attempts should fail immediately. In terms of implementation, the Polly [Bulkhead Isolation](https://github.com/App-vNext/Polly/wiki/Bulkhead) policy can be used to fulfill this requirement. This approach is essentially a parallelization throttle with <xref:System.Threading.SemaphoreSlim> as the implementation. It also permits a "queue" outside the bulkhead. You can proactively shed excess load even before execution (for example, because capacity is deemed full). This makes its response to certain failure scenarios faster than a circuit breaker would be, since the circuit breaker waits for the failures. The BulkheadPolicy object in [Polly](https://www.pollydocs.org/) exposes how full the bulkhead and queue are, and offers events on overflow so can also be used to drive automated horizontal scaling.
 
 ## Additional resources
 

docs/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests.md

@@ -25,7 +25,7 @@ To address the issues mentioned above and to make `HttpClient` instances managea
 
 The alternative is to use `SocketsHttpHandler` with configured `PooledConnectionLifetime`. This approach is applied to long-lived, `static` or singleton `HttpClient` instances. To learn more about different strategies, see [HttpClient guidelines for .NET](../../../fundamentals/networking/http/httpclient-guidelines.md).
 
-[Polly](https://thepollyproject.azurewebsites.net/) is a transient-fault-handling library that helps developers add resiliency to their applications, by using some pre-defined policies in a fluent and thread-safe manner.
+[Polly](https://www.pollydocs.org/) is a transient-fault-handling library that helps developers add resiliency to their applications, by using some pre-defined policies in a fluent and thread-safe manner.
 
 ## Benefits of using IHttpClientFactory
 
@@ -204,7 +204,7 @@ Up to this point, the above code snippet only shows the example of performing re
   <https://github.com/dotnet/runtime/tree/release/7.0/src/libraries/Microsoft.Extensions.Http/>
 
 - **Polly (.NET resilience and transient-fault-handling library)**
-  <https://thepollyproject.azurewebsites.net/>
+  <https://www.pollydocs.org/>
 
 >[!div class="step-by-step"]
 >[Previous](implement-resilient-entity-framework-core-sql-connections.md)

docs/azure/sdk/aspnetcore-guidance.md

@@ -20,7 +20,7 @@ The Azure SDK for .NET enables ASP.NET Core apps to integrate with many differen
 ASP.NET Core apps that connect to Azure services generally depend on the following Azure SDK client libraries:
 
 - [Microsoft.Extensions.Azure](https://www.nuget.org/packages/Microsoft.Extensions.Azure) provides helper methods to register clients with the dependency injection service collection and handles various concerns for you, such as setting up logging, handling DI service lifetimes, and authentication credential management.
-- [Azure.Identity](https://www.nuget.org/packages/Azure.Identity) enables Microsoft Entra ID authentication support across the Azure SDK. It provides a set of [TokenCredential](/dotnet/api/azure.core.tokencredential?view=azure-dotnet) implementations to construct Azure SDK clients that support Microsoft Entra authentication.
+- [Azure.Identity](https://www.nuget.org/packages/Azure.Identity) enables Microsoft Entra ID authentication support across the Azure SDK. It provides a set of <xref:Azure.Core.TokenCredential> implementations to construct Azure SDK clients that support Microsoft Entra authentication.
 - `Azure.<service-namespace>` libraries, such as [Azure.Storage.Blobs](https://www.nuget.org/packages/Azure.Storage.Blobs) and [Azure.Messaging.ServiceBus](https://www.nuget.org/packages/Azure.Messaging.ServiceBus), provide service clients and other types to help you connect to and consume specific Azure services. For a complete inventory of these libraries, see [Libraries using Azure.Core](packages.md#libraries-using-azurecore).
 
 In the sections ahead, you'll explore how to implement an ASP.NET Core application that uses these libraries.

docs/azure/sdk/authentication/additional-methods.md

@@ -39,7 +39,7 @@ For more exact control, such as setting redirect URIs, you can supply specific a
 
 ## Interactive brokered authentication
 
-This method interactively authenticates an application through [`InteractiveBrowserCredential`](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet) by collecting user credentials using the system authentication broker. A system authentication broker is an app running on a user's machine that manages the authentication handshakes and token maintenance for all connected accounts. Currently, only the Windows authentication broker, Web Account Manager (WAM), is supported. Users on macOS and Linux will be authenticated through the non-brokered interactive browser flow.
+This method interactively authenticates an application through <xref:Azure.Identity.InteractiveBrowserCredential> by collecting user credentials using the system authentication broker. A system authentication broker is an app running on a user's machine that manages the authentication handshakes and token maintenance for all connected accounts. Currently, only the Windows authentication broker, Web Account Manager (WAM), is supported. Users on macOS and Linux will be authenticated through the non-brokered interactive browser flow.
 
 WAM enables identity providers such as Microsoft Entra ID to natively plug into the OS and provide the service to other apps to provide a more secure login process. WAM offers the following benefits:
 
@@ -80,7 +80,7 @@ Perform the following steps to enable the application to authenticate through th
 
 ### Example using InteractiveBrowserCredential
 
-The following example demonstrates using an [`InteractiveBrowserCredential`](/dotnet/api/azure.identity.interactivebrowsercredential?view=azure-dotnet) in a Windows Forms app to authenticate with the [`BlobServiceClient`](/dotnet/api/azure.storage.blobs.blobserviceclient):
+The following example demonstrates using an <xref:Azure.Identity.InteractiveBrowserCredential> in a Windows Forms app to authenticate with the [`BlobServiceClient`](/dotnet/api/azure.storage.blobs.blobserviceclient):
 
 :::code language="csharp" source="../snippets/authentication/additional-auth/interactive/InteractiveBrokeredAuth.cs" highlight="16-20":::
 

docs/azure/sdk/authentication/user-assigned-managed-identity.md

@@ -41,7 +41,7 @@ User-assigned managed identities are created as standalone resources in your Azu
 
 ### [Azure CLI](#tab/azure-cli)
 
-Use the Azure CLI command [`az identity create`](/cli/azure/identity?view=azure-cli-latest#az-identity-create) to create a managed identity:
+Use the Azure CLI command [`az identity create`](/cli/azure/identity#az-identity-create) to create a managed identity:
 
 ```azurecli
 az identity create \
@@ -53,7 +53,7 @@ az identity create \
 
 The command output prints the client ID of the created user-assigned managed identity. The client ID is used to configure application code that relies on the identity.
 
-You can always view the managed identity properties again using the [`az identity show`](/cli/azure/identity?view=azure-cli-latest#az-identity-show) command:
+You can always view the managed identity properties again using the [`az identity show`](/cli/azure/identity#az-identity-show) command:
 
 ```azurecli
 az identity show \
@@ -83,7 +83,7 @@ A user-assigned managed identity can be associated with one or more Azure resour
 
 The Azure CLI provides different commands to assign a user-assigned managed identity to different types of hosting services.
 
-1. To assign a user-assigned managed identity to a resource such as an Azure App Service web app using the Azure CLI, you'll need the resource ID of the identity. Use the [`az identity show`](/cli/azure/identity?view=azure-cli-latest#az-identity-show) command to retrieve the resource ID:
+1. To assign a user-assigned managed identity to a resource such as an Azure App Service web app using the Azure CLI, you'll need the resource ID of the identity. Use the [`az identity show`](/cli/azure/identity#az-identity-show) command to retrieve the resource ID:
 
     ```azurecli
     az identity show \
@@ -95,7 +95,7 @@ The Azure CLI provides different commands to assign a user-assigned managed iden
 
 2. Once you have the resource ID, use the Azure CLI command `az <resourceType> identity assign` command to associate the user-assigned managed identity with different resources, such as the following:
 
-    For Azure App Service, use the Azure CLI command [`az webapp identity assign`](/cli/azure/webapp/identity?view=azure-cli-latest#az-webapp-identity-assign):
+    For Azure App Service, use the Azure CLI command [`az webapp identity assign`](/cli/azure/webapp/identity#az-webapp-identity-assign):
 
     ```azurecli
     az webapp identity assign \
@@ -104,7 +104,7 @@ The Azure CLI provides different commands to assign a user-assigned managed iden
         --identities <user-assigned-identity-resource-id>
     ```
 
-    For Azure Container Apps, use the Azure CLI command [`az containerapp identity assign`](/cli/azure/containerapp/identity?view=azure-cli-latest#az-containerapp-identity-assign):
+    For Azure Container Apps, use the Azure CLI command [`az containerapp identity assign`](/cli/azure/containerapp/identity#az-containerapp-identity-assign):
 
     ```azurecli
     az containerapp identity assign \
@@ -113,7 +113,7 @@ The Azure CLI provides different commands to assign a user-assigned managed iden
         --identities <user-assigned-identity-resource-id>
     ```
 
-    For Azure Virtual Machines, use the Azure CLI command [`az vm identity assign`](/cli/azure/vm/identity?view=azure-cli-latest#az-vm-identity-assign):
+    For Azure Virtual Machines, use the Azure CLI command [`az vm identity assign`](/cli/azure/vm/identity#az-vm-identity-assign):
 
     ```azurecli
     az vm identity assign \

docs/azure/sdk/pagination.md

@@ -27,16 +27,16 @@ For the latest directory of Azure SDK for .NET packages, see [Azure SDK latest r
 
 Clients instantiated from the Azure SDK for .NET can return the following pageable types.
 
-| Type | Description |
-|--|--|
-| [`Pageable<T>`](xref:Azure.Pageable%601) | A collection of values retrieved in pages |
+| Type                                               | Description                                              |
+|----------------------------------------------------|----------------------------------------------------------|
+| [`Pageable<T>`](xref:Azure.Pageable%601)           | A collection of values retrieved in pages                |
 | [`AsyncPageable<T>`](xref:Azure.AsyncPageable%601) | A collection of values asynchronously retrieved in pages |
 
 Most of the samples in this article are asynchronous, using variations of the `AsyncPageable<T>` type. Using asynchronous programming for I/O-bound operations is ideal. A perfect use case is using the async APIs from the Azure SDK for .NET as these operations represent HTTP/S network calls.
 
 ## Iterate over `AsyncPageable` with `await foreach`
 
-To iterate over an `AsyncPageable<T>` using the [`await foreach`](/dotnet/csharp/language-reference/proposals/csharp-8.0/async-streams#foreach) syntax, consider the following example:
+To iterate over an `AsyncPageable<T>` using the [`await foreach`](/dotnet/csharp/language-reference/language-specification/statements#13953-await-foreach) syntax, consider the following example:
 
 :::code source="snippets/pagination/Program.cs" range="38-46":::
 

docs/core/diagnostics/compare-metric-apis.md

@@ -58,5 +58,5 @@ Most application performance monitoring (APM) vendors such as [AppDynamics](http
 [Application Insights](/azure/azure-monitor/app/app-insights-overview),
 [DataDog](https://www.datadoghq.com/), [DynaTrace](https://www.dynatrace.com/), and
 [NewRelic](https://newrelic.com/) include metrics APIs as part of their instrumentation libraries.
-[Prometheus](https://github.com/prometheus-net/prometheus-net) and [AppMetrics](https://www.app-metrics.io/) are also popular .NET OSS projects.
+[Prometheus](https://github.com/prometheus-net/prometheus-net) and [AppMetrics](https://github.com/AppMetrics/AppMetrics) are also popular .NET OSS projects.
 To learn more about these projects, check the various project websites.