Assorted changes (#625)

* Assorted changes

* Removed remaining occurences of 'en-us'

Documentation/compatibility/! Template.md

@@ -6,7 +6,7 @@
 
 ### Scope
 [|Major|Minor|Edge|Transparent|]
-//A description of the Scope values can be found at https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/net-compatibility-diagnostics
+//A description of the Scope values can be found at https://docs.microsoft.com/dotnet/articles/framework/migration-guide/net-compatibility-diagnostics
 
 ### Version Introduced
 [|Version in which the breaking change first occurred|]
@@ -39,7 +39,7 @@
 [| List of APIs affected by change referred to using docids|]
 
 // For details on how to generate docids, please look at other change files or
-// see https://msdn.microsoft.com/en-us/library/fsbx0t7x.aspx for the spec.
+// see https://msdn.microsoft.com/library/fsbx0t7x.aspx for the spec.
 //
 // For example, if all members of System.Xml.XmlTextReader is affected, we would have the following item:
 // * `T:System.Xml.XmlTextReader`

Documentation/compatibility/Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md

@@ -24,13 +24,13 @@ There are two new context switch values to control whether SHA1 (insecure) or SH
 
 - Switch.System.Security.Cryptography.Pkcs.UseInsecureHashAlgorithms
 
-For applications that target the .NET Framework 4.7.1 and later versions, if the use of SHA256 is undesirable, you can restore the default to SHA1 by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file:
+For applications that target the .NET Framework 4.7.1 and later versions, if the use of SHA256 is undesirable, you can restore the default to SHA1 by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file:
 
 ```xml
 <AppContextSwitchOverrides value="Switch.System.Security.Cryptography.Xml.UseInsecureHashAlgorithms=true;Switch.System.Security.Cryptography.Pkcs.UseInsecureHashAlgorithms=true" /> 
 ```
 
-For applications that target the .NET Framework 4.7 and earlier versions, you can opt into this change by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file:
+For applications that target the .NET Framework 4.7 and earlier versions, you can opt into this change by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file:
 
 ```xml
 <AppContextSwitchOverrides value="Switch.System.Security.Cryptography.Xml.UseInsecureHashAlgorithms=false;Switch.System.Security.Cryptography.Pkcs.UseInsecureHashAlgorithms=false" /> 

Documentation/compatibility/SignedXml.GetPublicKey-returns-RSACng-on-net462.md

@@ -21,7 +21,7 @@ Starting with the .NET Framework 4.6.2, the concrete type of the object returned
 
 ### Recommended Action
 
-Starting with apps running on the .NET Framework 4.7.1, you can use the CryptoServiceProvider implementation used by default in the .NET Framework 4.6.1 and earlier versions by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file:
+Starting with apps running on the .NET Framework 4.7.1, you can use the CryptoServiceProvider implementation used by default in the .NET Framework 4.6.1 and earlier versions by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file:
 
 ```xml
 <AppContextSwitchOverrides value="Switch.System.Security.Cryptography.Xml.SignedXmlUseLegacyCertificatePrivateKey=true" />

Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md

@@ -38,7 +38,7 @@ Framework 4.6.1.
 
 Apps targeting the .NET Framework 4.6.1 can opt out of this change (or apps
 targeting older Frameworks may opt in) by using the
-[DontSupportReentrantFilterMessage](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-custom-imessagefilter-prefiltermessage-implementations#mitigation)
+[DontSupportReentrantFilterMessage](~/docs/framework/migration-guide/mitigation-custom-imessagefilter-prefiltermessage-implementations#mitigation.md)
 compatibility switch.
 
 ### Affected APIs

Documentation/compatibility/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md

@@ -19,13 +19,11 @@ In order to conform to RFC 2396, spaces in route paths are now escaped when popu
 Code should be updated to unescape string parameters from a route. If the original URI is needed, it can be accessed with the <xref:System.Net.HttpWebRequest.RequestUri>.OriginalString API.
 
 ### Affected APIs
-* `M:System.Web.Http.RouteAttribute.%23ctor(System.String)`
+* `M:System.Web.Mvc.RouteAttribute.#ctor(System.String)`
 
 ### Category
 ASP.NET
 
-[More information](http://connect.microsoft.com/VisualStudio/feedback/details/878827/issues-with-encoding-in-web-api-in-4-5-2)
-
 <!--
     ### Notes
     Single-diagnostic compilation action analyzer

Documentation/compatibility/binding-a-wpf-selector-property-(such-as-'selecteditem')-to-a-static-property-does-not-work.md

@@ -27,7 +27,7 @@ This behavior was reverted in a servicing update for the .NET Framework 4.5. Ple
 ### Category
 Windows Presentation Foundation (WPF)
 
-[More information](https://social.msdn.microsoft.com/Forums/vstudio/en-US/56ff3199-5abc-454e-87f7-bafff43e7422/net-45-critical-selecteditem-not-setting-binding-item?forum=wpf)
+[More information](https://social.msdn.microsoft.com/Forums/vstudio/56ff3199-5abc-454e-87f7-bafff43e7422/net-45-critical-selecteditem-not-setting-binding-item?forum=wpf)
 
 <!--
     ### Notes

Documentation/compatibility/certificate-eku-oid-validation.md

@@ -18,7 +18,7 @@ Starting with .NET Framework 4.6, the <xref:System.Net.Security.SslStream> or <x
 
 ### Recommended Action
 
-If this change is undesirable, you can disable certificate EKU OID validation by adding the following switch to the [`\<AppContextSwitchOverrides>` element](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element) in the [`\<runtime> section](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) of your app configuration file:
+If this change is undesirable, you can disable certificate EKU OID validation by adding the following switch to the [`\<AppContextSwitchOverrides>` element](~/docs/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element.md) in the [`\<runtime> section](~/docsframework/configure-apps/file-schema/runtime/runtime-element.md) of your app configuration file:
 
 ```xml
 <runtime>

Documentation/compatibility/change-in-path-separator-character-in-zip-files.md

@@ -20,7 +20,7 @@ Decompressing a zip file created by an app that targets a previous version of th
 
 ### Recommended Action
 
-The impact of this change on .ZIP files that are decompressed on the Windows operating system by APIs in the .NET Framework <xref:System.IO?displayProperty=nameWithType> namespace should be minimal, since these APIs can seamlessly handle either a slash ("/") or a backslash ("\\") as the path separator character.
+The impact of this change on .ZIP files that are decompressed on the Windows operating system by APIs in the .NET Framework <xref:System.IO?displayProperty=nameWithType> namespace should be minimal, since these APIs can seamlessly handle either a slash ("/") or a backslash ("\\") as the path separator character.  
 
 If this change is undesirable, you can opt out of it by adding a configuration setting to the [`<runtime>`](https://docs.microsoft.com/dotnet/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your application configuration file. The following example shows both the `<runtime` section and the `Switch.System.IO.Compression.ZipFile.UseBackslash` opt-out switch:
 

Documentation/compatibility/connection-pool-blocking-period-for-azure-sql-databases-is-removed.md

@@ -24,7 +24,7 @@ In the .NET Framework 4.6.1 and earlier versions, when an app encounters a
 transient connection failure when connecting to a database, the connection
 attempt cannot be retried quickly, because the connection pool caches the error
 and re-throws it for 5 seconds to 1 minute. For more information, see
-[SQL Server Connection Pooling (ADO.NET)](https://docs.microsoft.com/en-us/dotnet/articles/framework/data/adonet/sql-server-connection-pooling).
+[SQL Server Connection Pooling (ADO.NET)](~/docs/framework/data/adonet/sql-server-connection-pooling.md).
 This behavior is problematic for connections to Azure SQL databases, which often
 fail with transient errors that are typically recovered from within a few
 seconds. The connection pool blocking feature means that the app cannot connect

Documentation/compatibility/cspparameters_parentwindowhandle-now-expects-hwnd-value.md

@@ -26,7 +26,7 @@ cspParameters.ParentWindowHandle = form.Handle;
 
 In previous versions of the .NET Framework, the value was expected to be an <xref:System.IntPtr?displayProperty=name>
 representing a location in memory where the
-[HWND](https://msdn.microsoft.com/en-us/library/windows/desktop/aa383751(v=vs.85).aspx#HWND) value resided.
+[HWND](https://msdn.microsoft.com/library/windows/desktop/aa383751.aspx#HWND) value resided.
 Setting the property to form.Handle on Windows 7 and earlier versions had no
 effect, but on Windows 8 and later versions, it results in a
 "<xref:System.Security.Cryptography.CryptographicException?displayProperty=name>: The parameter is incorrect."

Documentation/compatibility/currentculture-flows-across-tasks.md

@@ -44,7 +44,7 @@ AppContext.SetSwitch("Switch.System.Globalization.NoAsyncCurrentCulture", true);
 ```
 
 This issue has been fixed by WPF in .NET Framework 4.6.2. It has also been fixed
-in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/en-us/kb/3139549).
+in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/kb/3139549).
 Applications targeting .NET 4.6 or later will automatically get the right
 behavior in WPF applications -
 <xref:System.Globalization.CultureInfo.CurrentCulture?displayProperty=name>/<xref:System.Globalization.CultureInfo.CurrentUICulture?displayProperty=name>)
@@ -59,6 +59,6 @@ would be preserved across Dispatcher operations.
 ### Category
 Core
 
-[More information](https://docs.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo#Async)
+[More information](https://docs.microsoft.com/dotnet/api/system.globalization.cultureinfo#Async)
 
 <!-- breaking change id: 146 -->

Documentation/compatibility/currentculture-not-preserved-across-wpf-dispatcher-operations.md

@@ -67,7 +67,7 @@ setting the following compatibility switch:
     ```
 
 This issue has been fixed by WPF in .NET Framework 4.6.2. It has also been fixed
-in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/en-us/kb/3139549).
+in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/kb/3139549).
 Applications targeting .NET 4.6 or later will automatically
 get the right behavior in WPF applications -
 <xref:System.Globalization.CultureInfo.CurrentCulture?displayProperty=name>/<xref:System.Globalization.CultureInfo.CurrentUICulture?displayProperty=name>)

Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md

@@ -16,7 +16,7 @@ In some cases, when an app uses two or more app domains with different applicati
 - [ ] Build-time break
 
 ### Recommended Action
-See [Mitigation: Deserialization of Objects Across App Domains](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains)
+See [Mitigation: Deserialization of Objects Across App Domains](~/docs/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains.md)
 
 ### Affected APIs
 * Not detectable via API analysis

Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md

@@ -29,7 +29,7 @@ finalizer thread, the previous behavior can be restored by providing an
 appropriate handler for the
 <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException>
 event, or by setting a
-[runtime configuration element](https://docs.microsoft.com/en-us/dotnet/articles/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element).
+[runtime configuration element](~/docs/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element.md).
 
 ### Affected APIs
 * `M:System.Threading.Tasks.Task.Run(System.Action)`

Documentation/compatibility/glyphrun_computeinkboundingbox()-and-formattedtext_extent-return-different-values-beginning-in-_net-4_5.md

@@ -43,6 +43,6 @@ the app.config file:
 ### Category
 Windows Presentation Foundation (WPF)
 
-[More information](http://support.microsoft.com/en-us/kb/3009678)
+[More information](http://support.microsoft.com/kb/3009678)
 
 <!-- breaking change id: 114 -->

Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md

@@ -25,7 +25,7 @@ Ideally, applications should be updated to not use UTF-7 encoding in
 <xref:System.Web.HttpRequest?displayProperty=name>s. Alternatively, legacy
 behavior can be restored by using the `aspnet:AllowUtf7RequestContentEncoding`
 attribute of the
-[appSettings](https://msdn.microsoft.com/en-us/library/hh975440(v=vs.110).aspx)
+[appSettings](https://msdn.microsoft.com/library/hh975440(v=vs.110).aspx)
 element.
 
 ### Affected APIs

Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md

@@ -21,7 +21,7 @@ escapes the ampersand (&) character.
 
 If your app depends on the previous behavior of this method, you can add an
 aspnet:JavaScriptDoNotEncodeAmpersand setting to the
-[ASP.NET appSettings element](https://msdn.microsoft.com/en-us/library/hh975440(v=vs.110).aspx)
+[ASP.NET appSettings element](https://msdn.microsoft.com/library/hh975440.aspx)
 in your configuration file.
 
 ### Affected APIs

Documentation/compatibility/listboxitem-isselected-binding-issue-with-observablecollection_move.md

@@ -43,6 +43,6 @@ Framework.
 ### Category
 Windows Presentation Foundation (WPF)
 
-[More information](http://social.msdn.microsoft.com/Forums/en-US/afcbc8b3-a2f2-41e4-b402-2efc9eab1ffe/listboxitem-isselected-binding-issue-with-observablecollectiontmove?forum=wpf)
+[More information](http://social.msdn.microsoft.com/Forums/afcbc8b3-a2f2-41e4-b402-2efc9eab1ffe/listboxitem-isselected-binding-issue-with-observablecollectiontmove?forum=wpf)
 
 <!-- breaking change id: 102 -->

Documentation/compatibility/marshal_sizeof-and-marshal_ptrtostructure-overloads-break-dynamic-code.md

@@ -29,7 +29,7 @@ have been added that may be ambiguous to the scripting engines.
 
 Update scripts to clearly indicate which overload should be used. This can
 typically done by explicitly casting the methods' type parameters as
-<xref:System.Type>. See [this link](https://support.microsoft.com/en-us/kb/2909958/)
+<xref:System.Type>. See [this link](https://support.microsoft.com/kb/2909958/)
 for more detail and examples of how to workaround the issue.
 
 ### Affected APIs
@@ -38,7 +38,7 @@ for more detail and examples of how to workaround the issue.
 ### Category
 Core
 
-[More information](https://support.microsoft.com/en-us/kb/2909958/)
+[More information](https://support.microsoft.com/kb/2909958/)
 
 <!--
     ### Notes

Documentation/compatibility/no-longer-able-to-set-enableviewstatemac-to-false.md

@@ -16,7 +16,7 @@ ASP.NET no longer allows developers to specify `<pages enableViewStateMac="false
 - [ ] Build-time break
 
 ### Recommended Action
-EnableViewStateMac must be assumed to be true, and any resulting MAC errors must be resolved (as explained in [this guidance](https://support.microsoft.com/en-us/kb/2915218), which contains multiple resolutions depending on the specifics of what is causing MAC errors).
+EnableViewStateMac must be assumed to be true, and any resulting MAC errors must be resolved (as explained in [this guidance](https://support.microsoft.com/kb/2915218), which contains multiple resolutions depending on the specifics of what is causing MAC errors).
 
 ### Affected APIs
 * Not detectable via API analysis

Documentation/compatibility/obsoleteattribute-exports-as-both-obsoleteattribute-and-deprecatedattribute-in-winmd-scenarios.md

@@ -14,7 +14,7 @@ Available
 When you create a Windows Metadata library (.winmd file), the
 <xref:System.ObsoleteAttribute?displayProperty=name> attribute is exported as
 both <xref:System.ObsoleteAttribute?displayProperty=name> and
-[Windows.Foundation.DeprecatedAttribute](https://docs.microsoft.com/en-us/uwp/api/windows.foundation.metadata.deprecatedattribute).
+[Windows.Foundation.DeprecatedAttribute](https://docs.microsoft.com/uwp/api/windows.foundation.metadata.deprecatedattribute).
 
 - [ ] Quirked
 - [x] Build-time break
@@ -27,7 +27,7 @@ warnings when consuming that code from C++/CX or JavaScript.
 
 We do not recommend applying both
 <xref:System.ObsoleteAttribute?displayProperty=name> and
-[Windows.Foundation.DeprecatedAttribute](https://docs.microsoft.com/en-us/uwp/api/windows.foundation.metadata.deprecatedattribute) to code in managed assemblies; it may
+[Windows.Foundation.DeprecatedAttribute](https://docs.microsoft.com/uwp/api/windows.foundation.metadata.deprecatedattribute) to code in managed assemblies; it may
 result in build warnings.
 
 ### Affected APIs

Documentation/compatibility/remove-ssl3-from-the-wcf-transportdefaults.md

@@ -27,8 +27,8 @@ Ssl3 to the list of negotiated protocols.
 
 * <xref:System.ServiceModel.Channels.SslStreamSecurityBindingElement.SslProtocols>
 * <xref:System.ServiceModel.TcpTransportSecurity.SslProtocols>
-* [\<transport> section of \<netTcpBinding>](https://docs.microsoft.com/en-us/dotnet/articles/framework/configure-apps/file-schema/wcf/transport-of-nettcpbinding)
-* [\<sslStreamSecurity> section of \<customBinding>](https://docs.microsoft.com/en-us/dotnet/articles/framework/configure-apps/file-schema/wcf/sslstreamsecurity)
+* [\<transport> section of \<netTcpBinding>](~/docs/framework/configure-apps/file-schema/wcf/transport-of-nettcpbinding.md)
+* [\<sslStreamSecurity> section of \<customBinding>]~/docs/framework/configure-apps/file-schema/wcf/sslstreamsecurity.md)
 
 ### Affected APIs
 * `P:System.ServiceModel.Channels.SslStreamSecurityBindingElement.SslProtocols`

Documentation/compatibility/servicepointmanager.securityprotocol-defaults-to-securityprotocoltype.systemdefault.md

@@ -12,7 +12,7 @@ NotPlanned
 ### Change Description
 Starting with apps that target the .NET Framework 4.7, the default value of the <xref:System.Net.ServicePointManager.SecurityProtocol?displayProperty=nameWithType> property is <xref:System.Net.SecurityProtocolType.SystemDefault?displayProperty=nameWithType>. This change allows .NET Framework networking APIs based on SslStream (such as FTP, HTTPS, and SMTP) to inherit the default security protocols from the operating system instead of using hard-coded values defined by the .NET Framework. The default varies by operating system and any custom configuration performed by the system administrator. For information on the default SChannel protocol in each version of the Windows operating system, see [Protocols in TLS/SSL (Schannel SSP)](https://msdn.microsoft.com/library/windows/desktop/mt808159.aspx).
 
-For applications that target an earlier version of the .NET Framework, the default value of the <xref:System.Net.ServicePointManager.SecurityProtocol?displayProperty=nameWithType> property depends on the version of the .NET Framework targeted. See the [Networking section of Retargeting Changes for Migration from .NET Framework 4.5.2 to 4.6](https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/retargeting/4.5.2-4.6#Networking) for more information.
+For applications that target an earlier version of the .NET Framework, the default value of the <xref:System.Net.ServicePointManager.SecurityProtocol?displayProperty=nameWithType> property depends on the version of the .NET Framework targeted. See the [Networking section of Retargeting Changes for Migration from .NET Framework 4.5.2 to 4.6](~/docs/framework/migration-guide/retargeting/4.5.2-4.6.md#Networking.md) for more information.
 
 - [X] Quirked 
 - [ ] Build-time break

Documentation/compatibility/sharing-session-state-with-asp_net-stateserver-requires-all-servers-in-the-web-farm-to-use-the-same-_net-framework-version.md

@@ -34,7 +34,7 @@ ASP.NET
 
 <!--
     ### Notes
-    Source analysis will be more useful than binary here; we'll want to look in the web.config for StateServer usage (https://msdn.microsoft.com/en-us/subscriptions/downloads/h6bb9cz9(v=vs.71).aspx)
+    Source analysis will be more useful than binary here; we'll want to look in the web.config for StateServer usage (https://msdn.microsoft.com/subscriptions/downloads/h6bb9cz9(v=vs.71).aspx)
 -->
 
 <!-- breaking change id: 128 -->