markdownlint: minor fixes

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4198e6bc5eb73ed3a078cf1d0ce8d26a8735d9eb
diff --git a/docs/checklists/changes.md b/docs/checklists/changes.md
index a994ef3..e58780e 100644
--- a/docs/checklists/changes.md
+++ b/docs/checklists/changes.md
@@ -187,6 +187,9 @@
     [C17 draft specification][c17-draft-standard], 6.7.2.1 Structure and union
     specifiers, paragraph 18.
 
+[c17-draft-standard]:
+  https://web.archive.org/web/20181230041359/http://www.open-std.org/jtc1/sc22/wg14/www/abq/c17_updated_proposed_fdis.pdf
+
 ### ABI control
 
 - [ ] My new function symbols are marked with `LIBPLDM_ABI_TESTING` in the
@@ -277,13 +280,13 @@
 
 Assuming:
 
-```
+```shell
 export OPENBMC_CI_IMAGE=openbmc/ubuntu-unit-test:2024-W21-ce361f95ff4fa669
 ```
 
 the ABI dump can be updated with:
 
-```
+```shell
 docker run \
   --cap-add=sys_admin \
   --rm=true \
diff --git a/docs/fuzzing.md b/docs/fuzzing.md
index 79c19aa..abb35bc 100644
--- a/docs/fuzzing.md
+++ b/docs/fuzzing.md
@@ -26,14 +26,14 @@
 
 Run with
 
-```
+```shell
 nice honggfuzz -i corpusdir --linux_perf_branch --dict tests/fuzz/fd.dict  -- ./bhf/tests/fuzz/fd-fuzz
 ```
 
 The `--linux_perf_branch` switch is optional, it requires permissions for perf
 counters:
 
-```
+```shell
 echo 0 | sudo tee /proc/sys/kernel/perf_event_paranoid
 ```
 
@@ -48,7 +48,7 @@
 
 Running a single instance (just for testing):
 
-```
+```shell
 afl-fuzz -i fuzzrun/hf11/ -o fuzzrun/out12single ./bfuzz/tests/fuzz/fd-fuzz
 ```
 
@@ -57,7 +57,7 @@
 
 Running with 20 threads:
 
-```
+```shell
 nice aflr run  -t bfuzz/tests/fuzz/fd-fuzz -i workdir/out5/m_fd-fuzz/queue -o workdir/out6 -c bcmplog/tests/fuzz/fd-fuzz -s bfuzzasan/tests/fuzz/fd-fuzz -n 20 -x tests/fuzz/fd.dict --session-name fuzz
 ```
 
@@ -81,7 +81,7 @@
 
 Typical usage, with corpus in `fuzzrun/corpus`:
 
-```
+```shell
 ./tests/fuzz/fuzz-coverage.py fuzzrun/corpus bnoopt/tests/fuzz/fd-fuzz . bnoopt/ coverage-output
 ```
 
@@ -90,7 +90,7 @@
 When the fuzz run encounters a crash, the testcase can be run against the built
 target manually, and stepped through with GDB etc.
 
-```
+```shell
 env TRACEFWFD=1 ./bnoopt/tests/fuzz/fd-fuzz < crashing.bin
 ```