Removed mentions of Go Global Developer Center (#2594)

* Removed mentions of Go Global Developer Center

* Apply suggestions from code review

Co-Authored-By: Maira Wenzel <[email protected]>

Author: Ron Petrusha

xml/System.Globalization/CultureAndRegionInfoBuilder.xml

@@ -27,7 +27,7 @@
 ## Remarks  
  The <xref:System.Globalization.CultureInfo> class holds culture-specific information, such as the associated language, sublanguage, country/region, calendar, and cultural conventions. This class also provides culture-specific instances of the <xref:System.Globalization.DateTimeFormatInfo>, <xref:System.Globalization.NumberFormatInfo>, <xref:System.Globalization.CompareInfo>, and <xref:System.Globalization.TextInfo> classes, which are required for culture-specific operations such as casing, formatting and parsing dates and numbers, and comparing strings.  
   
- By default, the .NET Framework supports <xref:System.Globalization.CultureInfo> objects that represent a predefined set of cultures. For a list of these cultures, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. The <xref:System.Globalization.CultureAndRegionInfoBuilder> class enables you to create a custom culture that is completely new or that overrides a predefined culture.  When a custom culture is installed and registered on a particular computer, it becomes indistinguishable from predefined <xref:System.Globalization.CultureInfo> objects, and can be instantiated and used just like those objects.  
+ By default, the .NET Framework supports <xref:System.Globalization.CultureInfo> objects that represent a predefined set of cultures. For a list of these cultures available on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). The <xref:System.Globalization.CultureAndRegionInfoBuilder> class enables you to create a custom culture that is completely new or that overrides a predefined culture.  When a custom culture is installed and registered on a particular computer, it becomes indistinguishable from predefined <xref:System.Globalization.CultureInfo> objects, and can be instantiated and used just like those objects.  
   
 > [!IMPORTANT]
 >  Note that the <xref:System.Globalization.CultureAndRegionInfoBuilder> class is found in an assembly named sysglobl.dll. Successfully compiling code that uses this type requires that you add a reference to sysglobl.dll.  
@@ -1474,4 +1474,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>

xml/System.Globalization/CultureInfo.xml

@@ -89,7 +89,7 @@
   
  A culture identifier is a standard international numeric abbreviation and has the components necessary to uniquely identify one of the installed cultures. Your application can use predefined culture identifiers or define custom identifiers.  
   
- Certain predefined culture names and identifiers are used by this and other classes in the <xref:System.Globalization?displayProperty=nameWithType> namespace. Detailed culture information appears in the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center.  
+ Certain predefined culture names and identifiers are used by this and other classes in the <xref:System.Globalization?displayProperty=nameWithType> namespace. For detailed culture information for Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47).  
   
  Remember that the culture names and identifiers represent only a subset of cultures that can be found on a particular computer. Windows versions or service packs can change the available cultures. Applications add custom cultures using the <xref:System.Globalization.CultureAndRegionInfoBuilder> class. Users add their own custom cultures using the Microsoft Locale Builder tool. Microsoft Locale Builder is written in managed code using the `CultureAndRegionInfoBuilder` class.  
   
@@ -355,7 +355,6 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
     </remarks>
     <altmember cref="T:System.Globalization.CultureAndRegionInfoBuilder" />
     <altmember cref="T:System.Globalization.RegionInfo" />
-    <related type="Article" href="/globalization/index">Go Global Developer Center</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">
@@ -405,9 +404,10 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- Predefined culture identifiers are listed in the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center.  
-  
+## Remarks
+
+Predefined culture identifiers for cultures available on Windows system are listed in the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47).
+
  In most cases, the `culture` parameter is mapped to the corresponding National Language Support (NLS) locale identifier. The value of the `culture` parameter becomes the value of the <xref:System.Globalization.CultureInfo.LCID%2A> property of the new <xref:System.Globalization.CultureInfo>.  
   
  We recommend that you call the locale name constructor <xref:System.Globalization.CultureInfo.%23ctor%2A?displayProperty=nameWithType>, because locale names are preferable to LCIDs. For custom locales, a locale name is required.  
