fix broken links and build suggestions (#49503)

Author: gewarren

docs/architecture/cloud-native/observability-patterns.md

@@ -51,7 +51,7 @@ The high performance of logging tools and the tunability of verbosity should enc
 
 Because of the challenges associated with using file-based logs in cloud-native apps, centralized logs are preferred. Logs are collected by the applications and shipped to a central logging application which indexes and stores the logs. This class of system can ingest tens of gigabytes of logs every day.
 
-It's also helpful to follow some standard practices when building logging that spans many services. For instance, generating a [correlation ID](https://blog.rapid7.com/2016/12/23/the-value-of-correlation-ids/) at the start of a lengthy interaction, and then logging it in each message that is related to that interaction, makes it easier to search for all related messages. One need only find a single message and extract the correlation ID to find all the related messages. Another example is ensuring that the log format is the same for every service, whatever the language or logging library it uses. This standardization makes reading logs much easier. Figure 7-4 demonstrates how a microservices architecture can leverage centralized logging as part of its workflow.
+It's also helpful to follow some standard practices when building logging that spans many services. For instance, generating a correlation ID at the start of a lengthy interaction, and then logging it in each message that is related to that interaction, makes it easier to search for all related messages. One need only find a single message and extract the correlation ID to find all the related messages. Another example is ensuring that the log format is the same for every service, whatever the language or logging library it uses. This standardization makes reading logs much easier. Figure 7-4 demonstrates how a microservices architecture can leverage centralized logging as part of its workflow.
 
 ![Logs from various sources are ingested into a centralized log store.](./media/centralized-logging.png)
 **Figure 7-4**. Logs from various sources are ingested into a centralized log store.

docs/core/extensions/httpclient-latency-extensions.md

@@ -53,7 +53,7 @@ This registration adds a `DelegatingHandler` to all HTTP clients created through
 
 ### Configure telemetry options
 
-You configure telemetry collection through the <xref:Microsoft.Extensions.Http.Latency.HttpClientLatencyTelemetryOptions> ([standard options pattern](https://learn.microsoft.com/dotnet/core/extensions/options)).
+You configure telemetry collection through the <xref:Microsoft.Extensions.Http.Latency.HttpClientLatencyTelemetryOptions> ([standard options pattern](options.md)).
 You can supply values either with a delegate or by binding configuration (for example, `appsettings.json`).
 The options instance is resolved once per handler pipeline so changes apply to new clients/handlers.
 

docs/core/porting/versioning-sdk-msbuild-vs.md

@@ -69,9 +69,9 @@ The support timeframe for the SDK typically matches that of the Visual Studio ve
 >
 > <sup>2</sup> .4xx .NET SDK feature bands are supported for the life of the matching runtime as stand-alone installs.
 >
-> [Visual Studio 2019 Lifecycle](https://learn.microsoft.com/lifecycle/products/visual-studio-2019)
+> [Visual Studio 2019 Lifecycle](/lifecycle/products/visual-studio-2019)
 >
-> [Visual Studio 2022 Lifecycle](https://learn.microsoft.com/lifecycle/products/visual-studio-2022)
+> [Visual Studio 2022 Lifecycle](/lifecycle/products/visual-studio-2022)
 
 ## Targeting and support rules
 

docs/core/tools/telemetry.md

@@ -36,7 +36,7 @@ A single telemetry entry is also sent by the .NET SDK installer when a successfu
 The .NET SDK displays text similar to the following when you first run one of the [.NET CLI commands](index.md) (for example, `dotnet build`). Text might vary slightly depending on the version of the SDK you're running. This "first run" experience is how Microsoft notifies you about data collection.
 
 > [!NOTE]
-> **Breaking change:** The behavior of telemetry messages written to `stderr` has changed in recent versions of the .NET SDK. For more information, see the [breaking change documentation](/dotnet/core/compatibility/sdk/8.0/telemetry-stderr-behavior).
+> **Breaking change:** The behavior of telemetry messages written to `stderr` has changed in recent versions of the .NET SDK. For more information, see [dotnet CLI commands log non-command-relevant data to stderr](../compatibility/sdk/10.0/dotnet-cli-stderr-output.md).
 
 ```console
 Telemetry

docs/core/whats-new/dotnet-10/libraries.md

@@ -269,7 +269,7 @@ This index can then be used with <xref:System.Collections.Generic.OrderedDiction
 
 :::code language="csharp" source="../snippets/dotnet-10/csharp/snippets.cs" id="snippet_getAtSetAt":::
 
-This new API is already used in <xref:System.Json.JsonObject> and improves the performance of updating properties by 10-20%.
+This new API is already used in <xref:System.Text.Json.Nodes.JsonObject> and improves the performance of updating properties by 10-20%.
 
 ## Serialization
 

docs/core/whats-new/dotnet-9/libraries.md

@@ -520,7 +520,7 @@ For more information, see [Non-optional constructor parameters](../../../standar
 
 ### Order JsonObject properties
 
-The <xref:System.Json.JsonObject> type now exposes ordered dictionary&ndash;like APIs that enable explicit property order manipulation.
+The <xref:System.Text.Json.Nodes.JsonObject> type now exposes ordered dictionary&ndash;like APIs that enable explicit property order manipulation.
 
 :::code language="csharp" source="../snippets/dotnet-9/csharp/Serialization.cs" id="PropertyOrder":::
 

docs/fundamentals/networking/telemetry/metrics.md

@@ -2,7 +2,6 @@
 title: Networking metrics
 description: Learn how to consume .NET networking Metrics.
 author: antonfirsov
-ms.author: anfirszo
 ms.date: 11/14/2023
 ---