Clarify the publishing articles by removing "deploy" where appropriate and merge similar info

.openpublishing.redirection.core.json

@@ -386,6 +386,14 @@
             "source_path_from_root": "/docs/core/deploying/applications.md",
             "redirect_url": "/dotnet/core/deploying/index"
         },
+        {
+            "source_path_from_root": "/docs/core/deploying/deploy-with-cli.md",
+            "redirect_url": "/dotnet/core/deploying/index"
+        },
+        {
+            "source_path_from_root": "/docs/core/deploying/deploy-with-vs.md",
+            "redirect_url": "/dotnet/core/deploying/index"
+        },
         {
             "source_path_from_root": "/docs/core/deploying/fixing-warnings.md",
             "redirect_url": "/dotnet/core/deploying/trimming/fixing-warnings",

docs/architecture/microservices/multi-container-microservice-net-applications/multi-container-applications-docker-compose.md

@@ -457,7 +457,7 @@ The .NET team provides some basic variants in [dotnet/](https://hub.docker.com/r
 - **sdk**: for development and build scenarios
 - **aspnet**: for ASP.NET production scenarios
 - **runtime**: for .NET production scenarios
-- **runtime-deps**: for production scenarios of [self-contained applications](../../../core/deploying/index.md#publish-self-contained)
+- **runtime-deps**: for production scenarios of [self-contained applications](../../../core/deploying/index.md#self-contained-deployment)
 
 For faster startup, runtime images also automatically set aspnetcore\_urls to port 80 and use Ngen to create a native image cache of assemblies.
 

docs/core/compatibility/sdk/6.0/apphost-generated-for-macos.md

@@ -5,7 +5,7 @@ ms.date: 07/13/2021
 ---
 # Generate apphost for macOS
 
-When building on macOS, the .NET SDK now [produces an executable](../../../deploying/index.md#produce-an-executable) for app projects.
+When building on macOS, the .NET SDK now produces an executable for app projects.
 
 Since .NET Core 3.0, the .NET SDK has created an executable for app projects when building on non-macOS operating systems. However, it did not create an executable on macOS since we weren't signing this binary. That resulted in an app that was recognized as dangerous by the OS, which made it hard for the user to run it. The .NET 6 SDK can sign the app executable, so it now produces the executable by default.
 

docs/core/compatibility/sdk/8.0/arch-option.md

@@ -5,7 +5,7 @@ ms.date: 10/05/2023
 ---
 # --arch option doesn't imply self-contained
 
-Up until now, the `--arch` option for `dotnet` CLI commands such as [dotnet publish](../../../tools/dotnet-publish.md) implied that the app was [self-contained](../../../deploying/index.md#publish-self-contained). The behavior of the `--arch` option has now been changed to match that of the `--runtime` option, and it no longer implies that an app is self-contained.
+Up until now, the `--arch` option for `dotnet` CLI commands such as [dotnet publish](../../../tools/dotnet-publish.md) implied that the app was [self-contained](../../../deploying/index.md#self-contained-deployment). The behavior of the `--arch` option has now been changed to match that of the `--runtime` option, and it no longer implies that an app is self-contained.
 
 ## Previous behavior
 

docs/core/compatibility/sdk/8.0/runtimespecific-app-default.md

@@ -5,7 +5,7 @@ ms.date: 06/05/2023
 ---
 # Runtime-specific apps no longer self-contained
 
-Runtime-specific apps, or .NET apps with a `RuntimeIdentifier`, are no longer [self-contained](../../../deploying/index.md#publish-self-contained) by default. Instead, they are [framework-dependent](../../../deploying/index.md#publish-framework-dependent) by default.
+Runtime-specific apps, or .NET apps with a `RuntimeIdentifier`, are no longer [self-contained](../../../deploying/index.md#self-contained-deployment) by default. Instead, they are [framework-dependent](../../../deploying/index.md#framework-dependent-deployment) by default.
 
 This is a breaking change in the following situations: