diff --git a/docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/seedwork-domain-model-base-classes-interfaces.md b/docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/seedwork-domain-model-base-classes-interfaces.md
index e76907759273e..33e2e70f1a5bd 100644
--- a/docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/seedwork-domain-model-base-classes-interfaces.md
+++ b/docs/standard/microservices-architecture/microservice-ddd-cqrs-patterns/seedwork-domain-model-base-classes-interfaces.md
@@ -19,7 +19,7 @@ This is the type of copy and paste reuse that many developers share between proj
## The custom Entity base class
-The following code is an example of an Entity base class where you can place code that can be used the same way by any domain entity, such as the entity ID, [equality operators](https://docs.microsoft.com/dotnet/csharp/language-reference/operators/equality-comparison-operator), a domain event list per entity, etc.
+The following code is an example of an Entity base class where you can place code that can be used the same way by any domain entity, such as the entity ID, [equality operators](~/docs/csharp/language-reference/operators/equality-comparison-operator.md), a domain event list per entity, etc.
```csharp
// COMPATIBLE WITH ENTITY FRAMEWORK CORE (1.1 and later)
diff --git a/docs/standard/microservices-architecture/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps.md b/docs/standard/microservices-architecture/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps.md
index 917f464420a73..d8ebcc720065c 100644
--- a/docs/standard/microservices-architecture/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps.md
+++ b/docs/standard/microservices-architecture/multi-container-microservice-net-applications/test-aspnet-core-services-web-apps.md
@@ -104,7 +104,7 @@ public class PrimeWebDefaultRequestShould
[*https://docs.microsoft.com/aspnet/core/test/integration-tests*](https://docs.microsoft.com/aspnet/core/test/integration-tests)
- **Unit testing in .NET Core using dotnet test**
- [*https://docs.microsoft.com/dotnet/core/testing/unit-testing-with-dotnet-test*](https://docs.microsoft.com/dotnet/core/testing/unit-testing-with-dotnet-test)
+ [*https://docs.microsoft.com/dotnet/core/testing/unit-testing-with-dotnet-test*](~/docs/core/testing/unit-testing-with-dotnet-test.md)
- **xUnit.net**. Official site.
[*https://xunit.github.io/*](https://xunit.github.io/)
diff --git a/includes/migration-guide/retargeting/winforms/accessibility-improvements-windows-forms-controls-for-net-472.md b/includes/migration-guide/retargeting/winforms/accessibility-improvements-windows-forms-controls-for-net-472.md
index 2324c91696574..3259fb9190031 100644
--- a/includes/migration-guide/retargeting/winforms/accessibility-improvements-windows-forms-controls-for-net-472.md
+++ b/includes/migration-guide/retargeting/winforms/accessibility-improvements-windows-forms-controls-for-net-472.md
@@ -3,7 +3,7 @@
| | |
|---|---|
|Details|Windows Forms Framework is improving how it works with accessibility technologies to better support Windows Forms customers. These include the following changes:
<runtime> section of the app config file and setting it to false, as the following example shows.<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
</startup>
<runtime>
<!-- AppContextSwitchOverrides value attribute is in the form of 'key1=true/false;key2=true/false -->
<AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false;Switch.UseLegacyAccessibilityFeatures.2=false" />
</runtime>
</configuration>
Note that to opt in to the accessibility features added in .NET Framework 4.7.2, you must also opt in to accessibility features of .NET Framework 4.7.1 as well. Applications that target the .NET Framework 4.7.2 or later and want to preserve the legacy accessibility behavior can opt in to the use of legacy accessibility features by explicitly setting this AppContext switch to true.Use of OS-defined colors in High Contrast themesfalse will now use OS-defined colors in High Contrast theme.<!-- Windows 10 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />
Improved Narrator supportfalse.true.true for the false for the true<runtime> section of the app config file and setting it to false, as the following example shows.<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
</startup>
<runtime>
<!-- AppContextSwitchOverrides value attribute is in the form of 'key1=true/false;key2=true/false -->
<AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false;Switch.UseLegacyAccessibilityFeatures.2=false" />
</runtime>
</configuration>
Note that to opt in to the accessibility features added in .NET Framework 4.7.2, you must also opt in to accessibility features of .NET Framework 4.7.1 as well. Applications that target the .NET Framework 4.7.2 or later and want to preserve the legacy accessibility behavior can opt in to the use of legacy accessibility features by explicitly setting this AppContext switch to true.Use of OS-defined colors in High Contrast themesfalse will now use OS-defined colors in High Contrast theme.<!-- Windows 10 -->
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />
Improved Narrator supportfalse.true.true for the false for the true<runtime> section of the app.config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Forms.UseLegacyContextMenuStripSourceControlValue=false"/>
</runtime>
Applications that target the .NET Framework 4.7.2 or later, and want to preserve the legacy behavior can opt in to the use of the legacy source control value by explicitly setting this AppContext switch to true.|
+|Suggestion|How to opt in or out of these changesIn order for an application to benefit from these changes, it must run on the .NET Framework 4.7.2 or later. The application can benefit from these changes in either of the following ways:<runtime> section of the app.config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Forms.UseLegacyContextMenuStripSourceControlValue=false"/>
</runtime>
Applications that target the .NET Framework 4.7.2 or later, and want to preserve the legacy behavior can opt in to the use of the legacy source control value by explicitly setting this AppContext switch to true.|
|Scope|Edge|
|Version|4.7.2|
|Type|Retargeting|
diff --git a/includes/migration-guide/retargeting/winforms/privatefontcollectionaddfontfile-method-releases-font-resources.md b/includes/migration-guide/retargeting/winforms/privatefontcollectionaddfontfile-method-releases-font-resources.md
index 1f4eff5024b87..6f11dcd65ac0a 100644
--- a/includes/migration-guide/retargeting/winforms/privatefontcollectionaddfontfile-method-releases-font-resources.md
+++ b/includes/migration-guide/retargeting/winforms/privatefontcollectionaddfontfile-method-releases-font-resources.md
@@ -3,7 +3,7 @@
| | |
|---|---|
|Details|In the .NET Framework 4.7.1 and previous versions, the <runtime> section of the app.config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Drawing.Text.DoNotRemoveGdiFontsResourcesFromFontCollection=false"/>
</runtime>
Applications that target the .NET Framework 4.7.2 or later, and want to preserve the legacy behavior can opt in to not release font resources by explicitly setting this AppContext switch to true.|
+|Suggestion|How to opt in or out of these changesIn order for an application to benefit from these changes, it must run on the .NET Framework 4.7.2 or later. The application can benefit from these changes in either of the following ways:<runtime> section of the app.config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Drawing.Text.DoNotRemoveGdiFontsResourcesFromFontCollection=false"/>
</runtime>
Applications that target the .NET Framework 4.7.2 or later, and want to preserve the legacy behavior can opt in to not release font resources by explicitly setting this AppContext switch to true.|
|Scope|Edge|
|Version|4.7.2|
|Type|Retargeting|
diff --git a/includes/migration-guide/retargeting/winforms/winforms-domain-upbutton-downbutton-actions-are-sync-now.md b/includes/migration-guide/retargeting/winforms/winforms-domain-upbutton-downbutton-actions-are-sync-now.md
index d423600f42ade..04af58874caf7 100644
--- a/includes/migration-guide/retargeting/winforms/winforms-domain-upbutton-downbutton-actions-are-sync-now.md
+++ b/includes/migration-guide/retargeting/winforms/winforms-domain-upbutton-downbutton-actions-are-sync-now.md
@@ -3,7 +3,7 @@
| | |
|---|---|
|Details|In the .NET Framework 4.7.1 and previous versions the <runtime> section of the app config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Forms.DomainUpDown.UseLegacyScrolling=false"/>
</runtime>
|
+|Suggestion|In order for an application to benefit from these changes, it must run on the .NET Framework 4.7.2 or later. The application can benefit from these changes in either of the following ways:<runtime> section of the app config file and setting it to false, as the following example shows.<runtime>
<AppContextSwitchOverrides value="Switch.System.Windows.Forms.DomainUpDown.UseLegacyScrolling=false"/>
</runtime>
|
|Scope|Edge|
|Version|4.7.2|
|Type|Retargeting|