Fix CI errors

Author: blyxyas

book/src/development/emitting_lints.md

@@ -9,7 +9,8 @@ Note that we will not go into concrete implementation of a lint logic in this
 chapter. We will go into details in later chapters as well as in two examples
 of real Clippy lints.
 
-In this chapter, we'll see an example of an imaginary `LateLintPass` lint named `bar_expressions`, that checks for expresions named `bar`.
+In this chapter, we'll see an example of an imaginary `LateLintPass` lint named `bar_expressions`, that checks for
+expresions named `bar`.
 
 To emit a lint with `LateLintPass`, we must implement it for the lint that we have
 declared. Take a look at the [LateLintPass][late_lint_pass] documentation, which
@@ -81,7 +82,10 @@ impl<'tcx> LateLintPass<'tcx> for BarExpressions {
 
 ## Suggestions: Automatic fixes
 
-Some lints know what to change in order to fix the lint. A real world example, the lint [`range_plus`][range_plus_one] lints for ranges where the user wrote `x..y + 1` instead of using an [inclusive range][inclusive_range] (`x..=1`). The fix to this lint would be just changing your `x..y + 1` expression to `x..=y`, **this is where suggestions come in**.
+Some lints know what to change in order to fix the lint. A real world example, the lint
+[`range_plus`][range_plus_one] lints for ranges where the user wrote `x..y + 1` instead of using an
+[inclusive range][inclusive_range] (`x..=1`). The fix to this lint would be just changing your `x..y + 1` expression
+to `x..=y`, **this is where suggestions come in**.
 
 A suggestion is a change that the lint provides to fix the issue it is linting.
 The output looks something like this (from the example earlier):
@@ -94,9 +98,12 @@ LL |     for _ in 1..1 + 1 {}
    |              ^^^^^^^^ help: use: `1..=1`
 ```
 
-**Not all suggestions are always right**, some of them require human supervision, that's why we have [Applicability][applicability].
+**Not all suggestions are always right**, some of them require human supervision, that's why we have
+[Applicability][applicability].
 
-Applicability indicates confidence in the correctness of the suggestion, some are always right (`Applicability::MachineApplicable`), but we use `Applicability::MaybeIncorrect` and other when talking about a lint that may be incorrect.
+Applicability indicates confidence in the correctness of the suggestion, some are always right
+(`Applicability::MachineApplicable`), but we use `Applicability::MaybeIncorrect` and other when talking about a lint
+that may be incorrect.
 
 ---
 
@@ -125,7 +132,8 @@ Suggestions generally use the [`format!`](format_macro) macro to interpolate the
 
 ## How to choose between notes, help messages and suggestions
 
-Notes are presented separately from the main lint message, they provide useful information that the user needs to understand why the lint was activated. They are the most helpful when attached to a span.
+Notes are presented separately from the main lint message, they provide useful information that the user needs to
+understand why the lint was activated. They are the most helpful when attached to a span.
 
 Example:
 
@@ -146,7 +154,8 @@ note: argument has type &SomeStruct
 
 ---
 
-Help messages are specifically to help the user. These are used in situation where you can't provide a specific machine applicable suggestion. They can also be attached to a span.
+Help messages are specifically to help the user. These are used in situation where you can't provide a specific
+machine applicable suggestion. They can also be attached to a span.
 
 Example:
 
@@ -162,7 +171,8 @@ error: constant division of 0.0 with 0.0 will always result in NaN
 
 ---
 
-Suggestions are the most helpful, they are direct changes to the source code in order to fix the error. The magic in suggestions is that tools like rustfix can detect them and automatically fix your code.
+Suggestions are the most helpful, they are direct changes to the source code in order to fix the error. The magic
+in suggestions is that tools like rustfix can detect them and automatically fix your code.
 
 Example:
 
@@ -178,9 +188,11 @@ error: This `.fold` can be more succinctly expressed as `.any`
 
 ### Snippets
 
-Snippets are pieces of the source code (as a string), they are extracted generally using the [`snippet`][snippet_fn] function.
+Snippets are pieces of the source code (as a string), they are extracted generally using the [`snippet`][snippet_fn]
+function.
 
-For example, if you want to know how an item looks (and you know the item's span), you could use `snippet(cx, span, "..")`.
+For example, if you want to know how an item looks (and you know the item's span), you could use
+`snippet(cx, span, "..")`.
 
 ## Final: Run UI Tests to Emit the Lint
 
@@ -191,8 +203,6 @@ The next step is to implement the logic properly, which is a detail that we will
 cover in the next chapters.
 
 [diagnostics]: https://doc.rust-lang.org/nightly/nightly-rustc/clippy_utils/diagnostics/index.html
-[early_check_fn]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint/trait.EarlyLintPass.html#method.check_fn
-[early_lint_pass]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint/trait.EarlyLintPass.html
 [late_check_expr]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint/trait.LateLintPass.html#method.check_expr
 [late_check_fn]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint/trait.LateLintPass.html#method.check_fn
 [late_check_item]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lint/trait.LateLintPass.html#method.check_item
@@ -204,5 +214,4 @@ cover in the next chapters.
 [range_plus_one]: https://rust-lang.github.io/rust-clippy/master/index.html#range_plus_one
 [inclusive_range]: https://doc.rust-lang.org/std/ops/struct.RangeInclusive.html
 [applicability]: https://doc.rust-lang.org/beta/nightly-rustc/rustc_errors/enum.Applicability.html
-[format_macro]: https://doc.rust-lang.org/std/macro.format.html
-[snippet_fn]: https://doc.rust-lang.org/beta/nightly-rustc/clippy_utils/source/fn.snippet.html
+[snippet_fn]: https://doc.rust-lang.org/beta/nightly-rustc/clippy_utils/source/fn.snippet.html