Replace .NET Core with .NET in performance documentation

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

Author: Copilot

aspnetcore/performance/caching/distributed.md

@@ -128,9 +128,9 @@ The sample app implements <xref:Microsoft.Extensions.Caching.SqlServer.SqlServer
 
 ### Distributed NCache Cache
 
-[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET Core. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
+[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
 
-To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET Core)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
+To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
 
 To configure NCache:
 

aspnetcore/performance/caching/distributed/includes/distributed5.md

@@ -107,9 +107,9 @@ See [this GitHub issue](https://github.com/dotnet/AspNetCore.Docs/issues/19542)
 
 ### Distributed NCache Cache
 
-[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET Core. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
+[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
 
-To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET Core)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
+To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
 
 To configure NCache:
 

aspnetcore/performance/caching/distributed/includes/distributed6-7.md

@@ -111,9 +111,9 @@ The sample app implements <xref:Microsoft.Extensions.Caching.SqlServer.SqlServer
 
 ### Distributed NCache Cache
 
-[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET Core. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
+[NCache](https://github.com/Alachisoft/NCache) is an open source in-memory distributed cache developed natively in .NET and .NET. NCache works both locally and configured as a distributed cache cluster for an ASP.NET Core app running in Azure or on other hosting platforms.
 
-To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET Core)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
+To install and configure NCache on your local machine, see [Getting Started Guide for Windows (.NET and .NET)](https://www.alachisoft.com/resources/docs/ncache/getting-started-guide-windows/).
 
 To configure NCache:
 

aspnetcore/performance/diagnostic-tools.md

@@ -59,13 +59,13 @@ For more about PerfView, see the user's guide available in the tool or [on GitHu
 
 While PerfView is a useful performance analysis tool for .NET scenarios, it only runs on Windows, so you can't use it to collect traces from ASP.NET Core apps running in Linux environments.
 
-[PerfCollect](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/linux-performance-tracing.md) is a bash script that uses native Linux profiling tools ([Perf](https://perf.wiki.kernel.org/index.php/Main_Page) and [LTTng](https://lttng.org/)) to collect traces on Linux that can be analyzed by PerfView. PerfCollect is useful when performance problems show up in Linux environments where PerfView can't be used directly. Instead, PerfCollect can collect traces from .NET Core apps that are then analyzed on a Windows computer using PerfView.
+[PerfCollect](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/linux-performance-tracing.md) is a bash script that uses native Linux profiling tools ([Perf](https://perf.wiki.kernel.org/index.php/Main_Page) and [LTTng](https://lttng.org/)) to collect traces on Linux that can be analyzed by PerfView. PerfCollect is useful when performance problems show up in Linux environments where PerfView can't be used directly. Instead, PerfCollect can collect traces from .NET apps that are then analyzed on a Windows computer using PerfView.
 
 More information about how to install and get started with PerfCollect is available [on GitHub](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/linux-performance-tracing.md).
 
 ## Other Third-party Performance Tools
 
-The following lists some third-party performance tools that are useful in performance investigation of .NET Core applications.
+The following lists some third-party performance tools that are useful in performance investigation of .NET applications.
 
 * [MiniProfiler](https://miniprofiler.com/)
 * [dotTrace](https://www.jetbrains.com/profiler/) and [dotMemory](https://www.jetbrains.com/dotmemory/) from [JetBrains](https://www.jetbrains.com/)

aspnetcore/performance/memory.md

@@ -13,10 +13,10 @@ By [Sébastien Ros](https://github.com/sebastienros) and [Rick Anderson](https:/
 
 Memory management is complex, even in a managed framework like .NET. Analyzing and understanding memory issues can be challenging. This article:
 
-* Was motivated by many *memory leak* and *GC not working* issues. Most of these issues were caused by not understanding how memory consumption works in .NET Core, or not understanding how it's measured.
+* Was motivated by many *memory leak* and *GC not working* issues. Most of these issues were caused by not understanding how memory consumption works in .NET, or not understanding how it's measured.
 * Demonstrates problematic memory use, and suggests alternative approaches.
 
-## How garbage collection (GC) works in .NET Core
+## How garbage collection (GC) works in .NET
 
 The GC allocates heap segments where each segment is a contiguous range of memory. Objects placed in the heap are categorized into one of 3 generations: 0, 1, or 2. The generation determines the frequency the GC attempts to release memory on managed objects that are no longer referenced by the app. Lower numbered generations are GC'd more frequently.
 
@@ -186,7 +186,7 @@ Some scenarios, such as caching, require object references to be held until memo
 
 ### Native memory
 
-Some .NET Core objects rely on native memory. Native memory can **not** be collected by the GC. The .NET object using native memory must free it using native code.
+Some .NET objects rely on native memory. Native memory can **not** be collected by the GC. The .NET object using native memory must free it using native code.
 
 .NET provides the <xref:System.IDisposable> interface to let developers release native memory. Even if <xref:System.IDisposable.Dispose%2A> is not called, correctly implemented classes call `Dispose` when the [finalizer](/dotnet/csharp/programming-guide/classes-and-structs/destructors) runs.
 
@@ -236,7 +236,7 @@ GC.Collect();
 
 See <xref:System.Runtime.GCSettings.LargeObjectHeapCompactionMode> for information on compacting the LOH.
 
-In containers using .NET Core 3.0 or later, the LOH is automatically compacted.
+In containers using .NET 3.0 or later, the LOH is automatically compacted.
 
 The following API that illustrates this behavior: