From fa2214584ce6ddda2c41d8bbe86f99c68f1ca5e3 Mon Sep 17 00:00:00 2001
From: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Date: Thu, 23 Jan 2025 17:45:08 -0800
Subject: [PATCH] fix up missing periods

---
 docs/azure/key-azure-services.md              |  6 +-
 docs/azure/migration/vm.md                    |  2 +-
 docs/azure/sdk/resource-management.md         |  4 +-
 .../aspnet-core/6.0/obsolete-removed-apis.md  |  2 +-
 .../prepare-libraries-for-trimming.md         |  2 +-
 .../trimming/trim-warnings/il2016.md          |  4 +-
 .../trimming/trim-warnings/il2017.md          |  4 +-
 docs/core/diagnostics/built-in-metrics.md     |  2 +-
 docs/core/diagnostics/compare-metric-apis.md  |  3 +-
 docs/core/diagnostics/debug-stackoverflow.md  |  8 +-
 docs/core/diagnostics/event-counters.md       |  8 +-
 .../eventsource-getting-started.md            |  2 +-
 .../eventsource-instrumentation.md            |  5 +-
 docs/core/docker/container-images.md          |  4 +-
 .../extensions/custom-logging-provider.md     |  2 +-
 docs/core/extensions/logging.md               |  4 +-
 docs/core/extensions/options.md               |  2 +-
 docs/core/install/windows.md                  |  2 +-
 docs/core/porting/modernize.md                |  2 +-
 .../porting/net-framework-tech-unavailable.md |  2 +-
 .../upgrade-assistant-how-to-analyze.md       |  4 +-
 .../upgrade-assistant-how-to-upgrade.md       |  4 +-
 .../core/porting/upgrade-assistant-install.md |  4 +-
 docs/core/project-sdk/overview.md             |  2 +-
 ...esting-platform-architecture-extensions.md |  2 +-
 .../testing/unit-testing-platform-intro.md    |  2 +-
 .../tools/dotnet-environment-variables.md     |  2 +-
 docs/core/tools/dotnet-new-details.md         |  2 +-
 docs/core/tools/dotnet-new-install.md         |  8 +-
 docs/core/tools/dotnet-tool-list.md           |  4 +-
 docs/core/tools/local-tools-how-to-use.md     |  2 +-
 docs/core/tools/sdk-errors/netsdk1079.md      |  4 +-
 docs/core/tools/troubleshoot-usage-issues.md  |  2 +-
 .../reflection-and-attributes/index.md        |  2 +-
 .../builtin-types/struct.md                   |  4 +-
 .../language-reference/keywords/interface.md  |  6 +-
 .../language-reference/statements/yield.md    |  8 +-
 .../named-and-optional-arguments.md           | 18 ++---
 .../dotnet-cli-and-continuous-integration.md  |  2 +-
 docs/devops/github-actions-overview.md        |  4 +-
 docs/fsharp/tools/development-tools.md        |  2 +-
 .../diagnostics/runtime-contention-events.md  | 48 ++++++------
 .../diagnostics/runtime-exception-events.md   |  2 +-
 .../runtime-garbage-collection-events.md      |  2 +-
 .../diagnostics/runtime-interop-events.md     |  2 +-
 .../runtime-loader-binder-events.md           |  2 +-
 .../diagnostics/runtime-method-events.md      |  2 +-
 .../diagnostics/runtime-thread-events.md      |  2 +-
 .../runtime-tiered-compilation-events.md      |  2 +-
 .../diagnostics/runtime-type-events.md        |  2 +-
 docs/orleans/deployment/consul-deployment.md  |  2 +-
 docs/orleans/deployment/kubernetes.md         |  2 +-
 docs/orleans/grains/grain-placement.md        |  2 +-
 docs/orleans/migration-guide.md               | 10 +--
 docs/orleans/overview.md                      |  2 +-
 .../overview-helloworld.md                    |  8 +-
 .../tutorials-and-samples/tutorial-1.md       |  2 +-
 .../event-based-asynchronous-pattern-eap.md   | 78 +++++++++----------
 .../comwrappers-source-generation.md          |  2 +-
 .../task-based-asynchronous-programming.md    |  6 +-
 .../system-text-json/customize-properties.md  |  2 +-
 61 files changed, 167 insertions(+), 171 deletions(-)

diff --git a/docs/azure/key-azure-services.md b/docs/azure/key-azure-services.md
index 7c766415848a3..347c630743840 100644
--- a/docs/azure/key-azure-services.md
+++ b/docs/azure/key-azure-services.md
@@ -22,8 +22,8 @@ While Azure contains over 100 services, the following Azure services are the ser
 | ![Azure Service Bus Icon](./media/service-bus.svg) | **Azure Service Bus**   | Azure Service Bus is a fully managed enterprise message broker supporting both point to point and publish-subscribe integrations.  It is ideal for building decoupled applications, queue based load leveling, or facilitating communication between microservices.   |
 | ![Azure Key Vault Icon](./media/azure-key-vault.svg) | **Azure Key Vault**   | Every application has application secrets like connection strings and API keys it must store.  Azure Key Vault helps you store and access those secrets securely, in an encrypted vault with restricted access to make sure your secrets and your application are not compromised.   |
 
-For the full list of Azure products and services, visit the [Azure documentation home page](/azure/?product=all)
+For the full list of Azure products and services, visit the [Azure documentation home page](/azure/?product=all).
 
-### Next steps
+## Next steps
 
