Address feedback: revert specified files and apply targeted corrections

- Reverted 11 files to original state as requested
- Fixed .NET distribution packaging link in servers/index.md
- Updated choose-aspnet-framework.md table text
- Fixed owin.md compatible replacements text
- Updated target-aspnetcore.md support policy reference

Co-authored-by: danroth27 <1874516+danroth27@users.noreply.github.com>

Author: Copilot

aspnetcore/data/ef-mvc/intro.md

@@ -67,7 +67,7 @@ Users can view and update student, course, and instructor information. Here are
 1. In the **Configure your new project** dialog, enter `ContosoUniversity` for **Project name**. It's important to use this exact name including capitalization, so each `namespace` matches when code is copied.
 1. Select **Create**.
 1. In the **Create a new ASP.NET Core web application** dialog, select:
-    1. **.NET** and **ASP.NET Core 5.0** in the dropdowns.
+    1. **.NET Core** and **ASP.NET Core 5.0** in the dropdowns.
     1. **ASP.NET Core Web App (Model-View-Controller)**.
     1. **Create**
       ![New ASP.NET Core Project dialog](~/data/ef-mvc/intro/_static/new-aspnet5.png)
@@ -396,10 +396,10 @@ The sample application is a web site for a fictional Contoso University. It incl
 
 ## Prerequisites
 
