Replace .NET Core with .NET in web-api, data, mvc, and test documentation

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 Core** and **ASP.NET Core 5.0** in the dropdowns.
+    1. **.NET** 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 Core SDK 2.2](https://dotnet.microsoft.com/download)
+* [.NET 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 Core cross-platform development** workload
+  * **.NET 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 Core**, **ASP.NET Core 2.2** and the **Web Application (Model-View-Controller)** template.
+* Select **.NET**, **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 Core** and **ASP.NET Core 5.0** in the dropdowns.
+    1. **.NET** 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 Core** and **ASP.NET Core 3.0** in the dropdowns, and then select **Web Application**.
+* Select **.NET** and **ASP.NET Core 3.0** in the dropdowns, and then select **Web Application**.
 
 # [Visual Studio Code](#tab/visual-studio-code)
 

aspnetcore/data/ef-rp/sort-filter-page.md

@@ -114,7 +114,7 @@ Where(s => s.LastName.ToUpper().Contains(searchString.ToUpper())`
 
 The preceding code would ensure that the filter is case-insensitive even if the `Where` method is called on an `IEnumerable` or runs on SQLite.
 
-When `Contains` is called on an `IEnumerable` collection, the .NET Core implementation is used. When `Contains` is called on an `IQueryable` object, the database implementation is used.
+When `Contains` is called on an `IEnumerable` collection, the .NET implementation is used. When `Contains` is called on an `IQueryable` object, the database implementation is used.
 
 Calling `Contains` on an `IQueryable` is usually preferable for performance reasons. With `IQueryable`, the filtering is done by the database server. If an `IEnumerable` is created first, all the rows have to be returned from the database server.
 
@@ -377,7 +377,7 @@ For example, the .NET Framework implementation of `Contains` performs a case-sen
 
 `Where(s => s.LastName.ToUpper().Contains(searchString.ToUpper())`
 
-The preceding code would ensure that results are case-insensitive if the code changes to use `IEnumerable`. When `Contains` is called on an `IEnumerable` collection, the .NET Core implementation is used. When `Contains` is called on an `IQueryable` object, the database implementation is used. Returning an `IEnumerable` from a repository can have a significant performance penalty:
+The preceding code would ensure that results are case-insensitive if the code changes to use `IEnumerable`. When `Contains` is called on an `IEnumerable` collection, the .NET implementation is used. When `Contains` is called on an `IQueryable` object, the database implementation is used. Returning an `IEnumerable` from a repository can have a significant performance penalty:
 
 1. All the rows are returned from the DB server.
 1. The filter is applied to all the returned rows in the application.

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 Core. 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. 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 Core 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 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/mvc/advanced/custom-model-binding.md

@@ -18,7 +18,7 @@ Model binding allows controller actions to work directly with model types (passe
 
 ## Default model binder limitations
 
-The default model binders support most of the common .NET Core data types and should meet most developers' needs. They expect to bind text-based input from the request directly to model types. You might need to transform the input prior to binding it. For example, when you have a key that can be used to look up model data. You can use a custom model binder to fetch data based on the key.
+The default model binders support most of the common .NET data types and should meet most developers' needs. They expect to bind text-based input from the request directly to model types. You might need to transform the input prior to binding it. For example, when you have a key that can be used to look up model data. You can use a custom model binder to fetch data based on the key.
 
 <!-- Duplicated in uid: mvc/models/model-binding -->
 ## Model binding simple and complex types
@@ -144,7 +144,7 @@ Model binding allows controller actions to work directly with model types (passe
 
 ## Default model binder limitations
 
-The default model binders support most of the common .NET Core data types and should meet most developers' needs. They expect to bind text-based input from the request directly to model types. You might need to transform the input prior to binding it. For example, when you have a key that can be used to look up model data. You can use a custom model binder to fetch data based on the key.
+The default model binders support most of the common .NET data types and should meet most developers' needs. They expect to bind text-based input from the request directly to model types. You might need to transform the input prior to binding it. For example, when you have a key that can be used to look up model data. You can use a custom model binder to fetch data based on the key.
 
 ## Model binding review
 

aspnetcore/test/debug-aspnetcore-source.md

@@ -40,9 +40,9 @@ The preceding instructions work for basic stepping into functions, but the optim
 
 If you have debugged an app before with the previous version of .NET, delete the `%TEMP%/SymbolCache` directory as it can have old PDBs that are out of date.
 
-## Debugging .NET Core on Unix over SSH
+## Debugging .NET on Unix over SSH
 
-* [Debugging .NET Core on Unix over SSH](https://devblogs.microsoft.com/devops/debugging-net-core-on-unix-over-ssh/)
+* [Debugging .NET on Unix over SSH](https://devblogs.microsoft.com/devops/debugging-net-core-on-unix-over-ssh/)
 * [Debugging ASP Core on Linux with Visual Studio 2017](https://devblogs.microsoft.com/premier-developer/debugging-asp-core-on-linux-with-visual-studio-2017/)
 
 ## Additional resources

aspnetcore/test/integration-tests/includes/integration-tests5.md

@@ -1,6 +1,6 @@
 :::moniker range="<= aspnetcore-5.0"
 
-This topic assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET Core and .NET Standard](/dotnet/core/testing/) topic and its linked content.
+This topic assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET and .NET Standard](/dotnet/core/testing/) topic and its linked content.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/test/integration-tests/samples) ([how to download](xref:index#how-to-download-a-sample))
 

aspnetcore/test/integration-tests/includes/integration-tests7.md

@@ -1,6 +1,6 @@
 :::moniker range="> aspnetcore-5.0 <= aspnetcore-7.0"
 
-This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET Core and .NET Standard](/dotnet/core/testing/) article and its linked content.
+This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET and .NET Standard](/dotnet/core/testing/) article and its linked content.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs.Samples/tree/main/test/integration-tests/7.x/IntegrationTestsSample) ([how to download](xref:index#how-to-download-a-sample))
 

aspnetcore/test/integration-tests/includes/integration-tests8.md

@@ -1,6 +1,6 @@
 :::moniker range="= aspnetcore-8.0"
 
-This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET Core and .NET Standard](/dotnet/core/testing/) article and its linked content.
+This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET and .NET Standard](/dotnet/core/testing/) article and its linked content.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs.Samples/tree/main/test/integration-tests/8.x/IntegrationTestsSample) ([how to download](xref:index#how-to-download-a-sample))
 

aspnetcore/test/integration-tests/includes/integration-tests9.md

@@ -1,6 +1,6 @@
 :::moniker range="= aspnetcore-9.0"
 
-This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET Core and .NET Standard](/dotnet/core/testing/) article and its linked content.
+This article assumes a basic understanding of unit tests. If unfamiliar with test concepts, see the [Unit Testing in .NET and .NET Standard](/dotnet/core/testing/) article and its linked content.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs.Samples/tree/main/test/integration-tests/9.x/IntegrationTestsSample) ([how to download](xref:index#how-to-download-a-sample))