fix style errors

Author: gibbyfree

src/attributes/debugger.md

@@ -1,27 +1,27 @@
 # Debugger attributes
 
-The following [attributes] are used for enhancing the debugging experience when using third-party debuggers like GDB or LLDB. 
+he following [attributes] are used for enhancing the debugging experience when using third-party debuggers like GDB or LLDB.
 
 ## The `debugger_visualizer` attribute
 
-The `debugger_visualizer` attribute can be used to embed a debugger visualizer file into the debug information generated by `rustc`. 
+The `debugger_visualizer` attribute can be used to embed a debugger visualizer file into the debug information generated by `rustc`.
 This enables an improved debugger experience for types outside of Rust's standard library.
 
 ### Using `debugger_visualizer` with Natvis
 
 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.
-A Natvis file is embedded using the `natvis-file` meta item. 
+A Natvis file is embedded using the `natvis-file` meta item.
 For detailed information on the Natvis format, refer to Microsoft's [Natvis documentation].
 
 <div class="warning">
-Currently, this attribute only supports embedding Natvis files on `-windows-msvc` targets. 
+Currently, this attribute only supports embedding Natvis files on `-windows-msvc` targets.
 </div>
 
 Consider a crate with this directory structure:
 
 ```text
 /Cargo.toml
-/Rectangle.natvis 
+/Rectangle.natvis
   +-- src
       +-- main.rs
 ```
@@ -81,14 +81,14 @@ When viewed under WinDbg, the `fancy_rect` variable would be shown as follows:
 
 ### Using `debugger_visualizer` with GDB
 
-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. 
-These scripts are embedded using the `gdb_script_file` meta item. 
+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.
+These scripts are embedded using the `gdb_script_file` meta item.
 For detailed information on pretty printers, refer to GDB's [pretty print 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 "set auto-load 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`. 
+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`.
 
 Consider a crate called `foobar` with this directory structure:
 
@@ -148,7 +148,7 @@ gdb.current_objfile().pretty_printers.append(lookup)
 
 When the crate's debug executable is passed into GDB, `print bob` will display:
 
-```
+```text
 "Bob" is 10 years old.
 ```