@@ -489,8 +489,9 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- For a list of predefined culture names, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
+## Remarks
+
+For a list of predefined culture names on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
   
  If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constructor creates an instance of the invariant culture; this is equivalent to retrieving the value of the <xref:System.Globalization.CultureInfo.InvariantCulture%2A> property.  
   
@@ -571,9 +572,10 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- Predefined culture identifiers are listed in the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center.  
-  
+## Remarks
+
+Predefined culture identifiers available on Windows systems are listed in the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47).
+
  In most cases, the `culture` parameter is mapped to the corresponding National Language Support (NLS) locale identifier. The value of the `culture` parameter becomes the value of the <xref:System.Globalization.CultureInfo.LCID%2A> property of the new <xref:System.Globalization.CultureInfo>.  
   
  We recommend that you call the locale name constructor <xref:System.Globalization.CultureInfo.%23ctor%2A?displayProperty=nameWithType>, because locale names are preferable to LCIDs. For custom locales, a locale name is required.  
@@ -655,10 +657,11 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- For a list of predefined culture names, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
+## Remarks
+
+For a list of predefined culture names, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
   
- If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constructor creates an instance of the invariant culture; this is equivalent to retrieving the value of the <xref:System.Globalization.CultureInfo.InvariantCulture%2A> property.  
+If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constructor creates an instance of the invariant culture; this is equivalent to retrieving the value of the <xref:System.Globalization.CultureInfo.InvariantCulture%2A> property.  
   
  The user might choose to override some of the values associated with the current Windows culture through the regional and language options portion of Control Panel. For example, the user might choose to display the date in a different format or to use a currency other than the default for the culture.  
   
@@ -990,7 +993,7 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
  The <xref:System.Globalization.CultureInfo.CreateSpecificCulture%2A> method wraps a call to the <xref:System.Globalization.CultureInfo.%23ctor%28System.String%29> constructor.  
   
 > [!NOTE]
->  For a list of predefined culture names, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
+> For a list of predefined culture names on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
   
  Cultures are grouped into three sets: the invariant culture, the neutral cultures, and the specific cultures. For more information, see the description of the <xref:System.Globalization.CultureInfo> class.  
   
@@ -2102,8 +2105,9 @@ csc /resource:GreetingStrings.resources Example1.cs
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- For a list of predefined culture names, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
+## Remarks
+
+For a list of predefined culture names on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
   
  The <xref:System.Globalization.CultureInfo.GetCultureInfo%2A> method retrieves a cached, read-only <xref:System.Globalization.CultureInfo> object. It offers better performance than a corresponding call to the <xref:System.Globalization.CultureInfo.%23ctor%28System.String%29?displayProperty=nameWithType> constructor.  
   
@@ -2166,7 +2170,7 @@ csc /resource:GreetingStrings.resources Example1.cs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For a list of predefined culture names, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
+ For a list of predefined culture names on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag.  
   
  The <xref:System.Globalization.CultureInfo.GetCultureInfo%2A> method obtains a cached, read-only <xref:System.Globalization.CultureInfo> object. It offers better performance than a corresponding call to a <xref:System.Globalization.CultureInfo.%23ctor%2A> constructor. The method is used to create a culture similar to that specified by the `name` parameter, but with different sorting and casing rules.  
   
@@ -2903,8 +2907,9 @@ csc /resource:GreetingStrings.resources Example1.cs
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- For a list of predefined culture names and identifiers that the <xref:System.Globalization.CultureInfo.Name%2A> property can return, see the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) at the Go Global Developer Center. In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag. Note that culture names are subject to change, and that they also can reflect the names of custom cultures.  
+## Remarks
+
+For a list of predefined culture names and identifiers that the <xref:System.Globalization.CultureInfo.Name%2A> property can return on Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47). In addition, starting with Windows 10, `name` can be any valid BCP-47 language tag. Note that culture names are subject to change, and that they also can reflect the names of custom cultures.  
   
  The <xref:System.Globalization.CultureInfo.Name%2A?displayProperty=nameWithType> property follows the naming standards provided in the <xref:System.Globalization.CultureInfo> class topic. It returns the short form of the culture name that excludes any indication of an alternate sort order. For example, if you instantiate a <xref:System.Globalization.CultureInfo> object by using the string "de-DE_phoneb" to reflect an alternate sort order, the <xref:System.Globalization.CultureInfo.Name%2A> property returns "de-DE".  
   
