updating for freshness

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: "11/04/2016"
+ms.date: "10/29/2018"
 ms.technology: "vs-ide-debug"
 ms.topic: "conceptual"
 f1_keywords: 
@@ -24,46 +24,47 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# View Disassembly Code in the Visual Studio Debugger
-This feature is available only if address-level debugging is enabled the **Options** dialog box, **Debugging** node. It is not available for Script or SQL debugging.  
+# 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 are 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) generated 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.
   
- In addition to assembly instructions, the **Disassembly** window can show the following optional information:  
+In addition to assembly instructions, the **Disassembly** window can show the following optional information:  
 
-- Memory address where each instruction is located. For native applications, this is the actual memory address. For Visual Basic, C#, or managed code, it is an offset from the beginning of the function.  
+- 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.  
 
 - Source code from which the assembly code derives.  
 
-- Code bytes—byte representations of the actual machine or MSIL instructions.  
+- Code bytes, that is, the byte representations of the actual machine or MSIL instructions.  
 
 - Symbol names for the memory addresses.  
 
 - Line numbers corresponding to the source code.  
 
-  Assembly-language instructions consist of mnemonics, which are abbreviations for instruction names, and symbols that represent variables, registers, and constants. Each machine-language instruction is represented by one assembly-language mnemonic, usually followed by one or more variables, registers, or constants.  
-  
-  If you cannot read assembly language and want to take full advantage of the Disassembly window, consult a good book on assembly-language programming. Assembly-language programming is beyond the scope of what we can address in this brief introduction to the Disassembly window.  
+Assembly-language instructions consist of *mnemonics*, which are abbreviations for instruction names, and *symbols* for variables, registers, and constants. Each machine-language instruction is represented by one assembly-language mnemonic optionally followed by one or more symbols.  
 
-  Because assembly code relies heavily on processor registers or, in the case of managed code, common language runtime registers, you will often find it useful to use the Disassembly window in conjunction with the Registers window, which allows you to examine register contents.  
+Assembly code relies heavily on processor registers or, for managed code, common language runtime registers. You can use the **Disassembly** window along with the **Registers** window, which allows you to examine register contents.  
 
-  You probably will never have the desire or need to view machine-code instructions in their raw, numeric form, rather than assembly language. However, if you want to do so, you can use the Memory window for that purpose or choose Code Bytes from the shortcut menu in the Disassembly window.  
+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.  
 
 > [!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 are debugging, select **Debug > Windows** and then click **Disassembly**.
+-   While you're debugging, select **Debug** > **Windows** and then select **Disassembly**.
 
 ### To turn optional information on or off  
 
--   Right-click the **Disassembly** window, and set or clear the desired options in the shortcut menu.  
+-   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, this corresponds to the CPU's program counter. This location shows the next instruction that will be executed in your program.  
+     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).  
+     For more information, see [Paging up or down in memory](../debugger/how-to-page-up-or-down-in-memory.md).  
 
-## 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)
+## 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)