Fix other links

adegeo · adegeo · commit 1beeb09dc8b8 · 2025-08-12T17:31:54.000-07:00
diff --git a/docs/core/deploying/single-file/overview.md b/docs/core/deploying/single-file/overview.md
@@ -75,7 +75,7 @@ Publish a single file application using the [dotnet publish](../../tools/dotnet-
 dotnet publish -r linux-x64 -p:PublishSingleFile=true --self-contained false
 ```
 
-For more information, see [Publish .NET Core apps with .NET CLI](../publish-with-cli.md).
+For more information, see [.NET application publishing overview](../../deploying/index.md).
 
 # [Visual Studio](#tab/vs)
 
@@ -105,7 +105,7 @@ Visual Studio creates reusable publishing profiles that control how your applica
 
 1. Choose **Publish** to publish your app as a single file.
 
-For more information, see [Publish .NET Core apps with Visual Studio](../publish-with-vs.md).
+For more information, see[.NET application publishing overview](../../deploying/index.md).
 
 ---
 
@@ -235,7 +235,5 @@ Single file apps can be inspected using the [ILSpy tool](https://ilspy.net/). Th
 
 ## See also
 
-- [.NET Core application deployment](../index.md)
-- [Publish .NET apps with .NET CLI](../publish-with-cli.md)
-- [Publish .NET Core apps with Visual Studio](../publish-with-vs.md)
+- [.NET application publishing overview](../../deploying/index.md)
 - [`dotnet publish` command](../../tools/dotnet-publish.md)
diff --git a/docs/core/deploying/trimming/trim-self-contained.md b/docs/core/deploying/trimming/trim-self-contained.md
@@ -51,7 +51,7 @@ Trimming is only supported for self-contained apps.
 
 `dotnet publish -r win-x64 -p:PublishTrimmed=true`
 
-For more information, see [Publish .NET apps with .NET CLI](../publish-with-cli.md).
+For more information, see [.NET application publishing overview](../../deploying/index.md).
 
 ### Publish with Visual Studio
 
@@ -67,11 +67,9 @@ For more information, see [Publish .NET apps with .NET CLI](../publish-with-cli.
 
     :::image type="content" source="../media/trim-self-contained/vs-publish-trimmed.png" alt-text="Visual studio publish page with Publish Trimmed selected.":::
 
-For more information, see [Publish .NET Core apps with Visual Studio](../publish-with-vs.md).
+For more information, see [.NET application publishing overview](../../deploying/index.md).
 
 ## See also
 
-- [.NET Core application deployment](../index.md).
-- [Publish .NET apps with .NET CLI](../publish-with-cli.md).
-- [Publish .NET Core apps with Visual Studio](../publish-with-vs.md).
+- [.NET application publishing overview](../../deploying/index.md).
 - [dotnet publish command](../../tools/dotnet-publish.md).
diff --git a/docs/core/tools/dotnet-publish.md b/docs/core/tools/dotnet-publish.md
@@ -38,7 +38,7 @@ dotnet publish -h|--help
 - A *.runtimeconfig.json* file that specifies the shared runtime that the application expects, as well as other configuration options for the runtime (for example, garbage collection type).
 - The application's dependencies, which are copied from the NuGet cache into the output folder.
 
-The `dotnet publish` command's output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution. It's the only officially supported way to prepare the application for deployment. Depending on the type of deployment that the project specifies, the hosting system may or may not have the .NET shared runtime installed on it. For more information, see [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md).
+The `dotnet publish` command's output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution. It's the only officially supported way to prepare the application for deployment. Depending on the type of deployment that the project specifies, the hosting system may or may not have the .NET shared runtime installed on it. For more information, see [.NET application publishing overview](../deploying/index.md).
 
 ### Implicit restore
 
@@ -196,7 +196,7 @@ For more information, see the following resources:
 
 - **`--sc|--self-contained [true|false]`**
 
-  Publishes the .NET runtime with your application so the runtime doesn't need to be installed on the target machine. Default is `true` if a runtime identifier is specified and the project is an executable project (not a library project). For more information, see [.NET application publishing](../deploying/index.md) and [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md).
+  Publishes the .NET runtime with your application so the runtime doesn't need to be installed on the target machine. Default is `true` if a runtime identifier is specified and the project is an executable project (not a library project). For more information, see [Self-contained deployment](../deploying/index.md#self-contained-deployment).
 
   If this option is used without specifying `true` or `false`, the default is `true`. In that case, don't put the solution or project argument immediately after `--self-contained`, because `true` or `false` is expected in that position.
 
@@ -210,7 +210,7 @@ For more information, see the following resources:
 
 - **`-r|--runtime <RUNTIME_IDENTIFIER>`**
 
-  Publishes the application for a given runtime. For a list of Runtime Identifiers (RIDs), see the [RID catalog](../rid-catalog.md). For more information, see [.NET application publishing](../deploying/index.md) and [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md). If you use this option, use `--self-contained` or `--no-self-contained` also.
+  Publishes the application for a given runtime. For a list of Runtime Identifiers (RIDs), see the [RID catalog](../rid-catalog.md). For more information, see [.NET application publishing overview](../deploying/index.md). If you use this option, use `--self-contained` or `--no-self-contained` also.
 
 [!INCLUDE [tl](../../../includes/cli-tl.md)]
 
@@ -271,7 +271,6 @@ For more information, see the following resources:
 ## See also
 
 - [.NET application publishing overview](../deploying/index.md)
-- [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md)
 - [Target frameworks](../../standard/frameworks.md)
 - [Runtime Identifier (RID) catalog](../rid-catalog.md)
 - [Containerize a .NET app with dotnet publish](../containers/sdk-publish.md)
diff --git a/docs/core/tutorials/publishing-with-visual-studio-code.md b/docs/core/tutorials/publishing-with-visual-studio-code.md
@@ -62,11 +62,11 @@ In the following steps, you'll look at the files created by the publish process.
 
    - *HelloWorld.dll*
 
-      This is the [framework-dependent deployment](../deploying/publish-with-cli.md#framework-dependent-deployment) version of the application. To run this dynamic link library, enter `dotnet HelloWorld.dll` at a command prompt. This method of running the app works on any platform that has the .NET runtime installed.
+      This is the [framework-dependent deployment](../deploying/index.md#cross-platform-dll-deployment) version of the application. To run this dynamic link library, enter `dotnet HelloWorld.dll` at a command prompt. This method of running the app works on any platform that has the .NET runtime installed.
 
    - *HelloWorld.exe* (*HelloWorld* on Linux or macOS.)
 
-      This is the [framework-dependent executable](../deploying/publish-with-cli.md#framework-dependent-executable) version of the application. The file is operating-system-specific.
+   This is the [framework-dependent executable](../deploying/index.md#framework-dependent-deployment) version of the application. The file is operating-system-specific.
 
    - *HelloWorld.pdb* (optional for deployment)
 
@@ -98,8 +98,7 @@ In the following steps, you'll look at the files created by the publish process.
 
 ## Additional resources
 
-- [.NET application deployment](../deploying/index.md)
-- [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md)
+- [.NET application publishing overview](../deploying/index.md)
 - [`dotnet publish`](../tools/dotnet-publish.md)
 - [Use the .NET SDK in continuous integration (CI) environments](../../devops/dotnet-cli-and-continuous-integration.md)
 
diff --git a/docs/core/tutorials/publishing-with-visual-studio.md b/docs/core/tutorials/publishing-with-visual-studio.md
@@ -104,8 +104,7 @@ In the following steps, you'll look at the files created by the publish process.
 
 ## Additional resources
 
-- [.NET application deployment](../deploying/index.md)
-- [Publish .NET apps with the .NET CLI](../deploying/publish-with-cli.md)
+- [.NET application publishing overview](../deploying/index.md)
 - [`dotnet publish`](../tools/dotnet-publish.md)
 - [Tutorial: Publish a .NET console application using Visual Studio Code](publishing-with-visual-studio-code.md)
 - [Use the .NET SDK in continuous integration (CI) environments](../../devops/dotnet-cli-and-continuous-integration.md)
diff --git a/docs/core/whats-new/dotnet-9/runtime.md b/docs/core/whats-new/dotnet-9/runtime.md
@@ -74,7 +74,7 @@ CET imposes some limitations on CET-enabled processes and can result in a small
 
 ## .NET install search behavior
 
-.NET apps can now be configured for how they should [search for the .NET runtime](../../deploying/publish-with-cli.md#configure-net-install-search-behavior). This capability can be used with private runtime installations or to more strongly control the execution environment.
+.NET apps can now be configured for how they should [search for the .NET runtime](../../deploying/index.md#configure-net-install-search-behavior). This capability can be used with private runtime installations or to more strongly control the execution environment.
 
 ## Performance improvements
 
