fix validation issues

Author: ghogen

docs/containers/container-entry-point.md

@@ -19,6 +19,7 @@ Visual Studio uses a custom container entry point depending on the project type
 |-|-|
 | **Linux containers** | The entry point is `tail -f /dev/null`, which is an infinite wait to keep the container running. When the app is launched through the debugger, it's the debugger that is responsible to run the app (that is, `dotnet webapp.dll`). If launched without debugging, the tooling runs a `docker exec -i {containerId} dotnet webapp.dll` to run the app.|
 | **Windows containers**| The entry point is something like `C:\remote_debugger\x64\msvsmon.exe /noauth /anyuser /silent /nostatus` which runs the debugger, so it's listening for connections. This method applies when the debugger runs the app. When launched without debugging, a `docker exec` command is used. For .NET Framework web apps, the entry point is slightly different where `ServiceMonitor` is added to the command.|
+:::moniker-end
 
 :::moniker range=">=vs-2022"
 |Container type|Entry point|

docs/containers/edit-and-refresh.md

@@ -19,7 +19,7 @@ This article illustrates how to use Visual Studio to start an app in a local Doc
 If you already have a project of a supported type, Visual Studio can create a Dockerfile and configure your project to run in a container. See [Container Tools in Visual Studio](overview.md).
 
 :::moniker range=">=vs-2022"
-Also, in Visual Studio 17.10 and later, [Hot Reload](..debugger/hot-reload.md) is supported in containers.
+Also, in Visual Studio 17.10 and later, [Hot Reload](../debugger/hot-reload.md) is supported in containers.
 :::moniker-end
 
 ## Prerequisites