attempt to fix github action, make markdown lint happy

.github/workflows/test.yml

@@ -170,9 +170,8 @@ jobs:
       - uses: actions/checkout@v3
       - uses: dtolnay/rust-toolchain
         with:
-          # This has to match `rust-toolchain` in the rust-toolchain file of the dylint lints
           toolchain: nightly-2023-10-06
-          components: "clippy llvm-tools-preview, rustc-dev"
+          components: "clippy, llvm-tools-preview, rustc-dev"
       - uses: Swatinem/rust-cache@v2.6.1
         with:
           cache-provider: "buildjet"
@@ -181,7 +180,6 @@ jobs:
       - name: run clippy against custom lints
         run: |
           cargo clippy --all-targets --all-features \
-          # Explicitly list all lints here
           -p tracing_debug_field \
           -- --warn clippy::pedantic --deny warnings
       - name: run dylint clippy on workspace crates

lint/tracing_debug_field/README.md

@@ -1,18 +1,18 @@
 # `tracing_debug_field`
 
-### What it does
+## What it does
 
 Warns about fields in `tracing::event!` macros that are debug formatted
 using either the `?` sigil or the [`tracing::field::debug`](https://docs.rs/tracing/0.1.40/tracing/field/fn.debug.html) 
 utility.
 
-### Why is this bad?
+## Why is this bad?
 
 Debug formatted fields are bad for observability as they are usually unparseable and
 unreadable. They also surface language-specific implementation details that are unnecessary
 and too verbose for operators.
 
-### What to do instead
+## What to do instead
 
 Depending on the complexity of what must be logged:
 
@@ -26,7 +26,7 @@ Depending on the complexity of what must be logged:
 5. Hash an object and emit the hash (this works very well for messages that will be otherwise recorded and
    can be retrieved outside the observability intake).
 
-### Example
+## Example
 ```rust
 #[derive(Clone, Copy, Debug)]
 struct Wrapped(&'static str);