Fix MD059 violations (#46315)

Author: gewarren

.markdownlint-cli2.jsonc

@@ -59,8 +59,7 @@
         "MD050": {
             "style": "asterisk"
         },
-        "MD051": false,
-        "MD059": false
+        "MD051": false
     },
     "ignores": [
         ".github/",

docs/architecture/blazor-for-web-forms-developers/security-authentication-authorization.md

@@ -255,15 +255,15 @@ It's also worth considering putting any additional columns on separate tables. S
 
 ### Migrating data from universal providers to ASP.NET Core Identity
 
-Once you have the destination table schema in place, the next step is to migrate your user and role records to the new schema. A complete list of the schema differences, including which columns map to which new columns, can be found [here](/aspnet/core/migration/proper-to-2x/membership-to-core-identity).
+Once you have the destination table schema in place, the next step is to migrate your user and role records to the new schema. For a complete list of the schema differences, including which columns map to which new columns, see [Migrate from ASP.NET Membership authentication to ASP.NET Core 2.0 Identity](/aspnet/core/migration/proper-to-2x/membership-to-core-identity).
 
-To migrate your users from membership to the new identity tables, you should [follow the steps described in the documentation](/aspnet/core/migration/proper-to-2x/membership-to-core-identity). After following these steps and the script provided, your users will need to change their password the next time they log in.
+To migrate your users from membership to the new identity tables, follow the steps described in [Migrate from ASP.NET Membership authentication to ASP.NET Core 2.0 Identity](/aspnet/core/migration/proper-to-2x/membership-to-core-identity). After following these steps and the script provided, your users will need to change their password the next time they log in.
 
-It is possible to migrate user passwords but the process is much more involved. Requiring users to update their passwords as part of the migration process, and encouraging them to use new, unique passwords, is likely to enhance the overall security of the application.
+It's possible to migrate user passwords, but the process is much more involved. Requiring users to update their passwords as part of the migration process, and encouraging them to use new, unique passwords, is likely to enhance the overall security of the application.
 
 ### Migrating security settings from web.config to app startup
 
-As noted above, ASP.NET membership and role providers are configured in the application's `web.config` file. Since ASP.NET Core apps are not tied to IIS and use a separate system for configuration, these settings must be configured elsewhere. For the most part, ASP.NET Core Identity is configured in the *Program.cs* file. Open the web project that was created earlier (to generate the identity table schema) and review its *Program.cs* (or *Startup.cs*) file.
+As noted previously, ASP.NET membership and role providers are configured in the application's `web.config` file. Since ASP.NET Core apps are not tied to IIS and use a separate system for configuration, these settings must be configured elsewhere. For the most part, ASP.NET Core Identity is configured in the *Program.cs* file. Open the web project that was created earlier (to generate the identity table schema) and review its *Program.cs* (or *Startup.cs*) file.
 
 This code adds support for EF Core and Identity:
 

docs/architecture/cloud-native/deploy-eshoponcontainers-azure.md

@@ -57,7 +57,8 @@ You'll find the eShopOnContainers helm charts in the /k8s/helm folder. Figure 2-
 
 Each individual component is installed using a `helm install` command. eShop includes a "deploy all" script that loops through and installs the components using their respective helm charts. The result is a repeatable process, versioned with the application in source control, that anyone on the team can deploy to an AKS cluster with a one-line script command.
 
-> Note that version 3 of Helm officially removes the need for the Tiller server component. More information on this enhancement can be found [here](https://medium.com/better-programming/why-is-tiller-missing-in-helm-3-2347c446714).
+> [!NOTE]
+> Version 3 of Helm officially removes the need for the Tiller server component. For more information on this enhancement, see [Why is Tiller Missing in Helm 3?](https://medium.com/better-programming/why-is-tiller-missing-in-helm-3-2347c446714).
 
 ## Azure Functions and Logic Apps (Serverless)
 

docs/architecture/microservices/microservice-ddd-cqrs-patterns/infrastructure-persistence-layer-implementation-entity-framework-core.md

@@ -408,7 +408,7 @@ public abstract class BaseSpecification<T> : ISpecification<T>
     }
 
     // string-based includes allow for including children of children
-    // e.g. Basket.Items.Product
+    // for example, Basket.Items.Product
     protected virtual void AddInclude(string includeString)
     {
         IncludeStrings.Add(includeString);

docs/core/extensions/log-sampling.md

@@ -104,7 +104,7 @@ Log sampling rules evaluation is performed on each log record, however, there ar
 - Select rules with `EventId` not defined or defined and equal to the log event ID.
 - Select rules with longest matching category prefix. If no match is found, select all rules that don't specify a category.
 - If multiple rules are selected, take the **last** one.
-- If no rules are selected, sampling is not applied, e.g. the log record is emitted as usual.
+- If no rules are selected, sampling is not applied, for example, the log record is emitted as usual.
 
 ### Inline code configuration
 
@@ -143,18 +143,18 @@ For each log record that isn't filtered out, the <xref:Microsoft.Extensions.Logg
 
 Log sampling is designed to reduce storage costs, with a trade-off of slightly increased CPU usage. If your application generates a high volume of logs that are expensive to store, sampling can help reduce that volume. When configured appropriately, sampling can lower storage costs without losing information that's critical for diagnosing incidents.
 
-For the built-in sampling, see the benchmarks [here](https://github.com/dotnet/extensions/blob/main/bench/Libraries/Microsoft.Extensions.Telemetry.PerformanceTests/README.md).
+For the built-in sampling, see [Benchmarks](https://github.com/dotnet/extensions/blob/main/bench/Libraries/Microsoft.Extensions.Telemetry.PerformanceTests/README.md).
 
 ## Log level guidance on when to use sampling
 
-| Log level | Recommendation |
-|--|--|
-| <xref:Microsoft.Extensions.Logging.LogLevel.Trace> | Don't apply sampling, because normally you disable these logs in production |
-| <xref:Microsoft.Extensions.Logging.LogLevel.Debug> | Don't apply sampling, because normally you disable these logs in production |
-| <xref:Microsoft.Extensions.Logging.LogLevel.Information> | Do apply sampling |
-| <xref:Microsoft.Extensions.Logging.LogLevel.Warning> | Consider applying sampling |
-| <xref:Microsoft.Extensions.Logging.LogLevel.Error> | Don't apply sampling |
-| <xref:Microsoft.Extensions.Logging.LogLevel.Critical> | Don't apply sampling |
+| Log level                                                | Recommendation             |
+|----------------------------------------------------------|----------------------------|
+| <xref:Microsoft.Extensions.Logging.LogLevel.Trace>       | Don't apply sampling, because normally you disable these logs in production |
+| <xref:Microsoft.Extensions.Logging.LogLevel.Debug>       | Don't apply sampling, because normally you disable these logs in production |
+| <xref:Microsoft.Extensions.Logging.LogLevel.Information> | Do apply sampling          |
+| <xref:Microsoft.Extensions.Logging.LogLevel.Warning>     | Consider applying sampling |
+| <xref:Microsoft.Extensions.Logging.LogLevel.Error>       | Don't apply sampling       |
+| <xref:Microsoft.Extensions.Logging.LogLevel.Critical>    | Don't apply sampling       |
 
 ## Best practices
 

docs/core/testing/microsoft-testing-platform-architecture-extensions.md

@@ -494,11 +494,11 @@ internal sealed class TestingFramework
 
 #### Well-known properties
 
-As detailed in the [requests section](#handling-requests), the testing platform identifies specific properties added to the `TestNodeUpdateMessage` to determine the status of a `TestNode` (e.g., successful, failed, skipped, etc.). This allows the runtime to accurately display a list of failed tests with their corresponding information in the console, and to set the appropriate exit code for the test process.
+As detailed in the [requests section](#handling-requests), the testing platform identifies specific properties added to the `TestNodeUpdateMessage` to determine the status of a `TestNode` (for example, successful, failed, skipped, etc.). This allows the runtime to accurately display a list of failed tests with their corresponding information in the console, and to set the appropriate exit code for the test process.
 
 In this segment, we'll elucidate the various well-known `IProperty` options and their respective implications.
 
-If you're looking for a comprehensive list of well-known properties, you can find it [here](https://github.com/microsoft/testfx/blob/main/src/Platform/Microsoft.Testing.Platform/Messages/TestNodeProperties.cs). If you notice that a property description is missing, please don't hesitate to file an issue.
+For a comprehensive list of well-known properties, see [TestNodeProperties.cs](https://github.com/microsoft/testfx/blob/main/src/Platform/Microsoft.Testing.Platform/Messages/TestNodeProperties.cs). If you notice that a property description is missing, please file an issue.
 
 These properties can be divided in the following categories:
 

docs/core/testing/unit-testing-code-coverage.md

@@ -271,7 +271,7 @@ Below is the example *coverage.cobertura.xml* file.
 > ```
 >
 > The resulting *coverage.cobertura.xml* file is output.
-> You can follow MSBuild integration guide [here](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/MSBuildIntegration.md)
+> For more information, see [Coverlet integration with MSBuild](https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/MSBuildIntegration.md)
 
 ## Generate reports
 

docs/core/testing/unit-testing-mstest-getting-started.md

@@ -16,7 +16,7 @@ MSTest functionality is split into multiple NuGet packages:
 
 We recommend that you don't install these packages directly into your test projects. Instead, you should use either:
 
-- [MSTest.Sdk](https://www.nuget.org/packages/MSTest.Sdk): A [MSBuild project SDK](/visualstudio/msbuild/how-to-use-project-sdk) that includes all the recommended packages and greatly simplifies all the boilerplate configuration. Although this is shipped as a NuGet package, it's not intended to be installed as a regular package dependency, instead you should modify the `Sdk` part of your project (e.g. `<Project Sdk="MSTest.Sdk">` or `<Project Sdk="MSTest.Sdk/X.Y.Z">` where `X.Y.Z` is MSTest version). For more information, please refer to [MSTest SDK overview](./unit-testing-mstest-sdk.md).
+- [MSTest.Sdk](https://www.nuget.org/packages/MSTest.Sdk): A [MSBuild project SDK](/visualstudio/msbuild/how-to-use-project-sdk) that includes all the recommended packages and greatly simplifies all the boilerplate configuration. Although this is shipped as a NuGet package, it's not intended to be installed as a regular package dependency, instead you should modify the `Sdk` part of your project (for example, `<Project Sdk="MSTest.Sdk">` or `<Project Sdk="MSTest.Sdk/X.Y.Z">` where `X.Y.Z` is MSTest version). For more information, please refer to [MSTest SDK overview](./unit-testing-mstest-sdk.md).
 
 - the [MSTest](https://www.nuget.org/packages/MSTest) NuGet package, which includes all recommended packages: `MSTest.TestFramework`, `MSTest.TestAdapter`, `MSTest.Analyzers` and `Microsoft.NET.Test.Sdk`.
 

docs/core/testing/unit-testing-mstest-migration-from-v1-to-v3.md

@@ -30,7 +30,7 @@ Even if you’re satisfied with your current MSTest setup, upgrading to MSTest v
 
 - **Increased Code Reliability with New Analyzers**: MSTest v3 built-in code analyzers enforce best practices, helping to catch issues early and promoting cleaner, more maintainable test code:
   - **Proactive Issue Detection**: The analyzers provide real-time feedback, suggesting improvements and flagging potential issues as you write your tests.
-  
+
   - **Stronger Type-Safe Assertions**: Replacing ambiguous overloads, MSTest v3 enforces type-safe assertions, reducing the risk of incorrect test behavior and making tests more reliable.
   - **Cleaner Code, Less Maintenance**: By aligning your tests with MSTest standards and best practices, MSTest v3 helps you maintain a cleaner, more manageable codebase, reducing technical debt over time.
 
@@ -146,7 +146,7 @@ In cases where types don’t match exactly, MSTest v3 will now raise an error ra
 
 In MSTest v3, the handling of `Timeout` settings has been standardized to ensure consistent behavior across different .NET environments. This change may impact tests that rely on specific timeout values, especially if those tests are asynchronous or run under different frameworks.
 
-- In MSTest v1 or v2, certain timeout settings might have been interpreted differently depending on the framework (e.g., .NET Framework vs. .NET Core).
+- In MSTest v1 or v2, certain timeout settings might have been interpreted differently depending on the framework (for example, .NET Framework vs. .NET Core).
 - MSTest v3 enforces consistent timeout behavior, which might mean that tests configured with timeouts in previous versions may fail or behave differently if the timeout values are too short under the new standard.
 
 **What This Means**:
@@ -166,7 +166,7 @@ public void TestMethod() { ... }
 // New (v3) - Unified handling of timeout
 [TestMethod]
 [Timeout(2000)] // Verify this value still works under MSTest v3
-public async Task TestMethod() { ... } 
+public async Task TestMethod() { ... }
 ```
 
 ## Configuration changes

docs/csharp/delegate-class.md

@@ -38,7 +38,7 @@ The compiler generates a class, derived from `System.Delegate`
 that matches the signature used (in this case, a method that
 returns an integer, and has two arguments). The type
 of that delegate is `Comparison`. The `Comparison` delegate
-type is a generic type. For details on generics see [here](fundamentals/types/generics.md).
+type is a generic type. For more information, see [Generic classes and methods](./fundamentals/types/generics.md).
 
 Notice that the syntax may appear as though it is declaring
 a variable, but it is actually declaring a *type*. You can