[3.10] bpo-35821: Fix restructuredtext code formatting in logging.rst (GH-29963) (GH-29965)

(cherry picked from commit c7e7a4b)


Co-authored-by: Ken Jin <[email protected]>

Automerge-Triggered-By: GH:Fidget-Spinner

Author: miss-islington

Doc/library/logging.rst

@@ -81,12 +81,12 @@ is the module's name in the Python package namespace.
       of ancestor loggers.
 
       Spelling it out with an example: If the propagate attribute of the logger named
-      `A.B.C` evaluates to true, any event logged to `A.B.C` via a method call such as
-      `logging.getLogger('A.B.C').error(...)` will [subject to passing that logger's
+      ``A.B.C`` evaluates to true, any event logged to ``A.B.C`` via a method call such as
+      ``logging.getLogger('A.B.C').error(...)`` will [subject to passing that logger's
       level and filter settings] be passed in turn to any handlers attached to loggers
-      named `A.B`, `A` and the root logger, after first being passed to any handlers
-      attached to `A.B.C`. If any logger in the chain `A.B.C`, `A.B`, `A` has its
-      `propagate` attribute set to false, then that is the last logger whose handlers
+      named ``A.B``, ``A`` and the root logger, after first being passed to any handlers
+      attached to ``A.B.C``. If any logger in the chain ``A.B.C``, ``A.B``, ``A`` has its
+      ``propagate`` attribute set to false, then that is the last logger whose handlers
       are offered the event to handle, and propagation stops at that point.
 
       The constructor sets this attribute to ``True``.