From e5c733037d1a27eaf2316c587cb2a722d6e4c204 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 5 Feb 2026 18:33:21 +0000
Subject: [PATCH 1/2] Initial plan


From 9815e8c8a9f162aa68b45f82cdd8c845057711bf Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 5 Feb 2026 18:34:35 +0000
Subject: [PATCH 2/2] Fix heading dash formatting to comply with style guide

Co-authored-by: adegeo <67293991+adegeo@users.noreply.github.com>
---
 docs/core/deploying/runtime-store.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/core/deploying/runtime-store.md b/docs/core/deploying/runtime-store.md
index 7a5a4be4a073e..45446031017f1 100644
--- a/docs/core/deploying/runtime-store.md
+++ b/docs/core/deploying/runtime-store.md
@@ -136,7 +136,7 @@ An alternative to specifying target manifests with the [`dotnet publish`](../too
 
 Specify the target manifests in the project file only when the target environment for the app is well-known, such as for .NET Core projects. This isn't the case for open-source projects. The users of an open-source project typically deploy it to different production environments. These production environments generally have different sets of packages pre-installed. You can't make assumptions about the target manifest in such environments, so you should use the `--manifest` option of [`dotnet publish`](../tools/dotnet-publish.md).
 
-## ASP.NET Core implicit store (.NET Core 2.0 only - Legacy)
+## ASP.NET Core implicit store (.NET Core 2.0, legacy)
 
 > [!NOTE]
 > This section describes legacy functionality that only applied to .NET Core 2.0. This feature is no longer relevant for modern .NET applications.