drop core (#6939)

fix #6910

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>

6 files changed, 17 insertions, 17 deletions

diff --git a/Documentation/contributing/maintainers.md b/Documentation/contributing/maintainers.md
index 81eebc69..cca024d6 100644
--- a/Documentation/contributing/maintainers.md
+++ b/Documentation/contributing/maintainers.md
@@ -1,6 +1,6 @@
 # What you can expect from Maintainers
 
-The .NET Core maintainer team aims to support a productive and safe working environment for everyone participating in .NET repositories. You can expect maintainers to do three things to that end: respect your contributions, make engagement efficient, and report potential .NET Foundation Code of Conduct violations.
+The .NET maintainer team aims to support a productive and safe working environment for everyone participating in .NET repositories. You can expect maintainers to do three things to that end: respect your contributions, make engagement efficient, and report potential .NET Foundation Code of Conduct violations.
 
 The following two lists summarize how maintainers will act. A more detailed description follows this summary.
 
diff --git a/Documentation/core-repos.md b/Documentation/core-repos.md
index 7fa0fe58..511e001c 100644
--- a/Documentation/core-repos.md
+++ b/Documentation/core-repos.md
@@ -1,22 +1,22 @@
 # .NET repositories
 
-.NET Core consists of many repositories. To file an issue, make a PR, or engage on specific topics, it's best to engage with developers working in the correct repo. A largely complete set of .NET Core and related repositories follows.
+.NET consists of many repositories. To file an issue, make a PR, or engage on specific topics, it's best to engage with developers working in the correct repo. A largely complete set of .NET and related repositories follows.
 
-## .NET Core
+## .NET
 
 |Repository                                                          |Description |
 |--------------------------------------------------------------------|------------|
-|[dotnet/core](https://github.com/dotnet/core)                       |.NET Core home repository|
-|[dotnet/runtime](https://github.com/dotnet/runtime)                 |.NET Core runtime, runtime installers, application model, & Base Class Library (BCL)|
+|[dotnet/core](https://github.com/dotnet/core)                       |.NET home repository|
+|[dotnet/runtime](https://github.com/dotnet/runtime)                 |.NET runtime, runtime installers, application model, & Base Class Library (BCL)|
 |[dotnet/docs](https://github.com/dotnet/docs)                       |.NET documentation|
 |[dotnet/dotnet-api-docs](https://github.com/dotnet/dotnet-api-docs) |.NET API documentation|
 |[dotnet/project-system](https://github.com/dotnet/project-system)   |Visual Studio project system for C#, F#, & VB|
-|[dotnet/sdk](https://github.com/dotnet/sdk)                         |.NET Core SDK (used by Visual Studio & .NET Core CLI)|
-|[dotnet/installer](https://github.com/dotnet/installer)             |.NET Core installer (produces zips, tarballs, and installers for the .NET SDK)
+|[dotnet/sdk](https://github.com/dotnet/sdk)                         |.NET SDK (used by Visual Studio & .NET CLI)|
+|[dotnet/installer](https://github.com/dotnet/installer)             |.NET installer (produces zips, tarballs, and installers for the .NET SDK)
 |[dotnet/extensions](https://github.com/dotnet/extensions)           |.NET extension APIs (DI, logging, configuration, etc.)|
-|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker)     |.NET Core Docker images|
+|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker)     |.NET Docker images|
 |[dotnet/templating](https://github.com/dotnet/templating)           |Templating engine used by `dotnet new`|
-|[dotnet/test-templates](https://github.com/dotnet/test-templates)   |.NET Core unit testing project templates|
+|[dotnet/test-templates](https://github.com/dotnet/test-templates)   |.NET unit testing project templates|
 |[dotnet/winforms](https://github.com/dotnet/winforms)               |Windows Forms|
 |[dotnet/wpf](https://github.com/dotnet/wpf)                         |Windows Presentation Foundation (WPF)|
 |[dotnet/maui](https://github.com/dotnet/maui)                       |.NET Multi-platform App UI|
diff --git a/Documentation/diagnostics/portable_pdb.md b/Documentation/diagnostics/portable_pdb.md
index becb7682..16071258 100644
--- a/Documentation/diagnostics/portable_pdb.md
+++ b/Documentation/diagnostics/portable_pdb.md
@@ -1,13 +1,13 @@
 # Portable PDB #
 
-.NET Core introduces a new symbol file (PDB) format - portable PDBs. Unlike traditional PDBs which are Windows-only, portable PDBs can be created and read on all platforms.
+.NET introduces a new symbol file (PDB) format - portable PDBs. Unlike traditional PDBs which are Windows-only, portable PDBs can be created and read on all platforms.
 
 ## What is a PDB? ##
 For anyone not familiar, a PDB file is an auxiliary file produced by a compiler to provide other tools, especially debuggers, information about what is in the main executable file and how it was produced. For example, a debugger reads a PDB to map foo.cs line 12 to the right executable location so that it can set a breakpoint.
 The Windows PDB format has been around a long time now (~25 years), and it evolved from other native debugging symbol formats which were even older. It started out its life as a format for native (C/C++) programs. For the first release of the .NET Framework, the Windows PDB format was extended to support .NET.
 
 ## Why a new format? ##
-While the Windows PDB format has worked okay over the years, with .NET Core the [Roslyn](https://github.com/dotnet/roslyn/wiki/Roslyn%20Overview) team decided it was time to go back to the drawing board and come up with a new format. A few of the reasons:
+While the Windows PDB format has worked okay over the years, with .NET the [Roslyn](https://github.com/dotnet/roslyn/wiki/Roslyn%20Overview) team decided it was time to go back to the drawing board and come up with a new format. A few of the reasons:
 
 * The Windows PDB format is complex, and not well documented. This complexity is important for some of the native code scenarios that the format was designed for, but it is unnecessary for the .NET scenarios. The portable format is [open source](https://github.com/dotnet/symreader-portable) and [documented](https://github.com/dotnet/runtime/blob/main/docs/design/specs/PortablePdb-Metadata.md).
 * At the time the effort was begun there wasn't a cross-platform library that could read or write the original windows PDB format.
diff --git a/Documentation/microsoft-team.md b/Documentation/microsoft-team.md
index d4c64c69..5467ad62 100644
--- a/Documentation/microsoft-team.md
+++ b/Documentation/microsoft-team.md
@@ -17,7 +17,7 @@ You need to join teams in two organizations. Click the two links:
 
 After you join the teams:
 
-* Users will be able to @mention you on [.NET Core Repos](https://github.com/dotnet/core/blob/main/Documentation/core-repos.md)
+* Users will be able to @mention you on [.NET Repos](https://github.com/dotnet/core/blob/main/Documentation/core-repos.md)
 * You will be able to access to private repos we maintain
 * You will get write access to a subset of repos
 
@@ -89,5 +89,5 @@ Service accounts should also be linked. For more details, see [Service accounts
 
 ## Guidelines
 
-* [Contributing to .NET Core](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
+* [Contributing to .NET](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
 * [What you can expect from Maintainers](https://github.com/dotnet/core/blob/main/Documentation/contributing/maintainers.md)
diff --git a/Documentation/official-docs.md b/Documentation/official-docs.md
index 55e9c5cc..cebb7656 100644
--- a/Documentation/official-docs.md
+++ b/Documentation/official-docs.md
@@ -1,8 +1,8 @@
 # Official Microsoft Docs
 
-Microsoft maintains official documentation for .NET, listed below. Both .NET Core and .NET Framework docs are relevant to .NET Core developers, both because many .NET Framework APIs are part of .NET Core (most relevant for .NET Core 2.0) but also because you can reference .NET Framework libraries with .NET Standard 2.0.
+Microsoft maintains official documentation for .NET, listed below. Both .NET and .NET Framework docs are relevant to .NET developers, both because many .NET Framework APIs are part of .NET (most relevant for .NET Core 2.0) but also because you can reference .NET Framework libraries with .NET Standard 2.0.
 
-## .NET Core
+## .NET
 
 - [Conceptual docs](https://docs.microsoft.com/dotnet/core/)
 - [API docs](https://docs.microsoft.com/dotnet/api/)
diff --git a/Documentation/prereqs.md b/Documentation/prereqs.md
index 914429d9..b5fbea20 100644
--- a/Documentation/prereqs.md
+++ b/Documentation/prereqs.md
@@ -1,7 +1,7 @@
-.NET Core native prerequisites
+.NET native prerequisites
 ==============================
 
 * [Windows Prerequisites](https://docs.microsoft.com/dotnet/core/install/windows)
 * [macOS Prerequisites](https://docs.microsoft.com/dotnet/core/install/macos)
 * [Linux Prerequisites](https://docs.microsoft.com/dotnet/core/install/linux)
-* [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)
+* [.NET Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)