Break lines

Author: c410-f3r

book/src/development/adding_lints.md

@@ -615,10 +615,13 @@ output in the `stdout` part.
 
 ## Opposing lints
 
-There are several lints that deal with the same pattern but suggest different approaches. When you are creating a lint that interact with this scenario, the following tips should be encouraged to guide classification:
+There are several lints that deal with the same pattern but suggest different approaches. When you are creating a
+lint that interact with this scenario, the following tips should be encouraged to guide classification:
 
-* The only case where they should be in the same category is if that category is `restriction`. For example, `semicolon_inside_block` and `semicolon_inside_block`.
-* For all the other cases, they should be in different categories with different levels of allowance. For example, `implicit_return` (restriction, allow) and `needless_return` (style, warn).
+* The only case where they should be in the same category is if that category is `restriction`. For example,
+`semicolon_inside_block` and `semicolon_inside_block`.
+* For all the other cases, they should be in different categories with different levels of allowance. For example,
+`implicit_return` (restriction, allow) and `needless_return` (style, warn).
 
 ## PR Checklist