tweak

Author: Mikejo5000

docs/debugger/attach-to-running-processes-with-the-visual-studio-debugger.md

@@ -32,7 +32,7 @@ ms.workload:
 ---
 # Attach to running processes with the Visual Studio debugger
 
-You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select **Debug** > **Attach to Process** or press **Ctrl**+**Alt**+**P** in Visual Studio, and use the **Attach to Process** dialog to attach the debugger to the process.
+You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select **Debug** > **Attach to Process** or press **Ctrl**+**Alt**+**p** in Visual Studio, and use the **Attach to Process** dialog to attach the debugger to the process.
 
 You can use **Attach to Process** to debug running apps on local or remote computers, debug multiple processes simultaneously, debug apps that weren't created in Visual Studio, or debug any app you didn't start from Visual Studio with the debugger attached. For example, if you're running an app without the debugger and hit an exception, you can then attach the debugger to the process running the app and begin debugging.
 

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -212,7 +212,7 @@ During debugging, the **Modules** window shows the code modules the debugger is
 
 **To monitor or change symbol locations or options while debugging:**
 
-1. To open the **Modules** window, while debugging, select **Debug** > **Windows** > **Modules**.
+1. To open the **Modules** window, while debugging, select **Debug** > **Windows** > **Modules** (or press **Ctrl** + **Alt** + **U**).
 1. In the **Modules** window, right-click the **Symbol Status** or **Symbol File** headers, or any module.
 1. In the context menu, select one of the following options: