removed locale information from URLs

Author: Tanya-Solyanik

README.md

@@ -52,7 +52,7 @@ What would not make the bar:
 
 :warning: This repository contains only implementations for Windows Forms for [.NET platform](https://github.com/dotnet/core).<br />
 It does not contain either:
-* The .NET Framework variant of Windows Forms. Issues with .NET Framework, including Windows Forms, should be filed on the [Developer Community](https://developercommunity.visualstudio.com/spaces/61/index.html) or [Product Support](https://support.microsoft.com/en-us/contactus?ws=support) websites. They should not be filed on this repository.
+* The .NET Framework variant of Windows Forms. Issues with .NET Framework, including Windows Forms, should be filed on the [Developer Community](https://developercommunity.visualstudio.com/spaces/61/index.html) or [Product Support](https://support.microsoft.com/contactus?ws=support) websites. They should not be filed on this repository.
 * The Windows Forms Designer implementations. Issues with the Designer can be filed via VS Feedback tool (top right-hand side icon in Visual Studio) or be filed in this repo using the Windows Forms out-of-process designer issue template.
 
 # How can I contribute?

docs/coding-style.md

@@ -15,7 +15,7 @@ There are a few key things we strive for to attain our clarity goals:
 - Minimal code visibility (via access modifiers, type nesting, and local functions).
 - All context captured in source (via code or comments).
 
-Windows Forms dates back to the mid 1990s (originally [Windows Foundation Classes](https://web.archive.org/web/20050915003238/http://msdn.microsoft.com/library/en-us/vjcore98/html/vjconintroductiontowfcprogramming.asp)). It has seen over 25 years of language and coding evolution. We believe that updating the code to modern style makes the code easier to maintain and update in the longer term. While we do not update everything as the style guidelines evolve, we do make continual investments in cleaning the codebase as an engineering best practice.
+Windows Forms dates back to the mid 1990s (originally [Windows Foundation Classes](https://web.archive.org/web/20050915003238/http://msdn.microsoft.com/library/vjcore98/html/vjconintroductiontowfcprogramming.asp)). It has seen over 25 years of language and coding evolution. We believe that updating the code to modern style makes the code easier to maintain and update in the longer term. While we do not update everything as the style guidelines evolve, we do make continual investments in cleaning the codebase as an engineering best practice.
 
 A number of the following detailed guidelines are captured in our `.editorconfig` and as such you'll get the appropriate feedback in Visual Studio. We're iterating to enable more automated analyzers in the future.
 

docs/porting-guidelines.md

@@ -139,11 +139,11 @@ You can search for additional types which you may need in porting your apps to .
 [dotnet-blog-port-guide]: https://devblogs.microsoft.com/dotnet/how-to-port-desktop-applications-to-net-core-3-0/
 [dotnet-blog-port-video]: https://www.youtube.com/watch?v=upVQEUc_KwU
 [api-port]: https://blogs.msdn.microsoft.com/dotnet/2018/08/08/are-your-windows-forms-and-wpf-applications-ready-for-net-core-3-0/
-[pkg-config]: https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference
+[pkg-config]: https://docs.microsoft.com/nuget/reference/migrate-packages-config-to-package-reference
 [sdk-tool]:https://github.com/hvanbakel/CsprojToVs2017
-[framework-charting]: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.datavisualization.charting
+[framework-charting]: https://docs.microsoft.com/dotnet/api/system.windows.forms.datavisualization.charting
 [nuget-dataviz]: https://www.nuget.org/packages/System.windows.forms.datavisualization
 [dataviz]: https://github.com/dotnet/winforms-datavisualization
-[compat-pack]: https://docs.microsoft.com/en-us/dotnet/core/porting/windows-compat-pack
+[compat-pack]: https://docs.microsoft.com/dotnet/core/porting/windows-compat-pack
 [wcf-supported]: https://github.com/dotnet/wcf/blob/master/release-notes/SupportedFeatures-v2.1.0.md
 [apisofnet]: https://apisof.net/

src/Accessibility/readme.md

@@ -2,7 +2,7 @@
 
 This directory contains source files used to build Accessibility.dll, the managed wrapper for COM accessibility interface.
 
-See https://docs.microsoft.com/en-us/dotnet/api/accessibility
+See https://docs.microsoft.com/dotnet/api/accessibility
 
 Source in this directory is generated by a tool and **should not be modified directly**.
 

src/System.Drawing.Common/src/System/Drawing/StringFormatFlags.cs

@@ -31,7 +31,7 @@ public enum StringFormatFlags
     /// The GDI+ equivalent for this is StringFormatFlags::StringFormatFlagsNoFitBlackBox,
     /// which is defined as 0x4. This was a mistake introduced since the first version of
     /// the product and fixing it at this point would be a breaking change.
-    /// <see href="https://docs.microsoft.com/en-us/windows/desktop/api/gdiplusenums/ne-gdiplusenums-stringformatflags"/>
+    /// <see href="https://docs.microsoft.com/windows/desktop/api/gdiplusenums/ne-gdiplusenums-stringformatflags"/>
     /// </summary>
     FitBlackBox = 0x00000004,
 

src/System.Drawing.Common/tests/System/Drawing/Printing/PrinterSettingsTests.cs

@@ -415,7 +415,7 @@ public void IsDirectPrintingSupported_ImageNotSupported_ReturnsExpected()
     public void SupportsColor_ReturnsExpected()
     {
         // XPS and PDF printers support color.
-        // docs.microsoft.com/en-us/windows-hardware/drivers/print/improved-color-printing
+        // docs.microsoft.com/windows-hardware/drivers/print/improved-color-printing
         PrinterSettings printerSettings = new() { PrinterName = GetNameOfTestPrinterSuitableForDevModeTesting() };
         Assert.True(printerSettings.SupportsColor);
     }

src/System.Private.Windows.Core/src/Windows/Win32/System/Com/SAFEARRAY.cs

@@ -71,7 +71,7 @@ public VARENUM VarType
     public T GetValue<T>(Span<int> indices)
     {
         // SAFEARRAY is laid out in column-major order.
-        // See https://docs.microsoft.com/en-us/previous-versions/windows/desktop/automat/array-manipulation-functions
+        // See https://docs.microsoft.com/previous-versions/windows/desktop/automat/array-manipulation-functions
         int indicesIndex = 0;
         int c1 = indices[indicesIndex++];
         uint dimensionSize = 1;

src/System.Private.Windows.Core/src/Windows/Win32/System/Variant/VARIANT.cs

@@ -417,7 +417,7 @@ private static Type GetRecordElementType(IRecordInfo* record)
                 // CLR arrays are laid out in row-major order.
                 // See CLI 8.9.1: https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-335.pdf
                 // However, SAFEARRAYs are laid out in column-major order.
-                // See https://docs.microsoft.com/en-us/previous-versions/windows/desktop/automat/array-manipulation-functions
+                // See https://docs.microsoft.com/previous-versions/windows/desktop/automat/array-manipulation-functions
                 // Therefore, we need to transpose data.
                 TransposeArray(psa, array, arrayType);
             }

src/System.Windows.Forms.Analyzers.CSharp/src/System/Windows/Forms/CSharp/Generators/ApplicationConfiguration/ApplicationConfigurationGenerator.cs

@@ -37,7 +37,7 @@ private static void Execute(
         if (outputKind is not OutputKind.WindowsApplication
             // Starting in the 5.0.100 version of the .NET SDK, when OutputType is set to Exe, it is automatically changed to WinExe
             // for WPF and Windows Forms apps that target any framework version, including .NET Framework.
-            // https://docs.microsoft.com/en-us/dotnet/core/compatibility/sdk/5.0/automatically-infer-winexe-output-type
+            // https://docs.microsoft.com/dotnet/core/compatibility/sdk/5.0/automatically-infer-winexe-output-type
             and not OutputKind.ConsoleApplication)
         {
             context.ReportDiagnostic(Diagnostic.Create(

src/System.Windows.Forms/System/Windows/Forms/Controls/PropertyGrid/PropertyGridInternal/CategoryGridEntry.CategoryGridEntryAccessibleObject.cs

@@ -89,7 +89,7 @@ internal override int Row
         internal override VARIANT GetPropertyValue(UIA_PROPERTY_ID propertyID) => propertyID switch
         {
             // To announce expanded collapsed state control type should be appropriate:
-            // https://docs.microsoft.com/en-us/windows/win32/winauto/uiauto-controlpatternmapping
+            // https://docs.microsoft.com/windows/win32/winauto/uiauto-controlpatternmapping
             UIA_PROPERTY_ID.UIA_ControlTypePropertyId => (VARIANT)(int)UIA_CONTROLTYPE_ID.UIA_TreeItemControlTypeId,
             UIA_PROPERTY_ID.UIA_LocalizedControlTypePropertyId => (VARIANT)SR.CategoryPropertyGridLocalizedControlType,
             _ => base.GetPropertyValue(propertyID),