-Start configuring your Azure development environment by [Creating an Azure Account](create-azure-account.md)
+Start configuring your Azure development environment by [Creating an Azure Account](create-azure-account.md).
diff --git a/docs/azure/migration/vm.md b/docs/azure/migration/vm.md
index f444f40458691..3faa8a728c7b4 100644
--- a/docs/azure/migration/vm.md
+++ b/docs/azure/migration/vm.md
@@ -52,7 +52,7 @@ Azure Virtual Networks enable you to:
 - Connect your VM to your on-premises network using one of several [connectivity options](/azure/vpn-gateway/vpn-gateway-about-vpngateways#s2smulti)
 - Integrate your virtual machine into your on-premises network using [ExpressRoute](https://azure.microsoft.com/services/expressroute/)
 
-To get started, see the [Virtual Network documentation](/azure/virtual-network/)
+To get started, see the [Virtual Network documentation](/azure/virtual-network/).
 
 ### Active Directory
 
diff --git a/docs/azure/sdk/resource-management.md b/docs/azure/sdk/resource-management.md
index ad282af92a552..8419e5df42750 100644
--- a/docs/azure/sdk/resource-management.md
+++ b/docs/azure/sdk/resource-management.md
@@ -18,13 +18,13 @@ Those packages follow the [new Azure SDK guidelines](https://azure.github.io/azu
 - Distributed tracing.
 
 > [!NOTE]
-> You may notice that some packages are still pre-release version, phased releases of additional Azure services' management plane libraries are in process. If you are looking for a stable version package for a particular azure resource and currently only a pre-release version is available, please raise an issue in [Azure SDK for .NET Github repo](https://github.com/Azure/azure-sdk-for-net/issues/new?assignees=&labels=&template=02_feature_request.yml&title=%5BFEATURE+REQ%5D)
+> You might notice that some packages are still prerelease version. Phased releases of additional Azure services' management plane libraries are in process. If you're looking for a stable version package for a particular Azure resource and currently only a prerelease version is available, please raise an issue in [Azure SDK for .NET GitHub repo](https://github.com/Azure/azure-sdk-for-net/issues/new?assignees=&labels=&template=02_feature_request.yml&title=%5BFEATURE+REQ%5D).
 
 ## Get started
 
 ### Prerequisites
 
-- An [Azure subscription](https://azure.microsoft.com/free/dotnet/)
+- An [Azure subscription](https://azure.microsoft.com/free/dotnet/).
 - A [TokenCredential](/dotnet/api/azure.core.tokencredential?view=azure-dotnet&preserve-view=false) implementation, such as an [Azure Identity library credential type](/dotnet/api/overview/azure/Identity-readme#credential-classes).
 
 ### Install the package
diff --git a/docs/core/compatibility/aspnet-core/6.0/obsolete-removed-apis.md b/docs/core/compatibility/aspnet-core/6.0/obsolete-removed-apis.md
index a77d24f5ea271..7d6647d88c6cf 100644
--- a/docs/core/compatibility/aspnet-core/6.0/obsolete-removed-apis.md
+++ b/docs/core/compatibility/aspnet-core/6.0/obsolete-removed-apis.md
@@ -38,7 +38,7 @@ Use the recommended replacement APIs.
 * Removed the constructor [Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor](/dotnet/api/microsoft.aspnetcore.mvc.infrastructure.objectresultexecutor.-ctor?view=aspnetcore-3.1&preserve-view=true#Microsoft_AspNetCore_Mvc_Infrastructure_ObjectResultExecutor__ctor_Microsoft_AspNetCore_Mvc_Infrastructure_OutputFormatterSelector_Microsoft_AspNetCore_Mvc_Infrastructure_IHttpResponseStreamWriterFactory_Microsoft_Extensions_Logging_ILoggerFactory_). Use <xref:Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.%23ctor(Microsoft.AspNetCore.Mvc.Infrastructure.OutputFormatterSelector,Microsoft.AspNetCore.Mvc.Infrastructure.IHttpResponseStreamWriterFactory,Microsoft.Extensions.Logging.ILoggerFactory,Microsoft.Extensions.Options.IOptions{Microsoft.AspNetCore.Mvc.MvcOptions})?displayProperty=nameWithType> instead.
 * Removed [Microsoft.AspNetCore.Mvc.ModelBinding.Validation.ValidationVisitor.AllowShortCircuitingValidationWhenNoValidatorsArePresent](/dotnet/api/microsoft.aspnetcore.mvc.modelbinding.validation.validationvisitor.allowshortcircuitingvalidationwhennovalidatorsarepresent?view=aspnetcore-3.1&preserve-view=true#Microsoft_AspNetCore_Mvc_ModelBinding_Validation_ValidationVisitor_AllowShortCircuitingValidationWhenNoValidatorsArePresent).
 * Removed [Microsoft.AspNetCore.Mvc.ViewFeatures.ViewComponentResultExecutor](/dotnet/api/microsoft.aspnetcore.mvc.viewfeatures.viewcomponentresultexecutor.-ctor?view=aspnetcore-3.1&preserve-view=true#Microsoft_AspNetCore_Mvc_ViewFeatures_ViewComponentResultExecutor__ctor_Microsoft_Extensions_Options_IOptions_Microsoft_AspNetCore_Mvc_MvcViewOptions__Microsoft_Extensions_Logging_ILoggerFactory_System_Text_Encodings_Web_HtmlEncoder_Microsoft_AspNetCore_Mvc_ModelBinding_IModelMetadataProvider_Microsoft_AspNetCore_Mvc_ViewFeatures_ITempDataDictionaryFactory_). Use <xref:Microsoft.AspNetCore.Mvc.ViewFeatures.ViewComponentResultExecutor.%23ctor(Microsoft.Extensions.Options.IOptions{Microsoft.AspNetCore.Mvc.MvcViewOptions},Microsoft.Extensions.Logging.ILoggerFactory,System.Text.Encodings.Web.HtmlEncoder,Microsoft.AspNetCore.Mvc.ModelBinding.IModelMetadataProvider,Microsoft.AspNetCore.Mvc.ViewFeatures.ITempDataDictionaryFactory,Microsoft.AspNetCore.Mvc.Infrastructure.IHttpResponseStreamWriterFactory)?displayProperty=nameWithType> instead.
-* Obsoleted [CompatibilityVersion](/dotnet/api/microsoft.aspnetcore.mvc.compatibilityversion?view=aspnetcore-3.1&preserve-view=true)
+* Obsoleted [CompatibilityVersion](/dotnet/api/microsoft.aspnetcore.mvc.compatibilityversion?view=aspnetcore-3.1&preserve-view=true).
 
 <!--
 
diff --git a/docs/core/deploying/trimming/prepare-libraries-for-trimming.md b/docs/core/deploying/trimming/prepare-libraries-for-trimming.md
index edaf75cad620a..8185473604f72 100644
--- a/docs/core/deploying/trimming/prepare-libraries-for-trimming.md
+++ b/docs/core/deploying/trimming/prepare-libraries-for-trimming.md
@@ -137,7 +137,7 @@ In this case, the trim analysis keeps public methods of <xref:System.Tuple>, and
 * When code is incompatible with trimming, annotate it with `RequiresUnreferencedCode` and propagate this annotation to callers until the relevant public APIs are annotated.
 * Avoid using code that uses reflection in a way not understood by the static analysis. For example, reflection in static constructors should be avoided. Using statically unanalyzable reflection in static constructors result in the warning propagating to all members of the class.
 * Avoid annotating virtual methods or interface methods. Annotating virtual or interface methods requires all overrides to have matching annotations.
-* If an API is mostly trim-incompatible, alternative coding approaches to the API might need to be considered. A common example is reflection-based serializers. In these cases, consider adopting other technology like source generators to produce code that is more easily statically analyzed. For example, see [How to use source generation in System.Text.Json](../../../standard/serialization/system-text-json/source-generation.md)
+* If an API is mostly trim-incompatible, alternative coding approaches to the API might need to be considered. A common example is reflection-based serializers. In these cases, consider adopting other technology like source generators to produce code that is more easily statically analyzed. For example, see [How to use source generation in System.Text.Json](../../../standard/serialization/system-text-json/source-generation.md).
 
 ## Resolve warnings for non-analyzable patterns
 
diff --git a/docs/core/deploying/trimming/trim-warnings/il2016.md b/docs/core/deploying/trimming/trim-warnings/il2016.md
index f5d356d616a0e..9eb094a5c9b30 100644
--- a/docs/core/deploying/trimming/trim-warnings/il2016.md
+++ b/docs/core/deploying/trimming/trim-warnings/il2016.md
@@ -14,9 +14,7 @@ Could not find event on type.
 
 ## Rule description
 
-An event specified in an [XML file for the trimmer](https://github.com/dotnet/runtime/blob/main/docs/tools/illink/data-formats.md)
-file could not be found in the type matching the `fullname` argument that was passed to
-the parent of the `event` element.
+An event specified in an [XML file for the trimmer](https://github.com/dotnet/runtime/blob/main/docs/tools/illink/data-formats.md) file could not be found in the type matching the `fullname` argument that was passed to the parent of the `event` element.
 
 ## Example
 
diff --git a/docs/core/deploying/trimming/trim-warnings/il2017.md b/docs/core/deploying/trimming/trim-warnings/il2017.md
index 4a3c866a72bc5..f4665a398e75d 100644
--- a/docs/core/deploying/trimming/trim-warnings/il2017.md
+++ b/docs/core/deploying/trimming/trim-warnings/il2017.md
@@ -14,9 +14,7 @@ Could not find property on type.
 
 ## Rule description
 
-A property specified in an [XML file for the trimmer](https://github.com/dotnet/runtime/blob/main/docs/tools/illink/data-formats.md)
-file could not be found in the type matching the `fullname` argument that was passed to
-the parent of the `property` element.
+A property specified in an [XML file for the trimmer](https://github.com/dotnet/runtime/blob/main/docs/tools/illink/data-formats.md) file could not be found in the type matching the `fullname` argument that was passed to the parent of the `property` element.
 
 ## Example
 
diff --git a/docs/core/diagnostics/built-in-metrics.md b/docs/core/diagnostics/built-in-metrics.md
index 2ec47c0259c92..821d124d724b3 100644
--- a/docs/core/diagnostics/built-in-metrics.md
+++ b/docs/core/diagnostics/built-in-metrics.md
@@ -18,5 +18,5 @@ This is a reference for [metrics](metrics.md) built-in for .NET, produced using
 
 ## Older metric APIs
 
-For built-in metrics produced by [alternative metric APIs](compare-metric-apis.md)
+For built-in metrics produced by [alternative metric APIs](compare-metric-apis.md),
 see the [EventCounters reference](available-counters.md) and [Windows Performance Counter reference](../../framework/debug-trace-profile/performance-counters.md).
diff --git a/docs/core/diagnostics/compare-metric-apis.md b/docs/core/diagnostics/compare-metric-apis.md
index d49e3d377c6c9..e6b7fabd9d29a 100644
--- a/docs/core/diagnostics/compare-metric-apis.md
+++ b/docs/core/diagnostics/compare-metric-apis.md
@@ -30,8 +30,7 @@ Although this API was designed to work well with OpenTelemetry and its growing e
 ### PerformanceCounter
 
 <xref:System.Diagnostics.PerformanceCounter?displayProperty=nameWithType> APIs are the oldest .NET metric APIs. They're only supported on Windows and provide
-a managed wrapper for Windows OS [Performance Counter](/windows/win32/perfctrs/performance-counters-portal)
-technology. They are available in all supported versions of .NET.
+a managed wrapper for Windows OS [Performance Counter](/windows/win32/perfctrs/performance-counters-portal) technology. They are available in all supported versions of .NET.
 
 These APIs are provided primarily for compatibility; the .NET team
 considers this a stable area that's unlikely to receive further improvement aside from bug fixes. These APIs are not suggested
diff --git a/docs/core/diagnostics/debug-stackoverflow.md b/docs/core/diagnostics/debug-stackoverflow.md
index d672eb694cba4..7633a01142bda 100644
--- a/docs/core/diagnostics/debug-stackoverflow.md
+++ b/docs/core/diagnostics/debug-stackoverflow.md
@@ -49,7 +49,7 @@ Often just seeing this callstack on the console above is enough to identify the
 
 This example creates a core dump when the StackOverflowException occurs, then loads the dump into [lldb](https://lldb.llvm.org/) (a common Linux command-line debugger) and debugs it.
 
-1. Run the app with it configured to collect a dump on crash
+1. Run the app with it configured to collect a dump on crash.
 
     ````
     > export DOTNET_DbgEnableMiniDump=1
@@ -61,7 +61,7 @@ This example creates a core dump when the StackOverflowException occurs, then lo
 
    [!INCLUDE [complus-prefix](../../../includes/complus-prefix.md)]
 
-2. Install the SOS extension using [dotnet-sos](dotnet-sos.md)
+2. Install the SOS extension using [dotnet-sos](dotnet-sos.md).
 
     ````
     dotnet-sos install
@@ -85,7 +85,7 @@ This example creates a core dump when the StackOverflowException occurs, then lo
     ...
     ````
 
-4. The top frame `0x00007f59b40900cc` is repeated several times. Use the [SOS](sos-debugging-extension.md) `ip2md` command to figure out what managed method is located at the `0x00007f59b40900cc` address
+4. The top frame `0x00007f59b40900cc` is repeated several times. Use the [SOS](sos-debugging-extension.md) `ip2md` command to figure out what managed method is located at the `0x00007f59b40900cc` address.
 
     ````
     (lldb) ip2md 0x00007f59b40900cc
@@ -120,7 +120,7 @@ The callstack debugger window also shows the stack.
 
 You can use all the normal Visual Studio debugger features to investigate each frame on the callstack, its source code, and the value of local variables.
 
-## See Also
+## See also
 
 * [An introduction to dumps in .NET](dumps.md)
 * [Debug Linux dumps](debug-linux-dumps.md)
diff --git a/docs/core/diagnostics/event-counters.md b/docs/core/diagnostics/event-counters.md
index 38996eee4d747..995dd23946169 100644
--- a/docs/core/diagnostics/event-counters.md
+++ b/docs/core/diagnostics/event-counters.md
@@ -13,7 +13,7 @@ ms.date: 08/27/2024
 
 EventCounters are .NET APIs used for lightweight, cross-platform, and near real-time performance metric collection. EventCounters were added as a cross-platform alternative to the "performance counters" of .NET Framework on Windows. In this article, you'll learn what EventCounters are, how to implement them, and how to consume them.
 
-The .NET runtime and a few .NET libraries publish basic diagnostics information using EventCounters starting in .NET Core 3.0. Apart from the EventCounters that are provided by the .NET runtime, you may choose to implement your own EventCounters. EventCounters can be used to track various metrics. Learn more about them in [well-known EventCounters in .NET](available-counters.md)
+The .NET runtime and a few .NET libraries publish basic diagnostics information using EventCounters starting in .NET Core 3.0. Apart from the EventCounters that are provided by the .NET runtime, you may choose to implement your own EventCounters. EventCounters can be used to track various metrics. Learn more about them in [well-known EventCounters in .NET](available-counters.md).
 
 EventCounters live as a part of an <xref:System.Diagnostics.Tracing.EventSource>, and are automatically pushed to listener tools on a regular basis. Like all other events on an <xref:System.Diagnostics.Tracing.EventSource>, they can be consumed both in-proc and out-of-proc via <xref:System.Diagnostics.Tracing.EventListener> and [EventPipe](./eventpipe.md). This article focuses on the cross-platform capabilities of EventCounters, and intentionally excludes PerfView and ETW (Event Tracing for Windows) - although both can be used with EventCounters.
 
@@ -157,15 +157,15 @@ _requestRateCounter = new IncrementingPollingCounter("request-rate", this, () =>
 There are two primary ways of consuming EventCounters: in-proc and out-of-proc. The consumption of EventCounters can be distinguished into three layers of various consuming technologies.
 
 - Transporting events in a raw stream via ETW or EventPipe:
-  
+
   ETW APIs come with the Windows OS, and EventPipe is accessible as a [.NET API](https://github.com/dotnet/diagnostics/blob/main/documentation/design-docs/diagnostics-client-library.md#1-attaching-to-a-process-and-dumping-out-all-the-runtime-gc-events-in-real-time-to-the-console), or the diagnostic [IPC protocol](https://github.com/dotnet/diagnostics/blob/main/documentation/design-docs/ipc-protocol.md).
 
 - Decoding the binary event stream into events:
-  
+
   The [TraceEvent library](https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.TraceEvent) handles both ETW and EventPipe stream formats.
 
 - Command-line and GUI tools:
-  
+
   Tools like PerfView (ETW or EventPipe), dotnet-counters (EventPipe only), and dotnet-monitor (EventPipe only).
 
 ### Consume out-of-proc
diff --git a/docs/core/diagnostics/eventsource-getting-started.md b/docs/core/diagnostics/eventsource-getting-started.md
index 7736489be78f2..dbea122e3bbdd 100644
--- a/docs/core/diagnostics/eventsource-getting-started.md
+++ b/docs/core/diagnostics/eventsource-getting-started.md
@@ -83,7 +83,7 @@ This demo shows an [EventPipe](./eventpipe.md) example for .NET Core apps. To le
 technology built into the .NET Core runtime to give .NET developers trace collection tools and a portable compact trace
 format (*.nettrace files). [dotnet-trace](./dotnet-trace.md) is a command-line tool that collects EventPipe traces.
 
-1. Download and Install [dotnet-trace](./dotnet-trace.md#install)
+1. Download and Install [dotnet-trace](./dotnet-trace.md#install).
 1. Build the console app above. This demo assumes the app is named EventSourceDemo.exe and it is in the current directory. At the command-line run:
 
 ```dotnetcli
diff --git a/docs/core/diagnostics/eventsource-instrumentation.md b/docs/core/diagnostics/eventsource-instrumentation.md
index b0d34a6f1aae5..600255eae3d00 100644
--- a/docs/core/diagnostics/eventsource-instrumentation.md
+++ b/docs/core/diagnostics/eventsource-instrumentation.md
@@ -184,14 +184,13 @@ authoring errors.
 4. When debugging, that same error string will also be logged using Debug.WriteLine() and show up in the debug
 output window.
 5. EventSource internally throws and then catches exceptions when errors occur. To observe when these exceptions are occurring, enable first chance exceptions
-in a debugger, or use event tracing with the .NET runtime's [Exception events](../../fundamentals/diagnostics/runtime-exception-events.md)
-enabled.
+in a debugger, or use event tracing with the .NET runtime's [Exception events](../../fundamentals/diagnostics/runtime-exception-events.md) enabled.
 
 ## Advanced customizations
 
 ### Setting OpCodes and Tasks
 
-ETW has concepts of [Tasks and OpCodes](/windows/win32/wes/defining-tasks-and-opcodes)
+ETW has concepts of [Tasks and OpCodes](/windows/win32/wes/defining-tasks-and-opcodes),
 which are further mechanisms for tagging and filtering events. You can associate events with specific tasks and opcodes
 using the <xref:System.Diagnostics.Tracing.EventAttribute.Task%2A> and
 <xref:System.Diagnostics.Tracing.EventAttribute.Opcode%2A> properties. Here's an example:
diff --git a/docs/core/docker/container-images.md b/docs/core/docker/container-images.md
index 07304d6648ab6..27fab825ecca9 100644
--- a/docs/core/docker/container-images.md
+++ b/docs/core/docker/container-images.md
@@ -27,7 +27,7 @@ The following images are focused on resulting in the smallest possible image siz
 - Mariner distroless
 - Ubuntu chiseled
 
-These images are smaller, as they don't include globalization dependencies such as, ICU, or tzdata. These images only work with apps that are configured for globalization invariant mode. To configure an app for invariant globalization, add the following property to the project file:
+These images are smaller, as they don't include globalization dependencies such as ICU or tzdata. These images only work with apps that are configured for globalization invariant mode. To configure an app for invariant globalization, add the following property to the project file:
 
 ```xml
 <PropertyGroup>
@@ -83,7 +83,7 @@ AOT images are published for:
 - Mariner
 - Ubuntu
 
-For more information, see [Native AOT deployment](../deploying/native-aot/index.md)
+For more information, see [Native AOT deployment](../deploying/native-aot/index.md).
 
 ## Docker hub repositories
 
diff --git a/docs/core/extensions/custom-logging-provider.md b/docs/core/extensions/custom-logging-provider.md
index 8f926ef84a18c..287f1d496e0cd 100644
--- a/docs/core/extensions/custom-logging-provider.md
+++ b/docs/core/extensions/custom-logging-provider.md
@@ -12,7 +12,7 @@ ms.topic: how-to
 There are many [logging providers](logging-providers.md) available for common logging needs. You may need to implement a custom <xref:Microsoft.Extensions.Logging.ILoggerProvider> when one of the available providers doesn't suit your application needs. In this article, you'll learn how to implement a custom logging provider that can be used to colorize logs in the console.
 
 > [!TIP]
-> The custom logging provider example source code is available in the **Docs Github repo**. For more information, see [GitHub: .NET Docs - Console Custom Logging](https://github.com/dotnet/docs/tree/main/docs/core/extensions/snippets/configuration/console-custom-logging).
+> The custom logging provider example source code is available in the **Docs GitHub repo**. For more information, see [GitHub: .NET Docs - Console Custom Logging](https://github.com/dotnet/docs/tree/main/docs/core/extensions/snippets/configuration/console-custom-logging).
 
 ### Sample custom logger configuration
 
diff --git a/docs/core/extensions/logging.md b/docs/core/extensions/logging.md
index eb0d448e99366..3a7bfd0d64f5b 100644
--- a/docs/core/extensions/logging.md
+++ b/docs/core/extensions/logging.md
@@ -93,7 +93,7 @@ The preceding example:
 
 ## Configure logging
 
-Logging configuration is set in code or via external sources, such as, config files and environment variables. Using external configuration is beneficial when possible because it can be changed without rebuilding the application. However, some tasks, such as setting logging providers, can only be configured from code.
+Logging configuration is set in code or via external sources, such as config files and environment variables. Using external configuration is beneficial when possible because it can be changed without rebuilding the application. However, some tasks, such as setting logging providers, can only be configured from code.
 
 ### Configure logging without code
 
@@ -141,7 +141,7 @@ Any logs below the minimum level are ***not***:
 
 To suppress all logs, specify [LogLevel.None](xref:Microsoft.Extensions.Logging.LogLevel). `LogLevel.None` has a value of 6, which is higher than `LogLevel.Critical` (5).
 
-If a provider supports [log scopes](#log-scopes), `IncludeScopes` indicates whether they're enabled. For more information, see [log scopes](#log-scopes)
+If a provider supports [log scopes](#log-scopes), `IncludeScopes` indicates whether they're enabled. For more information, see [log scopes](#log-scopes).
 
 The following *appsettings.json* file contains settings for all of the built-in providers:
 
diff --git a/docs/core/extensions/options.md b/docs/core/extensions/options.md
index bfdd5e7d305d4..71f32116ed1b8 100644
--- a/docs/core/extensions/options.md
+++ b/docs/core/extensions/options.md
@@ -92,7 +92,7 @@ In the preceding code, changes to the JSON configuration file after the app has
 
 - Is useful in scenarios where options should be recomputed on every injection resolution, in [scoped or transient lifetimes](dependency-injection.md#service-lifetimes). For more information, see [Use IOptionsSnapshot to read updated data](#use-ioptionssnapshot-to-read-updated-data).
 - Is registered as [Scoped](dependency-injection.md#scoped) and therefore cannot be injected into a Singleton service.
-- Supports [named options](#named-options-support-using-iconfigurenamedoptions)
+- Supports [named options](#named-options-support-using-iconfigurenamedoptions).
 
 <xref:Microsoft.Extensions.Options.IOptionsMonitor%601>:
 
diff --git a/docs/core/install/windows.md b/docs/core/install/windows.md
index 06ec609841b88..4cb70f77314d3 100644
--- a/docs/core/install/windows.md
+++ b/docs/core/install/windows.md
@@ -395,7 +395,7 @@ Most likely you installed both the x86 (32-bit) and x64 (64-bit) versions of the
     C:\Program Files\dotnet\dotnet.exe
     ```
 
-    If it's correct and the _Program Files\\_ is first, you don't have the problem this section is discussing and you should create a [.NET help request issue on GitHub](https://github.com/dotnet/core/issues/new?assignees=&labels=&template=01_bug_report.md&title=)
+    If it's correct and the _Program Files\\_ is first, you don't have the problem this section is discussing and you should create a [.NET help request issue on GitHub](https://github.com/dotnet/core/issues/new?assignees=&labels=&template=01_bug_report.md&title=).
 
 01. Press the Windows button and type "Edit the system environment variables" into search. Select **Edit the system environment variables**.
 
diff --git a/docs/core/porting/modernize.md b/docs/core/porting/modernize.md
index 9a55615c5050f..3620ca5f06f03 100644
--- a/docs/core/porting/modernize.md
+++ b/docs/core/porting/modernize.md
@@ -17,7 +17,7 @@ When upgrading a .NET Framework app, you'll most likely have some incompatibilit
 
 ### Windows Compatibility Pack
 
-If after migration you have some dependencies on .NET Framework APIs that are not supported on your new version of .NET, you might find them in the [`Microsoft.Windows.Compatibility` NuGet package](https://www.nuget.org/packages/Microsoft.Windows.Compatibility). It adds around 20,000 APIs to your .NET project, significantly increasing the API set available to your project. These APIs include Windows-only APIs such as those related to Windows Management Instrumentation (WMI) and the Windows EventLog. For more information, see [Use the Windows Compatibility Pack to port code to .NET](windows-compat-pack.md)
+If after migration you have some dependencies on .NET Framework APIs that are not supported on your new version of .NET, you might find them in the [`Microsoft.Windows.Compatibility` NuGet package](https://www.nuget.org/packages/Microsoft.Windows.Compatibility). It adds around 20,000 APIs to your .NET project, significantly increasing the API set available to your project. These APIs include Windows-only APIs such as those related to Windows Management Instrumentation (WMI) and the Windows EventLog. For more information, see [Use the Windows Compatibility Pack to port code to .NET](windows-compat-pack.md).
 
 ## Web browser control
 
diff --git a/docs/core/porting/net-framework-tech-unavailable.md b/docs/core/porting/net-framework-tech-unavailable.md
index e0cb23113323a..f230007fa895f 100644
--- a/docs/core/porting/net-framework-tech-unavailable.md
+++ b/docs/core/porting/net-framework-tech-unavailable.md
@@ -61,7 +61,7 @@ Windows Workflow Foundation (WF) is not supported in .NET 6+. For an alternative
 
 In .NET 9, a `PersistedAssemblyBuilder` was implemented and the <xref:System.Reflection.Emit.AssemblyBuilder.Save%2A?displayProperty=nameWithType> method was added back to the reflection emit library. To learn more about how to use this API, see [System.Reflection.Emit.PersistedAssemblyBuilder class](../../fundamentals/runtime-libraries/system-reflection-emit-persistedassemblybuilder.md).
 
-For more information about the different AssemblyBuilder implementations in .NET, see [System.Reflection.Emit.AssemblyBuilder class](../../fundamentals/runtime-libraries/system-reflection-emit-assemblybuilder.md)
+For more information about the different AssemblyBuilder implementations in .NET, see [System.Reflection.Emit.AssemblyBuilder class](../../fundamentals/runtime-libraries/system-reflection-emit-assemblybuilder.md).
 
 ## Loading multi-module assemblies
 
diff --git a/docs/core/porting/upgrade-assistant-how-to-analyze.md b/docs/core/porting/upgrade-assistant-how-to-analyze.md
index 2a1fd456b75c3..afc1f1c76b59b 100644
--- a/docs/core/porting/upgrade-assistant-how-to-analyze.md
+++ b/docs/core/porting/upgrade-assistant-how-to-analyze.md
@@ -16,8 +16,8 @@ This article teaches you how to perform code analysis on your projects with .NET
 
 ## Prerequisites
 
-- For Visual Studio, see [Install .NET Upgrade Assistant - Visual Studio extension](upgrade-assistant-install.md#visual-studio-extension)
-- For the .NET Global Tool, see [Install .NET Upgrade Assistant - .NET Global Tool](upgrade-assistant-install.md#net-global-tool)
+- For Visual Studio, see [Install .NET Upgrade Assistant - Visual Studio extension](upgrade-assistant-install.md#visual-studio-extension).
+- For the .NET Global Tool, see [Install .NET Upgrade Assistant - .NET Global Tool](upgrade-assistant-install.md#net-global-tool).
 
 ## Create a report in Visual Studio
 
diff --git a/docs/core/porting/upgrade-assistant-how-to-upgrade.md b/docs/core/porting/upgrade-assistant-how-to-upgrade.md
index 1560f560b3f05..6d266124364ba 100644
--- a/docs/core/porting/upgrade-assistant-how-to-upgrade.md
+++ b/docs/core/porting/upgrade-assistant-how-to-upgrade.md
@@ -18,8 +18,8 @@ Some project types have specific guidance on upgrading. For more information, se
 
 ## Prerequisites
 
-- For Visual Studio, see [Install .NET Upgrade Assistant - Visual Studio extension](upgrade-assistant-install.md#visual-studio-extension)
-- For the .NET Global Tool, see [Install .NET Upgrade Assistant - .NET Global Tool](upgrade-assistant-install.md#net-global-tool)
+- For Visual Studio, see [Install .NET Upgrade Assistant - Visual Studio extension](upgrade-assistant-install.md#visual-studio-extension).
+- For the .NET Global Tool, see [Install .NET Upgrade Assistant - .NET Global Tool](upgrade-assistant-install.md#net-global-tool).
 
 ## Upgrade a project in Visual Studio
 
diff --git a/docs/core/porting/upgrade-assistant-install.md b/docs/core/porting/upgrade-assistant-install.md
index a4c04422e2e20..1d1085c5b8e36 100644
--- a/docs/core/porting/upgrade-assistant-install.md
+++ b/docs/core/porting/upgrade-assistant-install.md
@@ -8,7 +8,7 @@ ms.date: 10/08/2024
 
 #customer intent: As a developer, I want to install .NET Upgrade Assistant so that I can upgrade my projects.
 
----   
+---
 
 # Install .NET Upgrade Assistant
 
@@ -33,7 +33,7 @@ If you want the streamlined experience of opening a project in Visual Studio and
 The following steps install the Visual Studio extension.
 
 > [!TIP]
-> As an alternative to using the **Manage Extensions** feature of Visual Studio, you can download and run the extensions installer from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant)
+> As an alternative to using the **Manage Extensions** feature of Visual Studio, you can download and run the extensions installer from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant).
 
 01. Open Visual Studio.
 
diff --git a/docs/core/project-sdk/overview.md b/docs/core/project-sdk/overview.md
index a8f0f69a65182..f686945ee8d8d 100644
--- a/docs/core/project-sdk/overview.md
+++ b/docs/core/project-sdk/overview.md
@@ -53,7 +53,7 @@ The `Project/Sdk` attribute and `Sdk` element enable additive SDKs. Consider the
 </Project>
 ```
 
-In the preceding project file, both SDKs are used to resolve dependencies in an additive nature. For more information, see [.NET Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk)
+In the preceding project file, both SDKs are used to resolve dependencies in an additive nature. For more information, see [.NET Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk).
 
 To specify an SDK that comes from NuGet, include the version at the end of the name, or specify the name and version in the *global.json* file.
 
diff --git a/docs/core/testing/unit-testing-platform-architecture-extensions.md b/docs/core/testing/unit-testing-platform-architecture-extensions.md
index 59f3bba4b8014..492bea52f495a 100644
--- a/docs/core/testing/unit-testing-platform-architecture-extensions.md
+++ b/docs/core/testing/unit-testing-platform-architecture-extensions.md
@@ -453,7 +453,7 @@ The third attribute is `Properties`, which is a `PropertyBag` type. As demonstra
 
 ***The testing platform identifies specific properties added to a `TestNode.Properties` to determine whether a test has passed, failed, or been skipped.***
 
-You can find the current list of available properties with the relative description in the section [TestNodeUpdateMessage.TestNode](#the-testnodeupdatemessage-data)
+You can find the current list of available properties with the relative description in the section [TestNodeUpdateMessage.TestNode](#the-testnodeupdatemessage-data).
 
 The `PropertyBag` type is typically accessible in every `IData` and is utilized to store miscellaneous properties that can be queried by the platform and extensions. This mechanism allows us to enhance the platform with new information without introducing breaking changes. If a component recognizes the property, it can query it; otherwise, it will disregard it.
 
diff --git a/docs/core/testing/unit-testing-platform-intro.md b/docs/core/testing/unit-testing-platform-intro.md
index ac30161b143f0..2179a6e2726cb 100644
--- a/docs/core/testing/unit-testing-platform-intro.md
+++ b/docs/core/testing/unit-testing-platform-intro.md
@@ -41,7 +41,7 @@ The main driving factors for the evolution of the new testing platform are detai
 * MSTest. In MSTest, the support of `Microsoft.Testing.Platform` is done via [MSTest runner](unit-testing-mstest-runner-intro.md).
 * NUnit. In NUnit, the support of `Microsoft.Testing.Platform` is done via [NUnit runner](unit-testing-nunit-runner-intro.md).
 * xUnit.net: In xUnit.net, the support of `Microsoft.Testing.Platform` is done via [xUnit.net runner](https://xunit.net/docs/getting-started/v3/microsoft-testing-platform).
-* TUnit: entirely constructed on top of the `Microsoft.Testing.Platform`, for more information, see [TUnit documentation](https://thomhurst.github.io/TUnit/)
+* TUnit: entirely constructed on top of the `Microsoft.Testing.Platform`, for more information, see [TUnit documentation](https://thomhurst.github.io/TUnit/).
 
 ## Run and debug tests
 
diff --git a/docs/core/tools/dotnet-environment-variables.md b/docs/core/tools/dotnet-environment-variables.md
index a08322082b37e..6b785293e23e6 100644
--- a/docs/core/tools/dotnet-environment-variables.md
+++ b/docs/core/tools/dotnet-environment-variables.md
@@ -322,7 +322,7 @@ Determines roll forward behavior. For more information, see [the `--roll-forward
 
 If set to `1` (enabled), enables rolling forward to a pre-release version from a release version. By default (`0` - disabled), when a release version of .NET runtime is requested, roll-forward will only consider installed release versions.
 
-For more information, see [the `--roll-forward` option for the `dotnet` command](dotnet.md#rollforward)
+For more information, see [the `--roll-forward` option for the `dotnet` command](dotnet.md#rollforward).
 
 ### `DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX`
 
diff --git a/docs/core/tools/dotnet-new-details.md b/docs/core/tools/dotnet-new-details.md
index 7436d9a1f3432..a8ebef29ae490 100644
--- a/docs/core/tools/dotnet-new-details.md
+++ b/docs/core/tools/dotnet-new-details.md
@@ -34,7 +34,7 @@ If the package is installed locally or is found on the official NuGet website, i
 - **`--add-source|--nuget-source <SOURCE>`**
 
   By default, `dotnet new details` uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from. If `--nuget-source` is specified, the source is added to the list of sources to be checked.
-  To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior)
+  To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior).
 
 [!INCLUDE [interactive](../../../includes/cli-interactive.md)]
 
diff --git a/docs/core/tools/dotnet-new-install.md b/docs/core/tools/dotnet-new-install.md
index 2aa9bc159a1af..bcdea99c306d2 100644
--- a/docs/core/tools/dotnet-new-install.md
+++ b/docs/core/tools/dotnet-new-install.md
@@ -14,7 +14,7 @@ ms.date: 04/15/2022
 ## Synopsis
 
 ```dotnetcli
-dotnet new install <PATH|NUGET_ID>  [--interactive] [--add-source|--nuget-source <SOURCE>] [--force] 
+dotnet new install <PATH|NUGET_ID>  [--interactive] [--add-source|--nuget-source <SOURCE>] [--force]
     [-d|--diagnostics] [--verbosity <LEVEL>] [-h|--help]
 ```
 
@@ -52,9 +52,9 @@ Starting with .NET SDK 6.0.100, installed template packages are available in lat
 ## Options
 
 - **`--add-source|--nuget-source <SOURCE>`**
-  
-  By default, `dotnet new install` uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from. If `--nuget-source` is specified, the source will be added to the list of sources to be checked.  
-  To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior)
+
+  By default, `dotnet new install` uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from. If `--nuget-source` is specified, the source will be added to the list of sources to be checked.
+  To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior).
 
   > [!NOTE]
   > Following NuGet's [Https Everywhere](https://devblogs.microsoft.com/nuget/https-everywhere/) initiative, `dotnet new` is phasing out `http` feeds. If an `http` feed is passed, it isn't queried for packages and a warning is displayed. The `--force` option can be used to override this behavior if necessary.
diff --git a/docs/core/tools/dotnet-tool-list.md b/docs/core/tools/dotnet-tool-list.md
index b3176947efe80..de454488c1973 100644
--- a/docs/core/tools/dotnet-tool-list.md
+++ b/docs/core/tools/dotnet-tool-list.md
@@ -78,11 +78,11 @@ The `dotnet tool list` command provides a way for you to list .NET global, tool-
 
 - **`dotnet tool list -g dotnetsay`**
 
-  Lists the global tool with the package id [dotnetsay](https://www.nuget.org/packages/dotnetsay/)
+  Lists the global tool with the package ID [dotnetsay](https://www.nuget.org/packages/dotnetsay/)
 
 - **`dotnet tool list dotnetsay`**
 
-  Lists the local tool with the package id [dotnetsay](https://www.nuget.org/packages/dotnetsay/)
+  Lists the local tool with the package ID [dotnetsay](https://www.nuget.org/packages/dotnetsay/)
 
 ## See also
 
diff --git a/docs/core/tools/local-tools-how-to-use.md b/docs/core/tools/local-tools-how-to-use.md
index 7e1729deed1ba..6a05097d9f497 100644
--- a/docs/core/tools/local-tools-how-to-use.md
+++ b/docs/core/tools/local-tools-how-to-use.md
@@ -198,4 +198,4 @@ If you get an error message while following the tutorial, see [Troubleshoot .NET
 
 ## See also
 
-For more information, see [.NET tools](global-tools.md)
+For more information, see [.NET tools](global-tools.md).
diff --git a/docs/core/tools/sdk-errors/netsdk1079.md b/docs/core/tools/sdk-errors/netsdk1079.md
index ce4fbc6919e66..b0dbb14339dcd 100644
--- a/docs/core/tools/sdk-errors/netsdk1079.md
+++ b/docs/core/tools/sdk-errors/netsdk1079.md
@@ -18,4 +18,6 @@ You may receive this error message when:
 
 Remove the `PackageReference` for Microsoft.AspNetCore.All.  You may also need to add package references for packages that were referenced from Microsoft.AspNetCore.All but are not included in the ASP.NET Core shared framework.  These packages are listed here: [Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App](/aspnet/core/fundamentals/metapackage#migrating-from-microsoftaspnetcoreall-to-microsoftaspnetcoreapp).
 
-See also [Migrate from ASP.NET Core 2.2 to 3.0](/aspnet/core/migration/22-to-30)
+## See also
+
+- [Migrate from ASP.NET Core 2.2 to 3.0](/aspnet/core/migration/22-to-30).
diff --git a/docs/core/tools/troubleshoot-usage-issues.md b/docs/core/tools/troubleshoot-usage-issues.md
index 4afd9ea7e1d0d..809852ddf71f4 100644
--- a/docs/core/tools/troubleshoot-usage-issues.md
+++ b/docs/core/tools/troubleshoot-usage-issues.md
@@ -199,7 +199,7 @@ Most likely you've specified an alternative NuGet feed, and that feed requires a
   </configuration>
   ```
 
-  For more information, see [nuget.config reference](/nuget/reference/nuget-config-file)
+  For more information, see [nuget.config reference](/nuget/reference/nuget-config-file).
 
 - Add the required credentials to the config file.
 
diff --git a/docs/csharp/advanced-topics/reflection-and-attributes/index.md b/docs/csharp/advanced-topics/reflection-and-attributes/index.md
index f022192286501..fe48ca175dfff 100644
--- a/docs/csharp/advanced-topics/reflection-and-attributes/index.md
+++ b/docs/csharp/advanced-topics/reflection-and-attributes/index.md
@@ -69,7 +69,7 @@ Many attributes have parameters, which can be positional, unnamed, or named. Any
 
 The first parameter, the DLL name, is positional and always comes first; the others are named. In this case, both named parameters default to false, so they can be omitted. Positional parameters correspond to the parameters of the attribute constructor. Named or optional parameters correspond to either properties or fields of the attribute. Refer to the individual attribute's documentation for information on default parameter values.
 
-For more information on allowed parameter types, see the [Attributes](~/_csharpstandard/standard/attributes.md#2224-attribute-parameter-types) section of the [C# language specification](~/_csharpstandard/standard/README.md)
+For more information on allowed parameter types, see the [Attributes](~/_csharpstandard/standard/attributes.md#2224-attribute-parameter-types) section of the [C# language specification](~/_csharpstandard/standard/README.md).
 
 ### Attribute targets
 
diff --git a/docs/csharp/language-reference/builtin-types/struct.md b/docs/csharp/language-reference/builtin-types/struct.md
index 7ce46f3592ded..dcdab20680ff6 100644
--- a/docs/csharp/language-reference/builtin-types/struct.md
+++ b/docs/csharp/language-reference/builtin-types/struct.md
@@ -27,7 +27,7 @@ Because structure types have value semantics, we recommend you define *immutable
 
 You use the `readonly` modifier to declare that a structure type is immutable. All data members of a `readonly` struct must be read-only as follows:
 
-- Any field declaration must have the [`readonly` modifier](../keywords/readonly.md)
+- Any field declaration must have the [`readonly` modifier](../keywords/readonly.md).
 - Any property, including automatically implemented ones, must be read-only or [`init` only](../keywords/init.md). Init-only setters are only available from [C# version 9 onwards](../../whats-new/csharp-version-history.md).
 
 That guarantees that no member of a `readonly` struct modifies the state of the struct. That means that other instance members except constructors are implicitly [`readonly`](#readonly-instance-members).
@@ -110,7 +110,7 @@ But it can be any reference type, or any value type:
 
 You can use inline arrays with almost any C# data structure.
 
-Inline arrays are an advanced language feature. They're intended for high-performance scenarios where an inline, contiguous block of elements is faster than other alternative data structures. You can learn more about inline arrays from the [feature speclet](~/_csharplang/proposals/csharp-12.0/inline-arrays.md)
+Inline arrays are an advanced language feature. They're intended for high-performance scenarios where an inline, contiguous block of elements is faster than other alternative data structures. You can learn more about inline arrays from the [feature speclet](~/_csharplang/proposals/csharp-12.0/inline-arrays.md).
 
 ## Struct initialization and default values
 
diff --git a/docs/csharp/language-reference/keywords/interface.md b/docs/csharp/language-reference/keywords/interface.md
index 14a33f2e925d7..d33e6c95ce708 100644
--- a/docs/csharp/language-reference/keywords/interface.md
+++ b/docs/csharp/language-reference/keywords/interface.md
@@ -2,9 +2,9 @@
 description: "Use the `interface` keyword to define contracts that any implementing type must support. Interfaces provide the means to create common behavior among a set of unrelated types."
 title: "interface keyword"
 ms.date: 07/26/2024
-f1_keywords: 
+f1_keywords:
   - "interface_CSharpKeyword"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "interface keyword [C#]"
 ---
 # :::no-loc text="interface"::: (C# Reference)
@@ -87,7 +87,7 @@ The following example demonstrates interface implementation. In this example, th
 
 ## C# language specification
 
-For more information, see the [Interfaces](~/_csharpstandard/standard/interfaces.md) section of the [C# language specification](~/_csharpstandard/standard/README.md), the feature specification for [C# 8 - Default interface members](~/_csharplang/proposals/csharp-8.0/default-interface-methods.md), and the feature spec for [C# 11 - static abstract members in interfaces](~/_csharplang/proposals/csharp-11.0/static-abstracts-in-interfaces.md)
+For more information, see the [Interfaces](~/_csharpstandard/standard/interfaces.md) section of the [C# language specification](~/_csharpstandard/standard/README.md), the feature specification for [C# 8 - Default interface members](~/_csharplang/proposals/csharp-8.0/default-interface-methods.md), and the feature spec for [C# 11 - static abstract members in interfaces](~/_csharplang/proposals/csharp-11.0/static-abstracts-in-interfaces.md).
 
 ## See also
 
diff --git a/docs/csharp/language-reference/statements/yield.md b/docs/csharp/language-reference/statements/yield.md
index c387eb9d627d9..896fafe829175 100644
--- a/docs/csharp/language-reference/statements/yield.md
+++ b/docs/csharp/language-reference/statements/yield.md
@@ -2,10 +2,10 @@
 title: "yield statement - provide the next element in an iterator"
 description: "Use the yield statement in iterators to provide the next value or signal the end of an iteration"
 ms.date: 06/28/2024
-f1_keywords: 
+f1_keywords:
   - "yield"
   - "yield_CSharpKeyword"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "yield keyword [C#]"
 ---
 # yield statement - provide the next element
@@ -35,8 +35,8 @@ In the preceding examples, the return type of iterators is <xref:System.Collecti
 
 You can't use the `yield` statements in:
 
-- methods with [in](../keywords/method-parameters.md#in-parameter-modifier), [ref](../keywords/ref.md), or [out](../keywords/method-parameters.md#out-parameter-modifier) parameters
-- [lambda expressions](../operators/lambda-expressions.md) and [anonymous methods](../operators/delegate-operator.md)
+- methods with [in](../keywords/method-parameters.md#in-parameter-modifier), [ref](../keywords/ref.md), or [out](../keywords/method-parameters.md#out-parameter-modifier) parameters.
+- [lambda expressions](../operators/lambda-expressions.md) and [anonymous methods](../operators/delegate-operator.md).
 - [unsafe blocks](../keywords/unsafe.md). Before C# 13, `yield` was invalid in any method with an `unsafe` block. Beginning with C# 13, you can use `yield` in methods with `unsafe` blocks, but not in the `unsafe` block.
 - `yield return` and `yield break` can not be used in [catch](../statements/exception-handling-statements.md) and [finally](../statements/exception-handling-statements.md) blocks, or in [try](../statements/exception-handling-statements.md) blocks with a corresponding `catch` block. The `yield return` and `yield break` statements can be used in a `try` block with no `catch` blocks, only a `finally` block.
 
diff --git a/docs/csharp/programming-guide/classes-and-structs/named-and-optional-arguments.md b/docs/csharp/programming-guide/classes-and-structs/named-and-optional-arguments.md
index 7ffb8edcf9889..9316a2dc5187e 100644
--- a/docs/csharp/programming-guide/classes-and-structs/named-and-optional-arguments.md
+++ b/docs/csharp/programming-guide/classes-and-structs/named-and-optional-arguments.md
@@ -2,11 +2,11 @@
 title: "Named and Optional Arguments"
 description: Named arguments in C# specify arguments by name, not position. Optional arguments can be omitted.
 ms.date: 03/14/2024
-f1_keywords: 
+f1_keywords:
   - "namedParameter_CSharpKeyword"
   - "optionalParameter_CSharpKeyword"
   - "cs_namedParameter"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "parameters [C#], named"
   - "named arguments [C#]"
   - "arguments [C#], named"
@@ -26,7 +26,7 @@ Named and optional parameters enable you to supply arguments for selected parame
 
 ## Named arguments
 
-Named arguments free you from matching the order of arguments to the order of parameters in the parameter lists of called methods. The argument for each parameter can be specified by parameter name. For example, a function that prints order details (such as, seller name, order number & product name) can be called by sending arguments by position, in the order defined by the function.
+Named arguments free you from matching the order of arguments to the order of parameters in the parameter lists of called methods. The argument for each parameter can be specified by parameter name. For example, a function that prints order details (such as seller name, order number, and product name) can be called by sending arguments by position, in the order defined by the function.
 
 ```csharp
 PrintOrderDetails("Gift Shop", 31, "Red Mug");
@@ -40,7 +40,7 @@ PrintOrderDetails(productName: "Red Mug", sellerName: "Gift Shop", orderNum: 31)
 ```
 
 Named arguments also improve the readability of your code by identifying what each argument represents. In the example method below, the `sellerName` can't be null or white space. As both `sellerName` and `productName` are string types, instead of sending arguments by position, it makes sense to use named arguments to disambiguate the two and reduce confusion for anyone reading the code.
-  
+
 Named arguments, when used with positional arguments, are valid as long as
 
 - they're not followed by any positional arguments, or
@@ -64,7 +64,7 @@ PrintOrderDetails(productName: "Red Mug", 31, "Gift Shop");
 
 ### Example
 
-The following code implements the examples from this section along with some additional ones.  
+The following code implements the examples from this section along with some additional ones.
 
 :::code language="csharp" source="./snippets/NamedAndOptional/program.cs" id="Snippet1":::
 
@@ -74,7 +74,7 @@ The definition of a method, constructor, indexer, or delegate can specify its pa
 
 Each optional parameter has a default value as part of its definition. If no argument is sent for that parameter, the default value is used. A default value must be one of the following types of expressions:
 
-- a constant expression;  
+- a constant expression;
 - an expression of the form `new ValType()`, where `ValType` is a value type, such as an [enum](../../language-reference/builtin-types/enum.md) or a [struct](../../language-reference/builtin-types/struct.md);
 - an expression of the form [default(ValType)](../../language-reference/operators/default.md),  where `ValType` is a value type.
 
@@ -128,15 +128,15 @@ However, you can greatly simplify the call to `AutoFormat` by using named and op
 :::code language="csharp" source="./snippets/NamedAndOptional/namedandoptcom.cs" id="Snippet13":::
 
 For more information and examples, see [How to use named and optional arguments in Office programming](../../advanced-topics/interop/how-to-use-named-and-optional-arguments-in-office-programming.md) and [How to access Office interop objects by using C# features](../../advanced-topics/interop/how-to-access-office-interop-objects.md).
-  
+
 ## Overload resolution
 
 Use of named and optional arguments affects overload resolution in the following ways:
 
-- A method, indexer, or constructor is a candidate for execution if each of its parameters either is optional or corresponds, by name or by position, to a single argument in the calling statement, and that argument can be converted to the type of the parameter.  
+- A method, indexer, or constructor is a candidate for execution if each of its parameters either is optional or corresponds, by name or by position, to a single argument in the calling statement, and that argument can be converted to the type of the parameter.
 - If more than one candidate is found, overload resolution rules for preferred conversions are applied to the arguments that are explicitly specified. Omitted arguments for optional parameters are ignored.
 - If two candidates are judged to be equally good, preference goes to a candidate that doesn't have optional parameters for which arguments were omitted in the call. Overload resolution generally prefers candidates that have fewer parameters.
-  
+
 ## C# language specification
 
 [!INCLUDE[CSharplangspec](~/includes/csharplangspec-md.md)]
diff --git a/docs/devops/dotnet-cli-and-continuous-integration.md b/docs/devops/dotnet-cli-and-continuous-integration.md
index da0dc7d19dad2..79b9fff26aa52 100644
--- a/docs/devops/dotnet-cli-and-continuous-integration.md
+++ b/docs/devops/dotnet-cli-and-continuous-integration.md
@@ -33,7 +33,7 @@ The installer script is automated to run at the start of the build to fetch and
 
 ## CI setup examples
 
-This section describes a manual setup using a PowerShell or bash script, along with descriptions of software as a service (SaaS) CI solutions. The SaaS CI solutions covered are [Travis CI](https://travis-ci.org/), [AppVeyor](https://www.appveyor.com/), and [Azure Pipelines](/azure/devops/pipelines/index). For GitHub Actions, see [GitHub Actions and .NET](github-actions-overview.md)
+This section describes a manual setup using a PowerShell or bash script, along with descriptions of software as a service (SaaS) CI solutions. The SaaS CI solutions covered are [Travis CI](https://travis-ci.org/), [AppVeyor](https://www.appveyor.com/), and [Azure Pipelines](/azure/devops/pipelines/index). For GitHub Actions, see [GitHub Actions and .NET](github-actions-overview.md).
 
 ### Manual setup
 
diff --git a/docs/devops/github-actions-overview.md b/docs/devops/github-actions-overview.md
index 1466a30f547a5..bd9325f4a6116 100644
--- a/docs/devops/github-actions-overview.md
+++ b/docs/devops/github-actions-overview.md
@@ -26,7 +26,7 @@ For more information, see [Introduction to GitHub Actions](https://docs.github.c
 
 ### Custom GitHub Actions
 
-While there are plenty of GitHub Actions available in the [Marketplace](https://github.com/marketplace?type=actions), you may want to author your own. You can create GitHub Actions that run .NET applications. For more information, see [Tutorial: Create a GitHub Action with .NET](create-dotnet-github-action.md)
+While there are plenty of GitHub Actions available in the [Marketplace](https://github.com/marketplace?type=actions), you may want to author your own. You can create GitHub Actions that run .NET applications. For more information, see [Tutorial: Create a GitHub Action with .NET](create-dotnet-github-action.md).
 
 ## Workflow file
 
@@ -191,7 +191,7 @@ The .NET command-line interface (CLI) is a cross-platform toolchain for developi
 - [dotnet test](../core/tools/dotnet-test.md)
 - [dotnet publish](../core/tools/dotnet-publish.md)
 
-For more information, see [.NET CLI overview](../core/tools/index.md)
+For more information, see [.NET CLI overview](../core/tools/index.md).
 
 ## See also
 
diff --git a/docs/fsharp/tools/development-tools.md b/docs/fsharp/tools/development-tools.md
index 0c46c9b65914f..b219a7d22c7af 100644
--- a/docs/fsharp/tools/development-tools.md
+++ b/docs/fsharp/tools/development-tools.md
@@ -23,7 +23,7 @@ F# can be installed as part of [Visual Studio Code](https://code.visualstudio.co
 
 ### Other development environments
 
-Other IDEs are available for F#, see [F# Tools](https://dotnet.microsoft.com/languages/fsharp/tools)
+Other IDEs are available for F#. For more information, see [F# Tools](https://dotnet.microsoft.com/languages/fsharp/tools).
 
 ## Community Tools
 
diff --git a/docs/fundamentals/diagnostics/runtime-contention-events.md b/docs/fundamentals/diagnostics/runtime-contention-events.md
index 8489c458273a7..77e87293790f0 100644
--- a/docs/fundamentals/diagnostics/runtime-contention-events.md
+++ b/docs/fundamentals/diagnostics/runtime-contention-events.md
@@ -9,45 +9,45 @@ helpviewer_keywords:
 
 # .NET runtime contention events
 
-These runtime events capture information about monitor lock contentions such as with `Monitor.Enter` or the C# lock keyword. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+These runtime events capture information about monitor lock contentions such as with `Monitor.Enter` or the C# lock keyword. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## ContentionStart_V2 event
 
 This event is emitted at the start of a monitor lock contention.
 
-|Keyword for raising the event|Level|
-|-----------------------------------|-----------|
-|`ContentionKeyword` (0x4000)|Informational (4)|
+| Keyword for raising the event | Level             |
+|-------------------------------|-------------------|
+| `ContentionKeyword` (0x4000)  | Informational (4) |
 
  The following table shows event information.
 
-|Event|Event ID|Raised when|
-|-----------|--------------|-----------------|
-|`ContentionStart_V2`|81|A monitor lock contention starts.|
+| Event                | Event ID | Raised when                       |
+|----------------------|----------|-----------------------------------|
+| `ContentionStart_V2` | 81       | A monitor lock contention starts. |
 
-|Field name|Data type|Description|
-|----------------|---------------|-----------------|
-|`Flags`|`win:UInt8`|`0` for managed; `1` for native.|
-|`ClrInstanceID`|`win:UInt16`|Unique ID for the instance of CoreCLR.|
-|`LockObjectID`|`win:Pointer`|Address of the lock object.|
-|`LockOwnerThreadID`|`win:Pointer`|Address of the thread that owns the lock.|
+| Field name          | Data type     | Description                               |
+|---------------------|---------------|-------------------------------------------|
+| `Flags`             | `win:UInt8`   | `0` for managed; `1` for native.          |
+| `ClrInstanceID`     | `win:UInt16`  | Unique ID for the instance of CoreCLR.    |
+| `LockObjectID`      | `win:Pointer` | Address of the lock object.               |
+| `LockOwnerThreadID` | `win:Pointer` | Address of the thread that owns the lock. |
 
 ## ContentionStop_V1 event
 
 This event is emitted at the end of a monitor lock contention.
 
-|Keyword for raising the event|Level|
-|-----------------------------------|-----------|
-|`ContentionKeyword` (0x4000)|Informational (4)|
+| Keyword for raising the event | Level             |
+|-------------------------------|-------------------|
+| `ContentionKeyword` (0x4000)  | Informational (4) |
 
  The following table shows event information.
 
-|Event|Event ID|Raised when|
-|-----------|--------------|-----------------|
-|`ContentionStop_V1`|91|A monitor lock contention ends.|
+| Event               | Event ID | Raised when                     |
+|---------------------|----------|---------------------------------|
+| `ContentionStop_V1` | 91       | A monitor lock contention ends. |
 
-|Field name|Data type|Description|
-|----------------|---------------|-----------------|
-|`Flags`|`win:UInt8`|`0` for managed; `1` for native.|
-|`ClrInstanceID`|`win:UInt16`|Unique ID for the instance of CoreCLR.|
-|`DurationNs`|`win:Double`|Duration of the contention in nanoseconds.|
+| Field name      | Data type    | Description                                |
+|-----------------|--------------|--------------------------------------------|
+| `Flags`         | `win:UInt8`  | `0` for managed; `1` for native.           |
+| `ClrInstanceID` | `win:UInt16` | Unique ID for the instance of CoreCLR.     |
+| `DurationNs`    | `win:Double` | Duration of the contention in nanoseconds. |
diff --git a/docs/fundamentals/diagnostics/runtime-exception-events.md b/docs/fundamentals/diagnostics/runtime-exception-events.md
index 7aa31b1733a8e..78c5071f5bfb9 100644
--- a/docs/fundamentals/diagnostics/runtime-exception-events.md
+++ b/docs/fundamentals/diagnostics/runtime-exception-events.md
@@ -10,7 +10,7 @@ helpviewer_keywords:
 
 # .NET runtime exception events
 
-These runtime events capture information about exceptions that are thrown. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+These runtime events capture information about exceptions that are thrown. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## ExceptionThrown_V1 event
 
diff --git a/docs/fundamentals/diagnostics/runtime-garbage-collection-events.md b/docs/fundamentals/diagnostics/runtime-garbage-collection-events.md
index f29517bd03f00..4173ac3d84362 100644
--- a/docs/fundamentals/diagnostics/runtime-garbage-collection-events.md
+++ b/docs/fundamentals/diagnostics/runtime-garbage-collection-events.md
@@ -9,7 +9,7 @@ helpviewer_keywords:
 ---
 # .NET runtime garbage collection events
 
-The events described in this article collect information pertaining to garbage collection. They help in diagnostics and debugging, including determining how many times garbage collection was performed, how much memory was freed during garbage collection, etc. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information pertaining to garbage collection. They help in diagnostics and debugging, including determining how many times garbage collection was performed, how much memory was freed during garbage collection, etc. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## GCStart_V2 Event
 
diff --git a/docs/fundamentals/diagnostics/runtime-interop-events.md b/docs/fundamentals/diagnostics/runtime-interop-events.md
index 520eb92e8b0c1..0c82b0a2b0082 100644
--- a/docs/fundamentals/diagnostics/runtime-interop-events.md
+++ b/docs/fundamentals/diagnostics/runtime-interop-events.md
@@ -9,7 +9,7 @@ helpviewer_keywords:
 
 # .NET runtime interop events
 
-These runtime events capture information about Common Intermediate Language (CIL) stub generation. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+These runtime events capture information about Common Intermediate Language (CIL) stub generation. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## ILStubGenerated event
 
diff --git a/docs/fundamentals/diagnostics/runtime-loader-binder-events.md b/docs/fundamentals/diagnostics/runtime-loader-binder-events.md
index 2f2c762b9d1ce..2b1a6701973c9 100644
--- a/docs/fundamentals/diagnostics/runtime-loader-binder-events.md
+++ b/docs/fundamentals/diagnostics/runtime-loader-binder-events.md
@@ -10,7 +10,7 @@ helpviewer_keywords:
 
 # .NET runtime loader and binder events
 
-The events described in this article collect information relating to loading and unloading assemblies and modules. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information relating to loading and unloading assemblies and modules. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 |Keyword for raising the event|Event|Level|
 |-----------------------------------|-----------|-----------|
diff --git a/docs/fundamentals/diagnostics/runtime-method-events.md b/docs/fundamentals/diagnostics/runtime-method-events.md
index 4ffda848b241b..c9c84673832b5 100644
--- a/docs/fundamentals/diagnostics/runtime-method-events.md
+++ b/docs/fundamentals/diagnostics/runtime-method-events.md
@@ -9,7 +9,7 @@ helpviewer_keywords:
 
 # .NET runtime method events
 
-The events described in this article collect information that is specific to methods. The payload of these events is required for symbol resolution. In addition, these events provide helpful information such as methods that are loaded and unloaded. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information that is specific to methods. The payload of these events is required for symbol resolution. In addition, these events provide helpful information such as methods that are loaded and unloaded. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 All method events have a level of "Informational (4)". All method verbose events have a level of "Verbose (5)".
 
diff --git a/docs/fundamentals/diagnostics/runtime-thread-events.md b/docs/fundamentals/diagnostics/runtime-thread-events.md
index 2bc3e7ee9529c..9acc4e0092cdd 100644
--- a/docs/fundamentals/diagnostics/runtime-thread-events.md
+++ b/docs/fundamentals/diagnostics/runtime-thread-events.md
@@ -8,7 +8,7 @@ helpviewer_keywords:
 ---
 # .NET runtime thread pool events
 
-The events described in this article collect information about worker and I/O threads in the threadpool. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information about worker and I/O threads in the threadpool. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## IOThreadCreate_V1 event
 
diff --git a/docs/fundamentals/diagnostics/runtime-tiered-compilation-events.md b/docs/fundamentals/diagnostics/runtime-tiered-compilation-events.md
index c11e5a5507b11..4f8a369eb5b4e 100644
--- a/docs/fundamentals/diagnostics/runtime-tiered-compilation-events.md
+++ b/docs/fundamentals/diagnostics/runtime-tiered-compilation-events.md
@@ -8,7 +8,7 @@ helpviewer_keywords:
 ---
 # .NET runtime tiered compilation events
 
-The events described in this article collect information about tiered compilation. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information about tiered compilation. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## TieredCompilationSettings event
 
diff --git a/docs/fundamentals/diagnostics/runtime-type-events.md b/docs/fundamentals/diagnostics/runtime-type-events.md
index cf30ecb27699c..73eeb05212d49 100644
--- a/docs/fundamentals/diagnostics/runtime-type-events.md
+++ b/docs/fundamentals/diagnostics/runtime-type-events.md
@@ -9,7 +9,7 @@ helpviewer_keywords:
 
 # .NET runtime type events
 
-The events described in this article collect information relating to loading types. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md)
+The events described in this article collect information relating to loading types. For more information about how to use these events for diagnostic purposes, see [logging and tracing .NET applications](../../core/diagnostics/logging-tracing.md).
 
 ## TypeLoadStart Event
 
diff --git a/docs/orleans/deployment/consul-deployment.md b/docs/orleans/deployment/consul-deployment.md
index 2e150df7ef002..5590f99b6d61b 100644
--- a/docs/orleans/deployment/consul-deployment.md
+++ b/docs/orleans/deployment/consul-deployment.md
@@ -10,7 +10,7 @@ ms.date: 07/03/2024
 
 There's a detailed overview of Consul including comparisons with similar solutions [here](https://www.consul.io/intro/index.html).
 
-Consul is written in [Go](https://go.dev) and is [open source](https://github.com/hashicorp/consul); compiled downloads are available for [macOS X, FreeBSD, Linux, Solaris and Windows](https://www.consul.io/downloads.html)
+Consul is written in [Go](https://go.dev) and is [open source](https://github.com/hashicorp/consul); compiled downloads are available for [macOS X, FreeBSD, Linux, Solaris, and Windows](https://www.consul.io/downloads.html).
 
 ## Why choose Consul?
 
diff --git a/docs/orleans/deployment/kubernetes.md b/docs/orleans/deployment/kubernetes.md
index a2a8e7f677024..10ba92b9e0c84 100644
--- a/docs/orleans/deployment/kubernetes.md
+++ b/docs/orleans/deployment/kubernetes.md
@@ -164,4 +164,4 @@ at k8s.KubernetesClientConfiguration.InClusterConfig()
 
 * Check that `KUBERNETES_SERVICE_HOST` and `KUBERNETES_SERVICE_PORT` environment variables are set inside your Pod.
 You can check by executing the following command `kubectl exec -it <pod_name> /bin/bash -c env`.
-* Ensure that `automountServiceAccountToken` set to **true** on your Kubernetes `deployment.yaml`. For more information, see [Configure Service Accounts for Pods](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/)
+* Ensure that `automountServiceAccountToken` set to **true** on your Kubernetes `deployment.yaml`. For more information, see [Configure Service Accounts for Pods](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
diff --git a/docs/orleans/grains/grain-placement.md b/docs/orleans/grains/grain-placement.md
index 2ebe3963a33f6..382cbb2e55a46 100644
--- a/docs/orleans/grains/grain-placement.md
+++ b/docs/orleans/grains/grain-placement.md
@@ -158,4 +158,4 @@ private static void ConfigureServices(IServiceCollection services)
 }
 ```
 
-For a second simple example showing further use of the placement context, refer to the `PreferLocalPlacementDirector` in the [Orleans source repo](https://github.com/dotnet/orleans/blob/main/src/Orleans.Runtime/Placement/PreferLocalPlacementDirector.cs)
+For a second simple example showing further use of the placement context, refer to the `PreferLocalPlacementDirector` in the [Orleans source repo](https://github.com/dotnet/orleans/blob/main/src/Orleans.Runtime/Placement/PreferLocalPlacementDirector.cs).
diff --git a/docs/orleans/migration-guide.md b/docs/orleans/migration-guide.md
index 63e4a32f7b6db..d367ff8bc7a38 100644
--- a/docs/orleans/migration-guide.md
+++ b/docs/orleans/migration-guide.md
@@ -31,9 +31,9 @@ If you're upgrading a project to Orleans 7.0, you'll need to perform the followi
   - The [Microsoft.Orleans.Server](https://nuget.org/packages/Microsoft.Orleans.Server) packages reference its replacement, `Microsoft.Orleans.Runtime`.
 - Remove calls to `ConfigureApplicationParts`.
 _Application Parts_ has been removed. The C# Source Generator for Orleans is added to all packages (including the client and server) and will generate the equivalent of _Application Parts_ automatically.
-- Replace references to `Microsoft.Orleans.OrleansServiceBus` with [Microsoft.Orleans.Streaming.EventHubs](https://nuget.org/packages/Microsoft.Orleans.Streaming.EventHubs)
-- If you are using reminders, add a reference to [Microsoft.Orleans.Reminders](https://nuget.org/packages/Microsoft.Orleans.Reminders)
-- If you are using streams, add a reference to [Microsoft.Orleans.Streaming](https://nuget.org/packages/Microsoft.Orleans.Streaming)
+- Replace references to `Microsoft.Orleans.OrleansServiceBus` with [Microsoft.Orleans.Streaming.EventHubs](https://nuget.org/packages/Microsoft.Orleans.Streaming.EventHubs).
+- If you are using reminders, add a reference to [Microsoft.Orleans.Reminders](https://nuget.org/packages/Microsoft.Orleans.Reminders).
+- If you are using streams, add a reference to [Microsoft.Orleans.Streaming](https://nuget.org/packages/Microsoft.Orleans.Streaming).
 
 > [!TIP]
 > All of the Orleans samples have been upgraded to Orleans 7.0 and can be used as a reference for what changes were made. For more information, see [Orleans issue #8035](https://github.com/dotnet/orleans/issues/8035) that itemizes the changes made to each sample.
@@ -341,7 +341,7 @@ Removing the <xref:Orleans.Concurrency.ReentrantAttribute> is enough to fix the
 public sealed class CounterGrain : Grain, ICounterGrain
 {
     int _value;
-    
+
     /// <summary>
     /// Increments the grain's value and returns the previous value.
     /// </summary>
@@ -373,7 +373,7 @@ public Task<int> OuterCall(IMyGrain other)
 
 public Task CallMeBack(IMyGrain grain)
 {
-    // Because OuterCall allowed reentrancy back into that grain, this method 
+    // Because OuterCall allowed reentrancy back into that grain, this method
     // will be able to call grain.InnerCall() without deadlocking.
     await grain.InnerCall();
 }
diff --git a/docs/orleans/overview.md b/docs/orleans/overview.md
index 7177ffdb442b5..81066496d1c3a 100644
--- a/docs/orleans/overview.md
+++ b/docs/orleans/overview.md
@@ -60,7 +60,7 @@ Typically, a group of silos runs as a cluster for scalability and fault toleranc
 
 The preceding diagram shows the relationship between clusters, silos, and grains. You can have any number of clusters, each cluster has one or more silos, and each silo has one or more grains.
 
-In addition to the core programming model, silos provide grains with a set of runtime services such as timers, reminders (persistent timers), persistence, transactions, streams, and more. For more information, see [What can I do with Orleans?](#what-can-i-do-with-orleans)
+In addition to the core programming model, silos provide grains with a set of runtime services such as timers, reminders (persistent timers), persistence, transactions, streams, and more. For more information, see [What can I do with Orleans?](#what-can-i-do-with-orleans).
 
 Web apps and other external clients call grains in the cluster using the client library, which automatically manages network communication. Clients can also be co-hosted in the same process with silos for simplicity.
 
diff --git a/docs/orleans/tutorials-and-samples/overview-helloworld.md b/docs/orleans/tutorials-and-samples/overview-helloworld.md
index 761d969911d68..816ae79908a75 100644
--- a/docs/orleans/tutorials-and-samples/overview-helloworld.md
+++ b/docs/orleans/tutorials-and-samples/overview-helloworld.md
@@ -14,7 +14,7 @@ Creating an Orleans app involves configuring the silo, configuring the client, a
 ## Configure the silo
 
 Silos are configured programmatically via `SiloHostBuilder` and several supplemental option classes.
-A list of all of the options can be found [here.](../host/configuration-guide/list-of-options-classes.md)
+A list of all of the options can be found [here](../host/configuration-guide/list-of-options-classes.md).
 
 ```csharp
 static async Task<ISiloHost> StartSilo()
@@ -80,13 +80,13 @@ static async Task<IClusterClient> StartClientWithRetries()
 | `.UseLocalhostClustering()` | Same as for `SiloHost` |
 | `ClusterOptions`            | Same as for `SiloHost` |
 
-A more in-depth guide to configuring your client can be found [in the Client Configuration section of the Configuration Guide.](../host/configuration-guide/client-configuration.md)
+A more in-depth guide to configuring your client can be found [in the Client Configuration section of the Configuration Guide](../host/configuration-guide/client-configuration.md).
 
 ## Writing a grain
 
 Grains are the key primitives of the Orleans programming model. Grains are the building blocks of an Orleans application, they are atomic units of isolation, distribution, and persistence. Grains are objects that represent application entities. Just like in the classic Object-Oriented Programming, a grain encapsulates the state of an entity and encodes its behavior in the code logic. Grains can hold references to each other and interact by invoking each other's methods exposed via interfaces.
 
-You can read more about them in the [Core Concepts section of the Orleans documentation.](../grains/index.md)
+You can read more about them in the [Core Concepts section of the Orleans documentation](../grains/index.md).
 
 This is the main body of code for the Hello World grain:
 
@@ -103,7 +103,7 @@ public class HelloGrain : Orleans.Grain, IHello
 }
 ```
 
-A grain class implements one or more grain interfaces, as you can read [here, in the Grains section.](../grains/index.md)
+A grain class implements one or more grain interfaces. For more information, see the [Grains section](../grains/index.md).
 
 ```csharp
 namespace HelloWorld.Interfaces;
diff --git a/docs/orleans/tutorials-and-samples/tutorial-1.md b/docs/orleans/tutorials-and-samples/tutorial-1.md
index ea963fd12afb9..71ef8bafb3700 100644
--- a/docs/orleans/tutorials-and-samples/tutorial-1.md
+++ b/docs/orleans/tutorials-and-samples/tutorial-1.md
@@ -83,7 +83,7 @@ The preceding code:
 
 ### Create the client
 
-Finally, you need to configure a client for communicating with the grains, connect it to the cluster (with a single silo in it), and invoke the grain. The clustering configuration must match the one you used for the silo. For more information, see [Clusters and Clients](../host/client.md)
+Finally, you need to configure a client for communicating with the grains, connect it to the cluster (with a single silo in it), and invoke the grain. The clustering configuration must match the one you used for the silo. For more information, see [Clusters and Clients](../host/client.md).
 
 :::code source="snippets/minimal/Client/Program.cs":::
 
diff --git a/docs/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-eap.md b/docs/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-eap.md
index 49590a6109233..e7da7a0326e3c 100644
--- a/docs/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-eap.md
+++ b/docs/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-eap.md
@@ -2,7 +2,7 @@
 title: "Event-based Asynchronous Pattern (EAP)"
 description: See links to articles about the Event-based Asynchronous Pattern (EAP) in .NET, such as implementation, best practices, implementing an EAP client, and more.
 ms.date: "07/23/2018"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "asynchronous calls"
   - "asynchronous programming, design patterns"
   - "asynchronous programming"
@@ -10,53 +10,53 @@ ms.assetid: c6baed9f-2a25-4728-9a9a-53b7b14840cf
 ---
 # Event-based Asynchronous Pattern (EAP)
 
-There are a number of ways to expose asynchronous features to client code. The Event-based Asynchronous Pattern prescribes one way for classes to present asynchronous behavior.  
-  
+There are a number of ways to expose asynchronous features to client code. The Event-based Asynchronous Pattern prescribes one way for classes to present asynchronous behavior.
+
 > [!NOTE]
 > Starting with .NET Framework 4, the Task Parallel Library provides a new model for asynchronous and parallel programming. For more information, see [Task Parallel Library (TPL)](../parallel-programming/task-parallel-library-tpl.md) and [Task-based Asynchronous Pattern (TAP)](task-based-asynchronous-pattern-tap.md).
-  
+
 ## In This Section
 
- [Event-based Asynchronous Pattern Overview](event-based-asynchronous-pattern-overview.md)  
- Describes how the Event-based Asynchronous Pattern makes available the advantages of multithreaded applications while hiding many of the complex issues inherent in multithreaded design.  
-  
- [Implementing the Event-based Asynchronous Pattern](implementing-the-event-based-asynchronous-pattern.md)  
- Describes the standardized way to package a class that has asynchronous features.  
-  
- [Best Practices for Implementing the Event-based Asynchronous Pattern](best-practices-for-implementing-the-event-based-asynchronous-pattern.md)  
- Describes the requirements for exposing asynchronous features according to the Event-based Asynchronous Pattern.  
-  
- [Deciding When to Implement the Event-based Asynchronous Pattern](deciding-when-to-implement-the-event-based-asynchronous-pattern.md)  
- Describes how to determine when you should choose to implement the Event-based Asynchronous Pattern instead of the <xref:System.IAsyncResult> pattern represented by the [Asynchronous Programming Model (APM)](asynchronous-programming-model-apm.md)
-  
- [How to: Implement a Component That Supports the Event-based Asynchronous Pattern](component-that-supports-the-event-based-asynchronous-pattern.md)  
- Describes how to create a component that implements the Event-based Asynchronous Pattern. It is implemented using helper classes from the <xref:System.ComponentModel?displayProperty=nameWithType> namespace, which ensures that the component works correctly under any application model.  
-
- [How to: Implement a Client of the Event-based Asynchronous Pattern](how-to-implement-a-client-of-the-event-based-asynchronous-pattern.md)  
+ [Event-based Asynchronous Pattern Overview](event-based-asynchronous-pattern-overview.md)
+ Describes how the Event-based Asynchronous Pattern makes available the advantages of multithreaded applications while hiding many of the complex issues inherent in multithreaded design.
+
+ [Implementing the Event-based Asynchronous Pattern](implementing-the-event-based-asynchronous-pattern.md)
+ Describes the standardized way to package a class that has asynchronous features.
+
+ [Best Practices for Implementing the Event-based Asynchronous Pattern](best-practices-for-implementing-the-event-based-asynchronous-pattern.md)
+ Describes the requirements for exposing asynchronous features according to the Event-based Asynchronous Pattern.
+
+ [Deciding When to Implement the Event-based Asynchronous Pattern](deciding-when-to-implement-the-event-based-asynchronous-pattern.md)
+ Describes how to determine when you should choose to implement the Event-based Asynchronous Pattern instead of the <xref:System.IAsyncResult> pattern represented by the [Asynchronous Programming Model (APM)](asynchronous-programming-model-apm.md).
+
+ [How to: Implement a Component That Supports the Event-based Asynchronous Pattern](component-that-supports-the-event-based-asynchronous-pattern.md)
+ Describes how to create a component that implements the Event-based Asynchronous Pattern. It is implemented using helper classes from the <xref:System.ComponentModel?displayProperty=nameWithType> namespace, which ensures that the component works correctly under any application model.
+
+ [How to: Implement a Client of the Event-based Asynchronous Pattern](how-to-implement-a-client-of-the-event-based-asynchronous-pattern.md)
  Describes how to create a client that uses a component that implements the Event-based Asynchronous Pattern.
-  
- [How to: Use Components That Support the Event-based Asynchronous Pattern](how-to-use-components-that-support-the-event-based-asynchronous-pattern.md)  
- Describes how to use a component that supports the Event-based Asynchronous Pattern.  
-  
+
+ [How to: Use Components That Support the Event-based Asynchronous Pattern](how-to-use-components-that-support-the-event-based-asynchronous-pattern.md)
+ Describes how to use a component that supports the Event-based Asynchronous Pattern.
+
 ## Reference
 
- <xref:System.ComponentModel.AsyncOperation>  
- Describes the <xref:System.ComponentModel.AsyncOperation> class and has links to all its members.  
-  
- <xref:System.ComponentModel.AsyncOperationManager>  
- Describes the <xref:System.ComponentModel.AsyncOperationManager> class and has links to all its members.  
-  
- <xref:System.ComponentModel.BackgroundWorker>  
- Describes the <xref:System.ComponentModel.BackgroundWorker> component and has links to all its members.  
-  
+ <xref:System.ComponentModel.AsyncOperation>
+ Describes the <xref:System.ComponentModel.AsyncOperation> class and has links to all its members.
+
+ <xref:System.ComponentModel.AsyncOperationManager>
+ Describes the <xref:System.ComponentModel.AsyncOperationManager> class and has links to all its members.
+
+ <xref:System.ComponentModel.BackgroundWorker>
+ Describes the <xref:System.ComponentModel.BackgroundWorker> component and has links to all its members.
+
 ## Related Sections
 
- [Task Parallel Library (TPL)](../parallel-programming/task-parallel-library-tpl.md)  
- Describes a programming model for asynchronous and parallel operations.  
-  
- [Threading](../threading/managed-threading-basics.md)  
- Describes multithreading features in .NET.  
-  
+ [Task Parallel Library (TPL)](../parallel-programming/task-parallel-library-tpl.md)
+ Describes a programming model for asynchronous and parallel operations.
+
+ [Threading](../threading/managed-threading-basics.md)
+ Describes multithreading features in .NET.
+
 ## See also
 
 - [Managed Threading Best Practices](../threading/managed-threading-best-practices.md)
diff --git a/docs/standard/native-interop/comwrappers-source-generation.md b/docs/standard/native-interop/comwrappers-source-generation.md
index 7741008e16d1f..7c874770f23c3 100644
--- a/docs/standard/native-interop/comwrappers-source-generation.md
+++ b/docs/standard/native-interop/comwrappers-source-generation.md
@@ -124,7 +124,7 @@ HRESULT Method1(int i, int* j);
 HRESULT Method2(float i);
 ```
 
-For more information, see [Implicit method signature translations in .NET interop](./preserve-sig.md)
+For more information, see [Implicit method signature translations in .NET interop](./preserve-sig.md).
 
 ## Incompatibilities and differences to built-in COM
 
diff --git a/docs/standard/parallel-programming/task-based-asynchronous-programming.md b/docs/standard/parallel-programming/task-based-asynchronous-programming.md
index 2f5f6574ec184..e01a6fc89813c 100644
--- a/docs/standard/parallel-programming/task-based-asynchronous-programming.md
+++ b/docs/standard/parallel-programming/task-based-asynchronous-programming.md
@@ -3,10 +3,10 @@ title: "Task-based asynchronous programming - .NET"
 description: In this article, learn about task-based asynchronous programming through the Task Parallel Library (TPL) in .NET.
 ms.date: 06/03/2024
 ms.custom: devdivchpfy22
-dev_langs: 
+dev_langs:
   - "csharp"
   - "vb"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "parallelism, task"
 ms.assetid: 458b5e69-5210-45e5-bc44-3888f86abd6f
 ---
@@ -101,7 +101,7 @@ The following example shows a task that has the <xref:System.Threading.Tasks.Tas
 
 ## Tasks, threads, and culture
 
-Each thread has an associated culture and UI culture, which are defined by the <xref:System.Threading.Thread.CurrentCulture%2A?displayProperty=nameWithType> and <xref:System.Threading.Thread.CurrentUICulture%2A?displayProperty=nameWithType> properties, respectively. A thread's culture is used in operations such as, formatting, parsing, sorting, and string comparison operations. A thread's UI culture is used in resource lookup.
+Each thread has an associated culture and UI culture, which are defined by the <xref:System.Threading.Thread.CurrentCulture%2A?displayProperty=nameWithType> and <xref:System.Threading.Thread.CurrentUICulture%2A?displayProperty=nameWithType> properties, respectively. A thread's culture is used in operations such as formatting, parsing, sorting, and string comparison operations. A thread's UI culture is used in resource lookup.
 
 The system culture defines the default culture and UI culture of a thread. However, you can specify a default culture for all the threads in an application domain by using the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A?displayProperty=nameWithType> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A?displayProperty=nameWithType> properties. If you explicitly set a thread's culture and launch a new thread, the new thread doesn't inherit the culture of the calling thread; instead, its culture is the default system culture. However, in task-based programming, tasks use the calling thread's culture, even if the task runs asynchronously on a different thread.
 
diff --git a/docs/standard/serialization/system-text-json/customize-properties.md b/docs/standard/serialization/system-text-json/customize-properties.md
index 98cad3a78ffcb..085228f0f7a72 100644
--- a/docs/standard/serialization/system-text-json/customize-properties.md
+++ b/docs/standard/serialization/system-text-json/customize-properties.md
@@ -244,7 +244,7 @@ By default, properties are serialized in the order in which they're defined in t
 
 :::code language="csharp" source="snippets/how-to-6-0/csharp/PropertyOrder.cs":::
 
-## Use Github Copilot to customize property names and order
+## Use GitHub Copilot to customize property names and order
 
 You can use GitHub Copilot in your IDE to generate code to customize names and order of serialized properties. You can customize the prompt to output a JSON string with property names and values that suit your requirements.