PR Merger edits

Author: Mikejo5000

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -254,10 +254,10 @@ Starting in Visual Studio 2022 version 17.10 Preview 2, the Attach to Process di
    If you have multiple processes showing w3wp.exe, check the User Name column. In some scenarios, the User Name column shows your app pool name, such as IIS APPPOOL\DefaultAppPool. If you see the App Pool, an easy way to identify the correct process is to create a new named App Pool for the app instance you want to debug, and then you can find it easily in the User Name column.
 
    ::: moniker range=">=vs-2022"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
 
 7. Select **Attach**.

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md

@@ -242,10 +242,10 @@ Starting in Visual Studio 2022 version 17.10 Preview 2, the Attach to Process di
    If you have multiple processes showing *w3wp.exe* or *dotnet.exe*, check the **User Name** column. In some scenarios, the **User Name** column shows your app pool name, such as **IIS APPPOOL\DefaultAppPool**. If you see the App Pool, but it's not unique, create a new named App Pool for the app instance you want to debug, and then you can find it easily in the **User Name** column.
 
    ::: moniker range=">=vs-2022"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
 
 7. Select **Attach**.

docs/debugger/remote-debugging-azure.md

@@ -244,10 +244,10 @@ Starting in Visual Studio 2022 version 17.10 Preview 2, the Attach to Process di
    If you have multiple processes showing *w3wp.exe* or *dotnet.exe*, check the **User Name** column. In some scenarios, the **User Name** column shows your app pool name, such as **IIS APPPOOL\DefaultAppPool**. If you see the App Pool, but it's not unique, create a new named App Pool for the app instance you want to debug, and then you can find it easily in the **User Name** column.
 
    ::: moniker range=">=vs-2022"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2022/remote-debug-attach-to-process-aspnet-core.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![Screenshot of Attach to Process dialog](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
+   ![Screenshot of Attach to Process dialog.](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
    ::: moniker-end
 
 7. Select **Attach**.