@@ -3500,7 +3505,7 @@ csc /resource:GreetingStrings.resources Example1.cs
 ## Remarks  
  This method overrides <xref:System.Object.ToString%2A?displayProperty=nameWithType>. It returns a normalized version of the culture name that is passed to the <xref:System.Globalization.CultureInfo.%23ctor%28System.String%29> or <xref:System.Globalization.CultureInfo.%23ctor%28System.String%2CSystem.Boolean%29> constructor or to the <xref:System.Globalization.CultureInfo.CreateSpecificCulture%2A> or <xref:System.Globalization.CultureInfo.GetCultureInfo%28System.String%29> method. It normalizes the result string by converting characters in *languagecode2* to lowercase and converting characters in *country/regioncode2* to uppercase if necessary.  
   
- Predefined culture names are listed in the [National Language Support (NLS) API Reference](https://go.microsoft.com/fwlink/?LinkId=200048) page at the Go Global Developer Center.  
+ Predefined culture names on Windows systems are listed in the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47).  
   
  ]]></format>
         </remarks>
@@ -3628,4 +3633,4 @@ csc /resource:GreetingStrings.resources Example1.cs
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>

xml/System.Globalization/TextInfo.xml

@@ -511,10 +511,11 @@
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- Certain predefined culture names and identifiers are used by this and other classes in the <xref:System.Globalization?displayProperty=nameWithType> namespace, as well as the Windows API. The detailed culture information is defined in the [National Language Support (NLS) API Reference topic at the Go Global Developer Center](https://msdn.microsoft.com/goglobal/bb896001.aspx).  
-  
- The <xref:System.Globalization.TextInfo.LCID%2A> property always reflects a specific culture identifier instead of a neutral culture identifier. If <xref:System.Globalization.CultureInfo.LCID%2A?displayProperty=nameWithType> is set to a neutral culture identifier, the corresponding <xref:System.Globalization.TextInfo.LCID%2A> has as its value an arbitrary specific culture identifier that uses the same language. For example, the <xref:System.Globalization.CultureInfo.LCID%2A?displayProperty=nameWithType> property returns 0x0009 for the English neutral culture, named "en". However, the corresponding <xref:System.Globalization.TextInfo.LCID%2A> property might return 0x0409 for the English (United States) culture, named en-US.  
+## Remarks
+
+Certain predefined culture names and identifiers are used by this and other classes in the <xref:System.Globalization?displayProperty=nameWithType> namespace. For detailed culture information for Windows systems, see the **Language tag** column in the [list of language/region names supported by Windows](https://docs.microsoft.com/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c). Culture names follow the standard defined by [BCP 47](https://tools.ietf.org/html/bcp47).
+
+The <xref:System.Globalization.TextInfo.LCID%2A> property always reflects a specific culture identifier instead of a neutral culture identifier. If <xref:System.Globalization.CultureInfo.LCID%2A?displayProperty=nameWithType> is set to a neutral culture identifier, the corresponding <xref:System.Globalization.TextInfo.LCID%2A> has as its value an arbitrary specific culture identifier that uses the same language. For example, the <xref:System.Globalization.CultureInfo.LCID%2A?displayProperty=nameWithType> property returns 0x0009 for the English neutral culture, named "en". However, the corresponding <xref:System.Globalization.TextInfo.LCID%2A> property might return 0x0409 for the English (United States) culture, named en-US.  
   
  Similarly, the <xref:System.Globalization.TextInfo.LCID%2A> property always corresponds to a default sort order, and never reflects a specific sort order. For example, the default sort order for Spanish (Spain) is the international sort order. If <xref:System.Globalization.CultureInfo.LCID%2A?displayProperty=nameWithType> is set to "0x040A" (Spanish with the traditional sort order), the corresponding <xref:System.Globalization.TextInfo.LCID%2A> value is "0x0C0A" (Spanish with the default international sort order).  
   
@@ -1198,4 +1199,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>