Tidy up 3.0 fragments (#9057)

doc/whatsnew/fragments/6871.user_action

@@ -2,16 +2,15 @@ The compare to empty string checker (``pylint.extensions.emptystring``) and the
 zero checker (``pylint.extensions.compare-to-zero``) have been removed and their checks are
 now part of the implicit booleaness checker:
 
-``compare-to-zero`` was renamed ``use-implicit-booleaness-not-comparison-to-zero`` and
-``compare-to-empty-string`` was renamed ``use-implicit-booleaness-not-comparison-to-string``
-and they now need to be enabled explicitly.
+- ``compare-to-zero`` was renamed ``use-implicit-booleaness-not-comparison-to-zero`` and
+ ``compare-to-empty-string`` was renamed ``use-implicit-booleaness-not-comparison-to-string``
+ and they now need to be enabled explicitly.
 
-The ``pylint.extensions.emptystring`` and ``pylint.extensions.compare-to-zero`` extensions
-no longer exist and need to be removed from the ``load-plugins`` option.
+- The ``pylint.extensions.emptystring`` and ``pylint.extensions.compare-to-zero`` extensions
+ no longer exist and need to be removed from the ``load-plugins`` option.
 
-Messages related to implicit booleaness were made more explicit and actionable.
-
-This permits to make their likeness explicit and will provide better performance as they share most of their
-conditions to be raised.
+- Messages related to implicit booleaness were made more explicit and actionable.
+ This permits to make their likeness explicit and will provide better performance as they
+ share most of their conditions to be raised.
 
 Closes #6871

doc/whatsnew/fragments/8411.user_action

@@ -1,4 +1,4 @@
-The 'overgeneral-exceptions' option now only takes fully qualified names
+The ``overgeneral-exceptions`` option now only takes fully qualified names
 into account (``builtins.Exception`` not ``Exception``). If you overrode
 this option, you need to use the fully qualified name now.