Fix CI formatting

Author: blyxyas

book/src/development/writing_tests.md

@@ -107,6 +107,7 @@ with the reason for the lint, suggested fixes, and line numbers, etc.
 
 > _Note:_ we need to run `TESTNAME=foo_functions cargo uitest` every time before we run
 > `cargo dev bless`.
+
 Running `TESTNAME=foo_functions cargo uitest` should pass then. When we
 commit our lint, we need to commit the generated `.stderr` files, too.
 
@@ -115,6 +116,7 @@ specific lint you are creating/editing.
 
 > _Note:_ If the generated `.stderr`, and `.fixed` files are empty,
 > they should be removed.
+
 ## Cargo Lints
 
 The process of testing is different for Cargo lints in that now we are
@@ -162,7 +164,8 @@ Untracked files:
 If the lint you are working on is making use of structured suggestions, the test
 file should include a `// run-rustfix` comment at the top.
 
-Structured suggestions tell a user how to fix or re-write certain code that has been linted, they are usually linted with [`span_lint_and_sugg`](https://doc.rust-lang.org/beta/nightly-rustc/clippy_utils/diagnostics/fn.span_lint_and_sugg.html).
+Structured suggestions tell a user how to fix or re-write certain code that has been linted, they are usually linted
+with [`span_lint_and_sugg`](https://doc.rust-lang.org/beta/nightly-rustc/clippy_utils/diagnostics/fn.span_lint_and_sugg.html).
 
 The `// run-rustfix` comment will additionally run [rustfix] for our test.
 Rustfix will apply the suggestions from the lint to the test file code and