fix broken links (#51296)

gewarren · web-flow · commit e35b06df9ff8 · 2026-01-23T09:36:28.000-05:00
diff --git a/docs/ai/quickstarts/publish-mcp-registry.md b/docs/ai/quickstarts/publish-mcp-registry.md
@@ -10,7 +10,7 @@ ai-usage: ai-assisted
 
 # Publish an MCP server on NuGet.org to the Official MCP Registry
 
-In this quickstart, you publish your NuGet-based local MCP server to the [Official MCP Registry](https://github.com/modelcontextprotocol/registry/blob/main/docs/explanations/ecosystem-vision.md).
+In this quickstart, you publish your NuGet-based local MCP server to the [Official MCP Registry](https://github.com/modelcontextprotocol/registry/blob/main/docs/design/ecosystem-vision.md).
 
 The Official MCP Registry is an *upstream data source* for the MCP ecosystem. Other MCP registries, such as the [GitHub MCP Registry](https://github.com/mcp), will soon use the Official MCP Registry as a source of MCP server listings.
 
diff --git a/docs/architecture/cloud-native/azure-caching.md b/docs/architecture/cloud-native/azure-caching.md
@@ -35,7 +35,7 @@ Cloud native applications typically implement a distributed caching architecture
 
 In the previous figure, note how the cache is independent of and shared by the microservices. In this scenario, the cache is invoked by the [API Gateway](./front-end-communication.md). As discussed in chapter 4, the gateway serves as a front end for all incoming requests. The distributed cache increases system responsiveness by returning cached data whenever possible. Additionally, separating the cache from the services allows the cache to scale up or out independently to meet increased traffic demands.
 
-The previous figure presents a common caching pattern known as the [cache-aside pattern](/azure/architecture/patterns/cache-aside). For an incoming request, you first query the cache (step \#1) for a response. If found, the data is returned immediately. If the data doesn't exist in the cache (known as a [cache miss](https://www.techopedia.com/definition/6308/cache-miss)), it's retrieved from a local database in a downstream service (step \#2). It's then written to the cache for future requests (step \#3), and returned to the caller. Care must be taken to periodically evict cached data so that the system remains timely and consistent.
+The previous figure presents a common caching pattern known as the [*cache-aside pattern*](/azure/architecture/patterns/cache-aside). For an incoming request, you first query the cache (step \#1) for a response. If found, the data is returned immediately. If the data doesn't exist in the cache (known as a *cache miss*), it's retrieved from a local database in a downstream service (step \#2). It's then written to the cache for future requests (step \#3), and returned to the caller. Care must be taken to periodically evict cached data so that the system remains timely and consistent.
 
 As a shared cache grows, it might prove beneficial to partition its data across multiple nodes. Doing so can help minimize contention and improve scalability. Many Caching services support the ability to dynamically add and remove nodes and rebalance data across partitions. This approach typically involves clustering. Clustering exposes a collection of federated nodes as a seamless, single cache. Internally, however, the data is dispersed across the nodes following a predefined distribution strategy that balances the load evenly.
 
@@ -51,7 +51,7 @@ Azure Cache for Redis is more than a simple cache server. It can support a numbe
 - A distributed non-relational database
 - A message broker
 - A configuration or discovery server
-  
+
 For advanced scenarios, a copy of the cached data can be [persisted to disk](/azure/azure-cache-for-redis/cache-how-to-premium-persistence). If a catastrophic event disables both the primary and replica caches, the cache is reconstructed from the most recent snapshot.
 
 Azure Redis Cache is available across a number of predefined configurations and pricing tiers. The [Premium tier](/azure/azure-cache-for-redis/cache-overview#service-tiers) features many enterprise-level features such as clustering, data persistence, geo-replication, and virtual-network isolation.
diff --git a/docs/architecture/microservices/microservice-ddd-cqrs-patterns/nosql-database-persistence-infrastructure.md b/docs/architecture/microservices/microservice-ddd-cqrs-patterns/nosql-database-persistence-infrastructure.md
@@ -132,7 +132,7 @@ Cosmos DB databases support MongoDB API for .NET as well as the native MongoDB w
 
 **Figure 7-20**. Using MongoDB API and protocol to access Azure Cosmos DB
 
-This is a very convenient approach for proof of concepts in Docker environments with Linux containers because the [MongoDB Docker image](https://hub.docker.com/r/_/mongo/) is a multi-arch image that supports Docker Linux containers and Docker Windows containers.
+This is a very convenient approach for proof of concepts in Docker environments with Linux containers because the [MongoDB Docker image](https://hub.docker.com/_/mongo/) is a multi-arch image that supports Docker Linux containers and Docker Windows containers.
 
 As shown in the following image, by using the MongoDB API, eShopOnContainers supports MongoDB Linux and Windows containers for the local development environment but then, you can move to a scalable, PaaS cloud solution as Azure Cosmos DB by simply [changing the MongoDB connection string to point to Azure Cosmos DB](/azure/cosmos-db/connect-mongodb-account).
 
diff --git a/docs/architecture/microservices/multi-container-microservice-net-applications/subscribe-events.md b/docs/architecture/microservices/multi-container-microservice-net-applications/subscribe-events.md
@@ -345,9 +345,6 @@ If the "redelivered" flag is set, the receiver must take that into account, beca
 - **Introducing Event Sourcing** \
     [https://learn.microsoft.com/previous-versions/msp-n-p/jj591559(v=pandp.10)](/previous-versions/msp-n-p/jj591559(v=pandp.10))
 
-- **Event Store database**. Official site. \
-    <https://geteventstore.com/>
-
 - **Patrick Nommensen. Event-Driven Data Management for Microservices** \
     <https://dzone.com/articles/event-driven-data-management-for-microservices-1>
 
diff --git a/docs/core/whats-new/dotnet-10/overview.md b/docs/core/whats-new/dotnet-10/overview.md
@@ -35,7 +35,7 @@ For more information, see [What's new in the SDK for .NET 10](sdk.md).
 
 ## Aspire
 
-For information about what's new in Aspire, see [Aspire — what's new?](/dotnet/aspire/whats-new/).
+For information about what's new in Aspire, see [What's new in Aspire 13.1](https://aspire.dev/whats-new/aspire-13-1/).
 
 ## ASP.NET Core
 
diff --git a/docs/core/whats-new/dotnet-9/overview.md b/docs/core/whats-new/dotnet-9/overview.md
@@ -101,7 +101,7 @@ The latest release introduces significant new capabilities for tokenizers:
 
 ## Aspire
 
-Aspire is a set of powerful tools, templates, and packages for building observable, production ready apps.​ Aspire's latest release includes improvements to the dashboard and resource lifecycle management. It also adds new integrations and APIs for more flexibility during development. Aspire 9 works with both .NET 9 and .NET 8 apps. For more information, see [What's new in Aspire 9](/dotnet/aspire/whats-new/dotnet-aspire-9-release-candidate-1).
+Aspire is a set of powerful tools, templates, and packages for building observable, production ready apps.​ Aspire's latest release includes improvements to the dashboard and resource lifecycle management. It also adds new integrations and APIs for more flexibility during development. Aspire 9 works with both .NET 9 and .NET 8 apps. For more information, see [What's new in Aspire 9](https://aspire.dev/whats-new/aspire-9/).
 
 ## ASP.NET Core
 
diff --git a/docs/standard/data/xml/rules-for-inferring-simple-types.md b/docs/standard/data/xml/rules-for-inferring-simple-types.md
@@ -63,12 +63,12 @@ Describes how the <xref:System.Xml.Schema.XmlSchemaInference> class infers the d
 
 The following are schema-defining attributes that are ignored during schema inference.
 
-|Attribute|Description|
-|---------------|-----------------|
-|`xsi:type`|If an element is encountered with `xsi:type` specified, the `xsi:type` is ignored.|
-|`xsi:nil`|If an element with an `xsi:nil` attribute is encountered, its element declaration in the inferred schema has the value of `nillable="true"`. An element with an `xsi:nil` attribute set to `true` cannot have child elements.|
-|`xsi:schemaLocation`|If `xsi:schemaLocation` is encountered, it is ignored.|
-|`xsi:noNamespaceSchemaLocation`|If `xsi:noNamespaceSchemaLocation` is encountered, it is ignored.|
+| Attribute                       | Description                                                                        |
+|---------------------------------|------------------------------------------------------------------------------------|
+| `xsi:type`                      | If an element is encountered with `xsi:type` specified, the `xsi:type` is ignored. |
+| `xsi:nil`                       | If an element with an `xsi:nil` attribute is encountered, its element declaration in the inferred schema has the value of `nillable="true"`. An element with an `xsi:nil` attribute set to `true` cannot have child elements. |
+| `xsi:schemaLocation`            | If `xsi:schemaLocation` is encountered, it is ignored.                             |
+| `xsi:noNamespaceSchemaLocation` | If `xsi:noNamespaceSchemaLocation` is encountered, it is ignored.                  |
 
 ## See also
 

-Original file line number
+Diff line change
 ## Aspire
 -Aspire is a set of powerful tools, templates, and packages for building observable, production ready apps. Aspire's latest release includes improvements to the dashboard and resource lifecycle management. It also adds new integrations and APIs for more flexibility during development. Aspire 9 works with both .NET 9 and .NET 8 apps. For more information, see [What's new in Aspire 9](/dotnet/aspire/whats-new/dotnet-aspire-9-release-candidate-1).
 +Aspire is a set of powerful tools, templates, and packages for building observable, production ready apps. Aspire's latest release includes improvements to the dashboard and resource lifecycle management. It also adds new integrations and APIs for more flexibility during development. Aspire 9 works with both .NET 9 and .NET 8 apps. For more information, see [What's new in Aspire 9](https://aspire.dev/whats-new/aspire-9/).
 ## ASP.NET Core