addressed peer review comments

Author: WilliamAntonRohm

docs/debugger/how-to-use-the-disassembly-window.md

@@ -1,7 +1,7 @@
 ---
 title: "View Disassembly Code in the Debugger in Visual Studio | Microsoft Docs"
 ms.custom: "H1Hack27Feb2017"
-ms.date: "10/29/2018"
+ms.date: "10/30/2018"
 ms.technology: "vs-ide-debug"
 ms.topic: "conceptual"
 f1_keywords: 
@@ -25,13 +25,14 @@ ms.workload:
   - "multiple"
 ---
 # View disassembly code in the Visual Studio debugger
-This feature is only available if address-level debugging is enabled in the **Options** dialog box, **Debugging** node. It isn't available for Script or SQL debugging.  
-  
-The **Disassembly** window shows assembly code corresponding to the instructions created by the compiler. If you're debugging managed code, these assembly instructions correspond to the native code created by the Just-in-Time (JIT) compiler, not the Microsoft intermediate language (MSIL) created by the Visual Studio compiler.  
 
+The **Disassembly** window shows assembly code corresponding to the instructions created by the compiler. If you're debugging managed code, these assembly instructions correspond to the native code created by the Just-in-Time (JIT) compiler, not the Microsoft intermediate language (MSIL) created by the Visual Studio compiler.  
+  
 > [!NOTE]
-> To take full advantage of the **Disassembly** window, you'll need to understand the basics of assembly-language programming, which is beyond the scope of this article.
+> To take full advantage of the **Disassembly** window, understand or learn the basics of [assembly-language programming](https://wikipedia.org/wiki/Assembly_language).
   
+This feature is only available if address-level debugging is enabled. It isn't available for script or SQL debugging. 
+
 In addition to assembly instructions, the **Disassembly** window can show the following optional information:  
 
 - Memory address where each instruction is located. For native applications, it is the actual memory address. For Visual Basic, C#, or managed code, it's an offset from the beginning of the function.  
@@ -50,21 +51,21 @@ Assembly code relies heavily on processor registers or, for managed code, common
 
 To view machine-code instructions in their raw numeric form, rather than as assembly language, use the **Memory** window or select **Code Bytes** from the shortcut menu in the **Disassembly** window.  
 
+## Use the Disassembly window
+
+To enable the **Disassembly** window, under **Tools** > **Options** (or **Tools** > **Options**) > **Debugging**, select **Enable address-level debugging**.
+
+To open the **Disassembly** window during debugging, select **Windows** > **Disassembly** or press **Alt**+**8**.
+
 > [!NOTE]
 >  The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](../ide/personalizing-the-visual-studio-ide.md).  
   
-### To display the Disassembly window  
-  
--   While you're debugging, select **Debug** > **Windows** and then select **Disassembly**.
-  
-### To turn optional information on or off  
-  
--   Right-click in the **Disassembly** window, and set or clear the desired options in the shortcut menu.  
-  
-     A yellow arrow in the left margin marks the location of the current execution point. For native code, the execution point corresponds to the CPU's program counter. This location shows the next instruction that will be executed in your program.  
-  
-     For more information, see [Paging up or down in memory](../debugger/how-to-page-up-or-down-in-memory.md).  
-  
+To turn optional information on or off, right-click in the **Disassembly** window, and set or clear the desired options in the shortcut menu.  
+
+A yellow arrow in the left margin marks the current execution point. For native code, the execution point corresponds to the CPU's program counter. This location shows the next instruction that will be executed in your program.  
+
 ## See also  
- [Viewing data in the debugger](../debugger/viewing-data-in-the-debugger.md)   
- [How to: Use the Registers window](../debugger/how-to-use-the-registers-window.md)
+
+[Paging up or down in memory](../debugger/how-to-page-up-or-down-in-memory.md)
+[Viewing data in the debugger](../debugger/viewing-data-in-the-debugger.md)
+[How to: Use the Registers window](../debugger/how-to-use-the-registers-window.md)