Replace .NET Core with .NET in fundamentals documentation

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

Author: Copilot

aspnetcore/fundamentals/best-practices.md

@@ -65,7 +65,7 @@ Beginning with ASP.NET Core 3.0, `IAsyncEnumerable<T>` can be used as an alterna
 
 ## Minimize large object allocations
 
-The [.NET Core garbage collector](/dotnet/standard/garbage-collection/) manages allocation and release of memory automatically in ASP.NET Core apps. Automatic garbage collection generally means that developers don't need to worry about how or when memory is freed. However, cleaning up unreferenced objects takes CPU time, so developers should minimize allocating objects in [hot code paths](#understand-hot-code-paths). Garbage collection is especially expensive on large objects (>= 85,000 bytes). Large objects are stored on the [large object heap](/dotnet/standard/garbage-collection/large-object-heap) and require a full (generation 2) garbage collection to clean up. Unlike generation 0 and generation 1 collections, a generation 2 collection requires a temporary suspension of app execution. Frequent allocation and de-allocation of large objects can cause inconsistent performance.
+The [.NET garbage collector](/dotnet/standard/garbage-collection/) manages allocation and release of memory automatically in ASP.NET Core apps. Automatic garbage collection generally means that developers don't need to worry about how or when memory is freed. However, cleaning up unreferenced objects takes CPU time, so developers should minimize allocating objects in [hot code paths](#understand-hot-code-paths). Garbage collection is especially expensive on large objects (>= 85,000 bytes). Large objects are stored on the [large object heap](/dotnet/standard/garbage-collection/large-object-heap) and require a full (generation 2) garbage collection to clean up. Unlike generation 0 and generation 1 collections, a generation 2 collection requires a temporary suspension of app execution. Frequent allocation and de-allocation of large objects can cause inconsistent performance.
 
 Recommendations:
 
@@ -154,7 +154,7 @@ Recommendations:
 
 ## Use the latest ASP.NET Core release
 
-Each new release of ASP.NET Core includes performance improvements. Optimizations in .NET Core and ASP.NET Core mean that newer versions generally outperform older versions. For example, .NET Core 2.1 added support for compiled regular expressions and benefitted from [Span\<T>](/dotnet/standard/memory-and-spans/memory-t-usage-guidelines). ASP.NET Core 2.2 added support for HTTP/2. [ASP.NET Core 3.0 adds many improvements](xref:aspnetcore-3.0) that reduce memory usage and improve throughput. If performance is a priority, consider upgrading to the current version of ASP.NET Core.
+Each new release of ASP.NET Core includes performance improvements. Optimizations in .NET and ASP.NET Core mean that newer versions generally outperform older versions. For example, .NET 2.1 added support for compiled regular expressions and benefitted from [Span\<T>](/dotnet/standard/memory-and-spans/memory-t-usage-guidelines). ASP.NET Core 2.2 added support for HTTP/2. [ASP.NET Core 3.0 adds many improvements](xref:aspnetcore-3.0) that reduce memory usage and improve throughput. If performance is a priority, consider upgrading to the current version of ASP.NET Core.
 
 ## Minimize exceptions
 

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 Core runtime](/dotnet/standard/choosing-core-framework-server)|Use .NET Framework runtime|
+|[Use .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/dotnet-scaffold-telemetry.md

@@ -66,5 +66,5 @@ The telemetry feature collects the following data.
 
 ## Additional resources
 
-* [.NET Core SDK telemetry](/dotnet/core/tools/telemetry)
+* [.NET SDK telemetry](/dotnet/core/tools/telemetry)
 * [.NET CLI telemetry data](https://dotnet.microsoft.com/platform/telemetry)

aspnetcore/fundamentals/file-providers.md

@@ -21,7 +21,7 @@ ASP.NET Core abstracts file system access through the use of File Providers. Fil
 * <xref:Microsoft.AspNetCore.Hosting.IWebHostEnvironment> exposes the app's [content root](xref:fundamentals/index#content-root) and [web root](xref:fundamentals/index#web-root) as `IFileProvider` types.
 * [Static File Middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
 * [Razor](xref:mvc/views/razor) uses File Providers to locate pages and views.
-* .NET Core tooling uses File Providers and glob patterns to specify which files should be published.
+* .NET tooling uses File Providers and glob patterns to specify which files should be published.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/fundamentals/file-providers/samples) ([how to download](xref:index#how-to-download-a-sample))
 
@@ -172,7 +172,7 @@ ASP.NET Core abstracts file system access through the use of File Providers. Fil
 * <xref:Microsoft.Extensions.Hosting.IHostingEnvironment> exposes the app's [content root](xref:fundamentals/index#content-root) and [web root](xref:fundamentals/index#web-root) as `IFileProvider` types.
 * [Static File Middleware](xref:fundamentals/static-files) uses File Providers to locate static files.
 * [Razor](xref:mvc/views/razor) uses File Providers to locate pages and views.
-* .NET Core tooling uses File Providers and glob patterns to specify which files should be published.
+* .NET tooling uses File Providers and glob patterns to specify which files should be published.
 
 [View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/fundamentals/file-providers/samples) ([how to download](xref:index#how-to-download-a-sample))
 

aspnetcore/fundamentals/host/generic-host.md

@@ -1,7 +1,7 @@
 ---
 title: .NET Generic Host in ASP.NET Core
 author: tdykstra
-description: Use .NET Core Generic Host in ASP.NET Core apps.  Generic Host is responsible for app startup and lifetime management.
+description: Use .NET Generic Host in ASP.NET Core apps.  Generic Host is responsible for app startup and lifetime management.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: tdykstra
 ms.custom: mvc
@@ -434,7 +434,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
 
 :::moniker range=">= aspnetcore-5.0 < aspnetcore-6.0"
 
-The ASP.NET Core templates create a .NET Core Generic Host (<xref:Microsoft.Extensions.Hosting.HostBuilder>).
+The ASP.NET Core templates create a .NET Generic Host (<xref:Microsoft.Extensions.Hosting.HostBuilder>).
 
 This article provides information on using .NET Generic Host in ASP.NET Core. For information on using .NET Generic Host in console apps, see [.NET Generic Host](/dotnet/core/extensions/generic-host).
 
@@ -952,7 +952,7 @@ public class Program
 
 :::moniker range="< aspnetcore-5.0"
 
-The ASP.NET Core templates create a .NET Core Generic Host (<xref:Microsoft.Extensions.Hosting.HostBuilder>).
+The ASP.NET Core templates create a .NET Generic Host (<xref:Microsoft.Extensions.Hosting.HostBuilder>).
 
 This article provides information on using .NET Generic Host in ASP.NET Core. For information on using .NET Generic Host in console apps, see [.NET Generic Host](/dotnet/core/extensions/generic-host).
 

aspnetcore/fundamentals/host/platform-specific-configuration.md

@@ -126,7 +126,7 @@ The app's Index page reads and renders the configuration values for the two keys
 
 ### Console app without an entry point
 
-*This approach is only available for .NET Core apps, not .NET Framework.*
+*This approach is only available for .NET apps, not .NET Framework.*
 
 A dynamic hosting startup enhancement that doesn't require a compile-time reference for activation can be provided in a console app without an entry point that contains a `HostingStartup` attribute. Publishing the console app produces a hosting startup assembly that can be consumed from the runtime store.
 
@@ -526,7 +526,7 @@ The app's Index page reads and renders the configuration values for the two keys
 
 ### Console app without an entry point
 
-*This approach is only available for .NET Core apps, not .NET Framework.*
+*This approach is only available for .NET apps, not .NET Framework.*
 
 A dynamic hosting startup enhancement that doesn't require a compile-time reference for activation can be provided in a console app without an entry point that contains a `HostingStartup` attribute. Publishing the console app produces a hosting startup assembly that can be consumed from the runtime store.
 

aspnetcore/fundamentals/http-logging/index.md

@@ -1,5 +1,5 @@
 ---
-title: HTTP logging in .NET Core and ASP.NET Core
+title: HTTP logging in .NET and ASP.NET Core
 author: tdykstra
 description: Learn how to log HTTP requests and responses.
 monikerRange: '>= aspnetcore-6.0'

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 Core 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 and reference the [Microsoft.AspNetCore.App metapackage](xref:fundamentals/metapackage-app) already include the `Microsoft.Extensions.Http` package.
 
 ## Consumption patterns
 

aspnetcore/fundamentals/index.md

@@ -137,7 +137,7 @@ ASP.NET Core provides a [configuration](xref:fundamentals/configuration/index) f
 
 By [default](xref:fundamentals/configuration/index#default), ASP.NET Core apps are configured to read from `appsettings.json`, environment variables, the command line, and more. When the app's configuration is loaded, values from environment variables override values from `appsettings.json`.
 
-For managing confidential configuration data such as passwords in the development environment, .NET Core provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
+For managing confidential configuration data such as passwords in the development environment, .NET provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
 
 For more information, see <xref:fundamentals/configuration/index>.
 

aspnetcore/fundamentals/index/includes/index3-7.md

@@ -108,7 +108,7 @@ ASP.NET Core provides a [configuration](xref:fundamentals/configuration/index) f
 
 By [default](xref:fundamentals/configuration/index#default), ASP.NET Core apps are configured to read from `appsettings.json`, environment variables, the command line, and more. When the app's configuration is loaded, values from environment variables override values from `appsettings.json`.
 
-For managing confidential configuration data such as passwords, .NET Core provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
+For managing confidential configuration data such as passwords, .NET provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
 
 For more information, see <xref:fundamentals/configuration/index>.
 
@@ -329,7 +329,7 @@ By [default](xref:fundamentals/configuration/index#default), ASP.NET Core apps a
 
 The preferred way to read related configuration values is using the [options pattern](xref:fundamentals/configuration/options). For more information, see [Bind hierarchical configuration data using the options pattern](xref:fundamentals/configuration/index#optpat).
 
-For managing confidential configuration data such as passwords, .NET Core provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
+For managing confidential configuration data such as passwords, .NET provides the [Secret Manager](xref:security/app-secrets#secret-manager). For production secrets, we recommend [Azure Key Vault](xref:security/key-vault-configuration).
 
 For more information, see <xref:fundamentals/configuration/index>.