customizing the data

Author: Mikejo5000

docs/debugger/debugger-tips-and-tricks.md

@@ -47,6 +47,10 @@ If it is difficult or time-consuming to recreate a particular state in your app,
 
 3. If you are interested in another type of condition, select **Filter** instead of **Conditional expression** in the **Breakpoint Settings** dialog box, and then follow the filter tips.
 
+## Configure the data to show in the debugger
+
+For C#, Visual Basic, and C++/CLI code, you can tell the debugger what information to show using the [DebuggerDisplay](../debugger/using-the-debuggerdisplay-attribute.md) attribute. For C++ code, you can do the same using [Natvis visualizations](create-custom-views-of-native-objects.md).
+
 ## Change the execution flow
 
 With the debugger paused on a line of code, use the mouse to grab the yellow arrow pointer on the left. Move the yellow arrow pointer to a different point in the code execution path. Then you use F5 or a step command to continue running the app.

docs/debugger/toc.yml

@@ -201,18 +201,18 @@
     - name: Create custom views of data
       href: viewing-data-in-the-debugger.md
       items:
-      - name: Create custom views of native objects
+      - name: Create custom views of C++ objects
         href: create-custom-views-of-native-objects.md
         items:
         - name: "Visual C++ custom visualizer compatibility"
           href: visual-cpp-custom-visualizer-compatibility.md
       - name: Create custom views of managed objects
         href: create-custom-views-of-dot-managed-objects.md
         items:
-        - name: Use DebuggerTypeProxy attribute
-          href: using-debuggertypeproxy-attribute.md
-        - name: Use the DebuggerDisplay attribute
+        - name: Tell the debugger what to show
           href: using-the-debuggerdisplay-attribute.md
+        - name: Tell the debugger what type to show
+          href: using-debuggertypeproxy-attribute.md
       - name: Create custom visualizers of data
         href: create-custom-visualizers-of-data.md
         items:

docs/debugger/using-breakpoints.md

@@ -170,13 +170,13 @@ Data breakpoints in .NET Core won't work for:
 
 **To set a data breakpoint:**
 
-1.  In a C++ project, start debugging, and wait until a breakpoint is reached. On the **Debug** menu, choose **New Breakpoint** > **Data Breakpoint**
+1. In a C++ project, start debugging, and wait until a breakpoint is reached. On the **Debug** menu, choose **New Breakpoint** > **Data Breakpoint**
 
     You can also select **New** > **Data Breakpoint** in the **Breakpoints** window or right-click an item in the **Autos**, **Watch**, or **Locals** window and select **Break when value changes**in the context menu.
 
-2.  In the **Address** box, type a memory address, or an expression that evaluates to a memory address. For example, type `&avar` to break when the contents of the variable `avar` changes.
+2. In the **Address** box, type a memory address, or an expression that evaluates to a memory address. For example, type `&avar` to break when the contents of the variable `avar` changes.
 
-3.  In the **Byte Count** dropdown, select the number of bytes you want the debugger to watch. For example, if you select **4**, the debugger will watch the four bytes starting at `&avar` and break if any of those bytes change value.
+3. In the **Byte Count** dropdown, select the number of bytes you want the debugger to watch. For example, if you select **4**, the debugger will watch the four bytes starting at `&avar` and break if any of those bytes change value.
 
 Data breakpoints don't work under the following conditions:
 -   A process that is not being debugged writes to the memory location.

docs/debugger/using-debuggertypeproxy-attribute.md

@@ -1,5 +1,5 @@
 ---
-title: "Using DebuggerTypeProxy Attribute | Microsoft Docs"
+title: "Display custom type using DebuggerTypeProxy | Microsoft Docs"
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 dev_langs:
@@ -18,7 +18,7 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Using DebuggerTypeProxy Attribute (C#, Visual Basic, C++/CLI)
+# Tell the debugger what type to show using DebuggerTypeProxy Attribute (C#, Visual Basic, C++/CLI)
 
 <xref:System.Diagnostics.DebuggerTypeProxyAttribute> specifies a proxy, or stand-in, for a type and changes the way the type is displayed in debugger windows. When you view a variable that has a proxy, the proxy stands in for the original type in the **display**. The debugger variable window displays only the public members of the proxy type. Private members are not displayed.
 

docs/debugger/using-the-debuggerdisplay-attribute.md

@@ -1,5 +1,5 @@
 ---
-title: "Using the DebuggerDisplay Attribute | Microsoft Docs"
+title: "Display custom info using DebuggerDisplay | Microsoft Docs"
 ms.date: "01/09/2019"
 ms.topic: "conceptual"
 helpviewer_keywords:
@@ -13,7 +13,7 @@ manager: jillfra
 ms.workload:
   - "multiple"
 ---
-# Using the DebuggerDisplay Attribute (C#, Visual Basic, F#, C++/CLI)
+# Tell the debugger what to show using the DebuggerDisplay Attribute (C#, Visual Basic, F#, C++/CLI)
 The <xref:System.Diagnostics.DebuggerDisplayAttribute> controls how an object, property, or field is displayed in the debugger variable windows. This attribute can be applied to types, delegates, properties, fields, and assemblies.
 
 The `DebuggerDisplay` attribute has a single argument, which is a string to be displayed in the value column for instances of the type. This string can contain braces (`{` and `}`). Text within a pair of braces is evaluated as a field, property or method.