[1.7.x] Fixed syntax highlighting and indentation in docs/topics/logging.txt.

Backport of 90b64db39c from master

docs/topics/logging.txt

@@ -481,13 +481,16 @@ a ``SuspiciousOperation`` will not be logged to the ``django.request`` logger,
 but only to the ``django.security`` logger.
 
 To silence a particular type of SuspiciousOperation, you can override that
-specific logger following this example::
+specific logger following this example:
+
+.. code-block:: python
 
     'loggers': {
         'django.security.DisallowedHost': {
             'handlers': ['null'],
             'propagate': False,
         },
+    },
 
 ``django.db.backends.schema``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -520,7 +523,9 @@ Python logging module.
     containing the full content of the debug Web page that would have been
     produced if :setting:`DEBUG` were ``True``. To set this value in your
     configuration, include it in the handler definition for
-    ``django.utils.log.AdminEmailHandler``, like this::
+    ``django.utils.log.AdminEmailHandler``, like this:
+
+    .. code-block:: python
 
         'handlers': {
             'mail_admins': {
@@ -544,7 +549,9 @@ Python logging module.
 
     By setting the ``email_backend`` argument of ``AdminEmailHandler``, the
     :ref:`email backend <topic-email-backends>` that is being used by the
-    handler can be overridden, like this::
+    handler can be overridden, like this:
+
+    .. code-block:: python
 
         'handlers': {
             'mail_admins': {
@@ -569,9 +576,9 @@ logging module.
 .. class:: CallbackFilter(callback)
 
     This filter accepts a callback function (which should accept a single
-   argument, the record to be logged), and calls it for each record that passes
-   through the filter. Handling of that record will not proceed if the callback
-   returns False.
+    argument, the record to be logged), and calls it for each record that
+    passes through the filter. Handling of that record will not proceed if the
+    callback returns False.
 
     For instance, to filter out :exc:`~django.http.UnreadablePostError`
     (raised when a user cancels an upload) from the admin emails, you would
@@ -586,7 +593,9 @@ logging module.
                     return False
             return True
 
-   and then add it to your logging config::
+    and then add it to your logging config:
+
+    .. code-block:: python
 
         'filters': {
             'skip_unreadable_posts': {
@@ -607,8 +616,10 @@ logging module.
     This filter will only pass on records when settings.DEBUG is False.
 
     This filter is used as follows in the default :setting:`LOGGING`
-   configuration to ensure that the :class:`AdminEmailHandler` only sends error
-   emails to admins when :setting:`DEBUG` is ``False``::
+    configuration to ensure that the :class:`AdminEmailHandler` only sends
+    error emails to admins when :setting:`DEBUG` is ``False``:
+
+    .. code-block:: python
 
         'filters': {
             'require_debug_false': {