update corefx use (dotnet#17972)

gewarren · web-flow · commit fc0523a13673 · 2020-04-21T08:14:02.000-07:00
diff --git a/.github/ISSUE_TEMPLATE/dotnet-breaking-change.md b/.github/ISSUE_TEMPLATE/dotnet-breaking-change.md
@@ -43,7 +43,7 @@ Also, remove this comment before submitting the issue.
 - ASP.NET Core
 - C#
 - Core
-- CoreFx
+- Core .NET libraries
 - Data
 - Debugger
 - Deployment for .NET Core
diff --git a/docs/core/compatibility/2.0-2.1.md b/docs/core/compatibility/2.0-2.1.md
@@ -7,7 +7,7 @@ ms.date: 12/17/2019
 
 If you're migrating from version 2.0 to version 2.1 of .NET Core, the breaking changes listed in this article may affect your app.
 
-## CoreFx
+## Core .NET libraries
 
 - [Private fields added to built-in struct types](#private-fields-added-to-built-in-struct-types)
 - [OpenSSL versions on macOS](#openssl-versions-on-macos)
diff --git a/docs/core/compatibility/2.2-3.0.md b/docs/core/compatibility/2.2-3.0.md
@@ -260,7 +260,7 @@ If you're migrating from version 2.2 to version 3.0 of .NET Core, ASP.NET Core,
 
 ***
 
-## CoreFx
+## Core .NET libraries
 
 - [APIs that report version now report product and not file version](#apis-that-report-version-now-report-product-and-not-file-version)
 - [Custom EncoderFallbackBuffer instances cannot fall back recursively](#custom-encoderfallbackbuffer-instances-cannot-fall-back-recursively)
diff --git a/docs/core/compatibility/2.2-3.1.md b/docs/core/compatibility/2.2-3.1.md
@@ -263,7 +263,7 @@ If you're migrating from version 2.2 to version 3.1 of .NET Core, ASP.NET Core,
 
 [!INCLUDE[Target framework: .NET Framework not supported](~/includes/core-changes/aspnetcore/3.0/targetfx-netfx-tfm-support.md)]
 
-## CoreFx
+## Core .NET libraries
 
 - [APIs that report version now report product and not file version](#apis-that-report-version-now-report-product-and-not-file-version)
 - [Custom EncoderFallbackBuffer instances cannot fall back recursively](#custom-encoderfallbackbuffer-instances-cannot-fall-back-recursively)
diff --git a/docs/core/compatibility/corefx.md b/docs/core/compatibility/corefx.md
@@ -1,11 +1,11 @@
 ---
 title: Base class library breaking changes
-description: Lists the breaking changes in .NET CoreFx, the base class library.
-ms.date: "09/20/2019"
+description: Lists the breaking changes in core .NET libraries.
+ms.date: 09/20/2019
 ---
-# CoreFx breaking changes
+# Core .NET libraries breaking changes
 
-CoreFx provides the primitives and other general types used by .NET Core.
+The core .NET libraries provide the primitives and other general types used by .NET Core.
 
 The following breaking changes are documented on this page:
 
diff --git a/docs/core/compatibility/fx-core.md b/docs/core/compatibility/fx-core.md
@@ -11,7 +11,7 @@ If you're migrating an app from .NET Framework to .NET Core, the breaking change
 > [!NOTE]
 > This article is not a complete list of breaking changes between .NET Framework and .NET Core. The most important breaking changes are added here as we become aware of them.
 
-## CoreFx
+## Core .NET libraries
 
 - [Change in default value of UseShellExecute](#change-in-default-value-of-useshellexecute)
 - [UnauthorizedAccessException thrown by FileSystemInfo.Attributes](#unauthorizedaccessexception-thrown-by-filesysteminfoattributes)
diff --git a/docs/core/compatibility/toc.yml b/docs/core/compatibility/toc.yml
@@ -30,7 +30,7 @@
   items:
   - name: ASP.NET Core
     href: aspnetcore.md
-  - name: CoreFx
+  - name: Core .NET libraries
     href: corefx.md
   - name: Cryptography
     href: cryptography.md
diff --git a/docs/desktop-wpf/migration/differences-from-net-framework.md b/docs/desktop-wpf/migration/differences-from-net-framework.md
@@ -35,7 +35,7 @@ When your project uses `<PackageReference>`, packages aren't stored locally in a
 
 Code Access Security (CAS) is not supported by .NET Core or WPF for .NET Core. All CAS-related functionality is treated under the assumption of full-trust. WPF for .NET Core removes CAS-related code. The public API surface of these types still exists to ensure that calls into these types succeed.
 
-Publicly defined CAS-related types were moved out of the WPF assemblies and into the CoreFX assemblies. The WPF assemblies have type-forwarding set to the new location of the moved types.
+Publicly defined CAS-related types were moved out of the WPF assemblies and into the Core .NET library assemblies. The WPF assemblies have type-forwarding set to the new location of the moved types.
 
 | Source assembly | Target assembly | Type                |
 | --------------- | --------------- | ------------------- |
diff --git a/includes/core-changes/categoryselector.md b/includes/core-changes/categoryselector.md
@@ -1,7 +1,7 @@
 > [!div class="op_single_selector"]
 >
 > - [ASP.NET Core](~/docs/core/compatibility/aspnetcore.md)
-> - [CoreFx](~/docs/core/compatibility/corefx.md)
+> - [Core .NET libraries](~/docs/core/compatibility/corefx.md)
 > - [Cryptography](~/docs/core/compatibility/cryptography.md)
 > - [EF Core](/ef/core/what-is-new/ef-core-3.0/breaking-changes)
 > - [Globalization](~/docs/core/compatibility/globalization.md)
diff --git a/includes/core-changes/corefx/1.0/filesysteminfo-attributes-exceptions.md b/includes/core-changes/corefx/1.0/filesysteminfo-attributes-exceptions.md
@@ -16,7 +16,7 @@ Modify any `catch` statements to catch an <xref:System.UnauthorizedAccessExcepti
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/2.1/instantiate-struct.md b/includes/core-changes/corefx/2.1/instantiate-struct.md
@@ -45,7 +45,7 @@ if (key.ToString() == "y")
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/2.1/process-start-changes.md b/includes/core-changes/corefx/2.1/process-start-changes.md
@@ -21,7 +21,7 @@ If your app relies on the old behavior, call <xref:System.Diagnostics.Process.St
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/change-in-null-in-utf8jsonwriter.md b/includes/core-changes/corefx/3.0/change-in-null-in-utf8jsonwriter.md
@@ -62,7 +62,7 @@ When writing property names and values with the <xref:System.Text.Json.Utf8JsonW
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/custom-encoderfallbackbuffer-cannot-be-recursive.md b/includes/core-changes/corefx/3.0/custom-encoderfallbackbuffer-cannot-be-recursive.md
@@ -30,7 +30,7 @@ If an application uses a custom <xref:System.Text.EncoderFallback> and <xref:Sys
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/fieldinfo-setvalue-exception.md b/includes/core-changes/corefx/3.0/fieldinfo-setvalue-exception.md
@@ -23,7 +23,7 @@ Alternatively, you can remove the <xref:System.Reflection.FieldAttributes.InitOn
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/floating-point-changes.md b/includes/core-changes/corefx/3.0/floating-point-changes.md
@@ -18,7 +18,7 @@ The "Potential impact to existing code" section of the [Floating-point parsing a
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/floating-point-parsing-does-not-overflow.md b/includes/core-changes/corefx/3.0/floating-point-parsing-does-not-overflow.md
@@ -24,7 +24,7 @@ This change can affect your code in either of two ways:
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/jsonencodedtext-encode-has-additional-argument.md b/includes/core-changes/corefx/3.0/jsonencodedtext-encode-has-additional-argument.md
@@ -44,7 +44,7 @@ This is a binary breaking change only; a recompile against .NET Core 3.0 Preview
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/move-invalidasynchronousstateexception.md b/includes/core-changes/corefx/3.0/move-invalidasynchronousstateexception.md
@@ -18,7 +18,7 @@ This change only affects applications that use reflection to load the <xref:Syst
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/net-core-3-0-follows-unicode-utf8-best-practices.md b/includes/core-changes/corefx/3.0/net-core-3-0-follows-unicode-utf8-best-practices.md
@@ -28,7 +28,7 @@ No action is required on the part of the developer.
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/serializer-throws-notsupportedexception.md b/includes/core-changes/corefx/3.0/serializer-throws-notsupportedexception.md
@@ -25,7 +25,7 @@ If you're catching <xref:System.Text.Json.JsonException> when deserializing, you
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/3.0/version-information-changes.md b/includes/core-changes/corefx/3.0/version-information-changes.md
@@ -20,7 +20,7 @@ None. This change should make version detection intuitive rather than obtuse.
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 
diff --git a/includes/core-changes/corefx/openssl-dependencies-macos.md b/includes/core-changes/corefx/openssl-dependencies-macos.md
@@ -34,7 +34,7 @@ With this change, the behavior for the .NET Core runtimes on macOS is as follows
 
 #### Category
 
-CoreFx
+Core .NET libraries
 
 #### Affected APIs
 

Original file line number	Diff line number	Diff line change
`@@ -1,7 +1,7 @@`
`1`	`1`	`> [!div class="op_single_selector"]`
`2`	`2`	`>`
`3`	`3`	`> - [ASP.NET Core](~/docs/core/compatibility/aspnetcore.md)`
`4`		`-> - [CoreFx](~/docs/core/compatibility/corefx.md)`
	`4`	`+> - [Core .NET libraries](~/docs/core/compatibility/corefx.md)`
`5`	`5`	`> - [Cryptography](~/docs/core/compatibility/cryptography.md)`
`6`	`6`	`> - [EF Core](/ef/core/what-is-new/ef-core-3.0/breaking-changes)`
`7`	`7`	`> - [Globalization](~/docs/core/compatibility/globalization.md)`