-* [.NET SDK 2.2](https://dotnet.microsoft.com/download)
+* [.NET Core SDK 2.2](https://dotnet.microsoft.com/download)
 * [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the following workloads:
   * **ASP.NET and web development** workload
-  * **.NET cross-platform development** workload
+  * **.NET Core cross-platform development** workload
 
 ## Troubleshooting
 
@@ -434,7 +434,7 @@ Users can view and update student, course, and instructor information. Here are
 
 * Wait for the **New ASP.NET Core Web Application** dialog to appear.
 
-* Select **.NET**, **ASP.NET Core 2.2** and the **Web Application (Model-View-Controller)** template.
+* Select **.NET Core**, **ASP.NET Core 2.2** and the **Web Application (Model-View-Controller)** template.
 
 * Make sure **Authentication** is set to **No Authentication**.
 

aspnetcore/data/ef-rp/intro.md

@@ -642,7 +642,7 @@ Run the project to seed the database.
 1. In the **Configure your new project** dialog, enter `ContosoUniversity` for **Project name**. It's important to use this exact name including capitalization, so each `namespace` matches when code is copied.
 1. Select **Create**.
 1. In the **Create a new ASP.NET Core web application** dialog, select:
-    1. **.NET** and **ASP.NET Core 5.0** in the dropdowns.
+    1. **.NET Core** and **ASP.NET Core 5.0** in the dropdowns.
     1. **ASP.NET Core Web App**.
     1. **Create**
       ![New ASP.NET Core Project dialog](~/data/ef-rp/intro/_static/new-aspnet5.png)
@@ -1153,7 +1153,7 @@ To run the app after downloading the completed project:
 * From the Visual Studio **File** menu, select **New** > **Project**.
 * Select **ASP.NET Core Web Application**.
 * Name the project *ContosoUniversity*. It's important to use this exact name including capitalization, so the namespaces match when code is copied and pasted.
-* Select **.NET** and **ASP.NET Core 3.0** in the dropdowns, and then select **Web Application**.
+* Select **.NET Core** and **ASP.NET Core 3.0** in the dropdowns, and then select **Web Application**.
 
 # [Visual Studio Code](#tab/visual-studio-code)
 

aspnetcore/data/entity-framework-6.md

@@ -33,11 +33,11 @@ This article shows how to use Entity Framework 6 in an ASP.NET Core application.
 
 ## Overview
 
-To use Entity Framework 6, your project has to compile against .NET Framework, as Entity Framework 6 doesn't support .NET. If you need cross-platform features you will need to upgrade to [Entity Framework Core](/ef/).
+To use Entity Framework 6, your project has to compile against .NET Framework, as Entity Framework 6 doesn't support .NET Core. If you need cross-platform features you will need to upgrade to [Entity Framework Core](/ef/).
 
 The recommended way to use Entity Framework 6 in an ASP.NET Core application is to put the EF6 context and model classes in a class library project that targets .NET Framework. Add a reference to the class library from the ASP.NET Core project. See the sample [Visual Studio solution with EF6 and ASP.NET Core projects](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/data/entity-framework-6/sample/).
 
-You can't put an EF6 context in an ASP.NET Core project because .NET projects don't support all of the functionality that EF6 commands such as *Enable-Migrations* require.
+You can't put an EF6 context in an ASP.NET Core project because .NET Core projects don't support all of the functionality that EF6 commands such as *Enable-Migrations* require.
 
 Regardless of project type in which you locate your EF6 context, only EF6 command-line tools work with an EF6 context. For example, `Scaffold-DbContext` is only available in Entity Framework Core. If you need to do reverse engineering of a database into an EF6 model, see [Code First to an Existing Database](/ef/ef6/modeling/code-first/workflows/existing-database).
 

aspnetcore/fundamentals/choose-aspnet-framework.md

@@ -32,7 +32,7 @@ The following table compares ASP.NET Core to ASP.NET 4.x.
 |Multiple versions per machine|One version per machine|
 |Develop with [Visual Studio](https://visualstudio.microsoft.com/vs/) or [Visual Studio Code](https://code.visualstudio.com/) using C# or F#|Develop with [Visual Studio](https://visualstudio.microsoft.com/vs/) using C#, VB, or F#|
 |Higher performance than ASP.NET 4.x|Good performance|
-|[Use .NET runtime](/dotnet/standard/choosing-core-framework-server)|Use .NET Framework runtime|
+|[Use the latest .NET runtime](/dotnet/standard/choosing-core-framework-server)|Use .NET Framework runtime|
 
 See [ASP.NET Core targeting .NET Framework](xref:index#target-framework) for information on ASP.NET Core 2.x support on .NET Framework.
 

aspnetcore/fundamentals/http-requests.md

@@ -1246,7 +1246,7 @@ An <xref:System.Net.Http.IHttpClientFactory> can be registered and used to confi
 
 ## Prerequisites
 
-Projects targeting .NET Framework require installation of the [Microsoft.Extensions.Http](https://www.nuget.org/packages/Microsoft.Extensions.Http/) NuGet package. Projects that target .NET and reference the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) already include the `Microsoft.Extensions.Http` package.
+Projects targeting .NET Framework require installation of the [Microsoft.Extensions.Http](https://www.nuget.org/packages/Microsoft.Extensions.Http/) NuGet package. Projects that target .NET Core and reference the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) already include the `Microsoft.Extensions.Http` package.
 
 ## Consumption patterns
 

aspnetcore/fundamentals/metapackage-app.md

@@ -13,7 +13,7 @@ uid: fundamentals/metapackage-app
 
 :::moniker range=">= aspnetcore-3.0"
 
- The ASP.NET Core shared framework (`Microsoft.AspNetCore.App`) contains assemblies that are developed and supported by Microsoft. `Microsoft.AspNetCore.App` is installed when the [.NET 3.0 or later SDK](https://dotnet.microsoft.com/download/dotnet-core/3.0) is installed. The *shared framework* is the set of assemblies (*.dll* files) that are installed on the machine and includes a runtime component and a targeting pack. For more information, see [The shared framework](https://natemcmaster.com/blog/2018/08/29/netcore-primitives-2/).
+ The ASP.NET Core shared framework (`Microsoft.AspNetCore.App`) contains assemblies that are developed and supported by Microsoft. `Microsoft.AspNetCore.App` is installed when the [.NET Core 3.0 or later SDK](https://dotnet.microsoft.com/download/dotnet-core/3.0) is installed. The *shared framework* is the set of assemblies (*.dll* files) that are installed on the machine and includes a runtime component and a targeting pack. For more information, see [The shared framework](https://natemcmaster.com/blog/2018/08/29/netcore-primitives-2/).
 
 * Projects that target the `Microsoft.NET.Sdk.Web` SDK implicitly reference the `Microsoft.AspNetCore.App` framework.
 
@@ -37,7 +37,7 @@ The ASP.NET Core shared framework:
 
 :::moniker range="< aspnetcore-3.0"
 
-This feature requires ASP.NET Core 2.x targeting .NET 2.x.
+This feature requires ASP.NET Core 2.x targeting .NET Core 2.x.
 
 The [Microsoft.AspNetCore.App](https://www.nuget.org/packages/Microsoft.AspNetCore.App) [metapackage](/dotnet/core/packages#metapackages) for ASP.NET Core:
 
@@ -89,7 +89,7 @@ Specifying a version number on the `Microsoft.AspNetCore.App` reference does **n
 
   *Warning NU1604: Project dependency Microsoft.AspNetCore.App does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.*
 
-* This is a known issue with the .NET 2.1 SDK.
+* This is a known issue with the .NET Core 2.1 SDK.
 
 :::moniker-end
 
@@ -103,8 +103,8 @@ The `Microsoft.AspNetCore.App` [metapackage](/dotnet/core/packages#metapackages)
 
 To update ASP.NET Core:
 
-* On development machines and build servers: Download and install the [.NET SDK](https://dotnet.microsoft.com/download).
-* On deployment servers: Download and install the [.NET runtime](https://dotnet.microsoft.com/download).
+* On development machines and build servers: Download and install the [.NET Core SDK](https://dotnet.microsoft.com/download).
+* On deployment servers: Download and install the [.NET Core runtime](https://dotnet.microsoft.com/download).
 
  Applications will roll forward to the latest installed version on application restart. It's not necessary to update the `Microsoft.AspNetCore.App` version number in the project file. For more information, see [Framework-dependent apps roll forward](/dotnet/core/versions/selection#framework-dependent-apps-roll-forward).
 

aspnetcore/fundamentals/metapackage.md

@@ -22,7 +22,7 @@ uid: fundamentals/metapackage
 > [!NOTE]
 > We recommend applications targeting ASP.NET Core 2.1 or later use the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) rather than this package. See [Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App](#migrate) in this article.
 
-This feature requires ASP.NET Core 2.x targeting .NET 2.x.
+This feature requires ASP.NET Core 2.x targeting .NET Core 2.x.
 
 [Microsoft.AspNetCore.All](https://www.nuget.org/packages/Microsoft.AspNetCore.All) is a metapackage that refers to a shared framework. A *shared framework* is a set of assemblies (*.dll* files) that are not in the app's folders. The shared framework must be installed on the machine to run the app. For more information, see [The shared framework](https://natemcmaster.com/blog/2018/08/29/netcore-primitives-2/).
 
@@ -54,7 +54,7 @@ The project's SDK must be set to `Microsoft.NET.Sdk.Web` in the project file to
 
 *Warning NU1604: Project dependency Microsoft.AspNetCore.All does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.*
 
-This is a known issue with the .NET 2.1 SDK and will be fixed in the .NET 2.2 SDK.
+This is a known issue with the .NET Core 2.1 SDK and will be fixed in the .NET Core 2.2 SDK.
 
 :::moniker-end
 
@@ -91,6 +91,6 @@ Any dependencies of the preceding packages that otherwise aren't dependencies of
 
 We recommend migrating to the `Microsoft.AspNetCore.App` metapackage for 2.1 or later. To keep using the `Microsoft.AspNetCore.All` metapackage and ensure the latest patch version is deployed:
 
-* On development machines and build servers: Install the latest [.NET SDK](https://dotnet.microsoft.com/download).
-* On deployment servers: Install the latest [.NET runtime](https://dotnet.microsoft.com/download).
+* On development machines and build servers: Install the latest [.NET Core SDK](https://dotnet.microsoft.com/download).
+* On deployment servers: Install the latest [.NET Core runtime](https://dotnet.microsoft.com/download).
  Your app will roll forward to the latest installed version on an application restart.

aspnetcore/fundamentals/owin.md

@@ -14,7 +14,7 @@ By [Steve Smith](https://ardalis.com/) and [Rick Anderson](https://twitter.com/R
 ASP.NET Core:
 
 * Supports the Open Web Interface for .NET (OWIN).
-* Has .NET compatible replacements for the `Microsoft.Owin.*` ([Katana](/aspnet/aspnet/overview/owin-and-katana/)) libraries.
+* Has compatible replacements for the `Microsoft.Owin.*` ([Katana](/aspnet/aspnet/overview/owin-and-katana/)) libraries.
 
 OWIN allows web apps to be decoupled from web servers. It defines a standard way for middleware to be used in a pipeline to handle requests and associated responses. ASP.NET Core applications and middleware can interoperate with OWIN-based applications, servers, and middleware.
 

aspnetcore/fundamentals/servers/index.md

@@ -189,13 +189,13 @@ A `launchSettings.json` file provides configuration when launching an app with `
     * Windows Server 2016/Windows 10 or later†
     * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
     * macOS 10.15 or later
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [HTTP.sys](xref:fundamentals/servers/httpsys#http2-support)
   * Windows Server 2016/Windows 10 or later
   * Target framework: Not applicable to HTTP.sys deployments.
 * [IIS (in-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [IIS (out-of-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
   * Public-facing edge server connections use HTTP/2, but the reverse proxy connection to Kestrel uses HTTP/1.1.
@@ -212,13 +212,13 @@ A `launchSettings.json` file provides configuration when launching an app with `
     * Windows Server 2016/Windows 10 or later†
     * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
     * HTTP/2 will be supported on macOS in a future release.
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [HTTP.sys](xref:fundamentals/servers/httpsys#http2-support)
   * Windows Server 2016/Windows 10 or later
   * Target framework: Not applicable to HTTP.sys deployments.
 * [IIS (in-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [IIS (out-of-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
   * Public-facing edge server connections use HTTP/2, but the reverse proxy connection to Kestrel uses HTTP/1.1.
@@ -235,13 +235,13 @@ A `launchSettings.json` file provides configuration when launching an app with `
     * Windows Server 2016/Windows 10 or later†
     * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
     * HTTP/2 will be supported on macOS in a future release.
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [HTTP.sys](xref:fundamentals/servers/httpsys#http2-support)
   * Windows Server 2016/Windows 10 or later
   * Target framework: Not applicable to HTTP.sys deployments.
 * [IIS (in-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
-  * Target framework: .NET 2.2 or later
+  * Target framework: .NET Core 2.2 or later
 * [IIS (out-of-process)](xref:host-and-deploy/iis/index#http2-support)
   * Windows Server 2016/Windows 10 or later; IIS 10 or later
   * Public-facing edge server connections use HTTP/2, but the reverse proxy connection to Kestrel uses HTTP/1.1.

aspnetcore/fundamentals/servers/kestrel/http2.md

@@ -21,15 +21,15 @@ uid: fundamentals/servers/kestrel/http2
   * Windows Server 2016/Windows 10 or later‡
   * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
   * macOS 10.15 or later
-* Target framework: .NET 2.2 or later
+* Target framework: .NET Core 2.2 or later
 * [Application-Layer Protocol Negotiation (ALPN)](https://tools.ietf.org/html/rfc7301#section-3) connection
 * TLS 1.2 or later connection
 
 ‡Kestrel has limited support for HTTP/2 on Windows Server 2012 R2 and Windows 8.1. Support is limited because the list of supported TLS cipher suites available on these operating systems is limited. A certificate generated using an Elliptic Curve Digital Signature Algorithm (ECDSA) may be required to secure TLS connections.
 
 If an HTTP/2 connection is established, [HttpRequest.Protocol](xref:Microsoft.AspNetCore.Http.HttpRequest.Protocol%2A) reports `HTTP/2`.
 
-Starting with .NET 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
+Starting with .NET Core 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
 
 ## Advanced HTTP/2 features
 
@@ -52,7 +52,7 @@ Additional HTTP/2 features in Kestrel support gRPC, including support for respon
 * Operating system†
   * Windows Server 2016/Windows 10 or later‡
   * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
-* Target framework: .NET 2.2 or later
+* Target framework: .NET Core 2.2 or later
 * [Application-Layer Protocol Negotiation (ALPN)](https://tools.ietf.org/html/rfc7301#section-3) connection
 * TLS 1.2 or later connection
 
@@ -61,7 +61,7 @@ Additional HTTP/2 features in Kestrel support gRPC, including support for respon
 
 If an HTTP/2 connection is established, [HttpRequest.Protocol](xref:Microsoft.AspNetCore.Http.HttpRequest.Protocol%2A) reports `HTTP/2`.
 
-Starting with .NET 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
+Starting with .NET Core 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
 
 ## Advanced HTTP/2 features
 
@@ -84,7 +84,7 @@ Additional HTTP/2 features in Kestrel support gRPC, including support for respon
 * Operating system†
   * Windows Server 2016/Windows 10 or later‡
   * Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
-* Target framework: .NET 2.2 or later
+* Target framework: .NET Core 2.2 or later
 * [Application-Layer Protocol Negotiation (ALPN)](https://tools.ietf.org/html/rfc7301#section-3) connection
 * TLS 1.2 or later connection
 
@@ -93,7 +93,7 @@ Additional HTTP/2 features in Kestrel support gRPC, including support for respon
 
 If an HTTP/2 connection is established, [HttpRequest.Protocol](xref:Microsoft.AspNetCore.Http.HttpRequest.Protocol%2A) reports `HTTP/2`.
 
-Starting with .NET 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
+Starting with .NET Core 3.0, HTTP/2 is enabled by default. For more information on configuration, see the [Kestrel HTTP/2 limits](xref:fundamentals/servers/kestrel/options#http2-limits) and [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) sections.
 
 ## Advanced HTTP/2 features