Skip to content

Fix heading dash formatting in runtime-store.md #51530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adegeo merged 2 commits into from
Feb 5, 2026
Merged

Fix heading dash formatting in runtime-store.md #51530

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e5c7330
Initial plan
Copilot Feb 5, 2026
9815e8c
Fix heading dash formatting to comply with style guide
Copilot Feb 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core/deploying/runtime-store.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down