Revise debugger_visualizer text

Author: traviscross

src/attributes/debugger.md

@@ -3,12 +3,12 @@ r[attributes.debugger]
 
 The following [attributes] are used for enhancing the debugging experience when using third-party debuggers like GDB or WinDbg.
 
+<!-- template:attributes -->
 r[attributes.debugger.debugger_visualizer]
 ## The `debugger_visualizer` attribute
 
 r[attributes.debugger.debugger_visualizer.intro]
-The *`debugger_visualizer` [attribute][attributes]* can be used to embed a debugger visualizer file into the debug information.
-This enables an improved debugger experience for displaying values in the debugger.
+The *`debugger_visualizer` [attribute][attributes]* can be used to embed a debugger visualizer file into the debug information. This improves the debugger experience when displaying values.
 
 > [!EXAMPLE]
 > <!-- ignore: requires external files-->
@@ -24,26 +24,25 @@ The `debugger_visualizer` attribute uses the [MetaListNameValueStr] syntax to sp
 - [`gdb_script_file`][attributes.debugger.debugger_visualizer.gdb]
 
 r[attributes.debugger.debugger_visualizer.allowed-positions]
-The `debugger_visualizer` attribute may only be specified on a [module] or crate root.
+The `debugger_visualizer` attribute may only be applied to a [module] or to the crate root.
 
 r[attributes.debugger.debugger_visualizer.duplicates]
-Duplicate instances of the `debugger_visualizer` attribute will load all of the specified visualizers.
+The `debugger_visualizer` attribute may be used any number of times on a form. All specified visualizer files will be loaded.
 
 r[attributes.debugger.debugger_visualizer.natvis]
 ### Using `debugger_visualizer` with Natvis
 
 r[attributes.debugger.debugger_visualizer.natvis.intro]
-Natvis is an XML-based framework for Microsoft debuggers (such as Visual Studio and WinDbg) that uses declarative rules to customize the display of types.
-For detailed information on the Natvis format, refer to Microsoft's [Natvis documentation].
+Natvis is an XML-based framework for Microsoft debuggers (such as Visual Studio and WinDbg) that uses declarative rules to customize the display of types. For detailed information on the Natvis format, refer to Microsoft's [Natvis documentation].
 
 r[attributes.debugger.debugger_visualizer.natvis.msvc]
 This attribute only supports embedding Natvis files on `-windows-msvc` targets.
 
 r[attributes.debugger.debugger_visualizer.natvis.path]
-The path to the Natvis file is specified with the `natvis_file` key, which is a path relative to the crate source file.
+The path to the Natvis file is specified with the `natvis_file` key, which is a path relative to the source file.
 
 > [!EXAMPLE]
-> <!-- ignore: requires external files, and msvc -->
+> <!-- ignore: requires external files and msvc -->
 > ```rust ignore
 > #![debugger_visualizer(natvis_file = "Rectangle.natvis")]
 >
@@ -60,7 +59,7 @@ The path to the Natvis file is specified with the `natvis_file` key, which is a
 > }
 > ```
 >
-> and `Rectangle.natvis` contains:
+> `Rectangle.natvis` contains:
 >
 > ```xml
 > <?xml version="1.0" encoding="utf-8"?>
@@ -100,17 +99,18 @@ r[attributes.debugger.debugger_visualizer.gdb]
 ### Using `debugger_visualizer` with GDB
 
 r[attributes.debugger.debugger_visualizer.gdb.pretty]
-GDB supports the use of a structured Python script, called a *pretty printer*, that describes how a type should be visualized in the debugger view.
-For detailed information on pretty printers, refer to GDB's [pretty printing documentation].
+GDB supports the use of a structured Python script, called a *pretty printer*, that describes how a type should be visualized in the debugger view. For detailed information on pretty printers, refer to GDB's [pretty printing documentation].
 
-Embedded pretty printers are not automatically loaded when debugging a binary under GDB.
-There are two ways to enable auto-loading embedded pretty printers:
-1. Launch GDB with extra arguments to explicitly add a directory or binary to the auto-load safe path: `gdb -iex "add-auto-load-safe-path safe-path path/to/binary" path/to/binary`
- For more information, see GDB's [auto-loading documentation].
-1. Create a file named `gdbinit` under `$HOME/.config/gdb` (you may need to create the directory if it doesn't already exist). Add the following line to that file: `add-auto-load-safe-path path/to/binary`.
+> [!NOTE]
+> Embedded pretty printers are not automatically loaded when debugging a binary under GDB.
+>
+> There are two ways to enable auto-loading embedded pretty printers:
+>
+> 1. Launch GDB with extra arguments to explicitly add a directory or binary to the auto-load safe path: `gdb -iex "add-auto-load-safe-path safe-path path/to/binary" path/to/binary` For more information, see GDB's [auto-loading documentation].
+> 1. Create a file named `gdbinit` under `$HOME/.config/gdb` (you may need to create the directory if it doesn't already exist). Add the following line to that file: `add-auto-load-safe-path path/to/binary`.
 
 r[attributes.debugger.debugger_visualizer.gdb.path]
-These scripts are embedded using the `gdb_script_file` key, which is a path relative to the crate source file.
+These scripts are embedded using the `gdb_script_file` key, which is a path relative to the source file.
 
 > [!EXAMPLE]
 > <!-- ignore: requires external files -->
@@ -128,7 +128,7 @@ These scripts are embedded using the `gdb_script_file` key, which is a path rela
 > }
 > ```
 >
-> and `printer.py` contains:
+> `printer.py` contains:
 >
 > ```python
 > import gdb