From 3e5b349535f011a51dc308898924786143000631 Mon Sep 17 00:00:00 2001
From: Mariusz Felisiak <felisiak.mariusz@gmail.com>
Date: Wed, 20 Nov 2019 20:35:36 +0100
Subject: [PATCH] Fixed #31008 -- Fixed typos in docs/topics/logging.txt.
---
docs/topics/logging.txt | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/topics/logging.txt b/docs/topics/logging.txt
index 7403bece62..789fa794d5 100644
--- a/docs/topics/logging.txt
+++ b/docs/topics/logging.txt
@@ -240,9 +240,9 @@ is the best source of information about logging configuration dictionaries.
However, to give you a taste of what is possible, here are several examples.
First, here's a configuration which writes all logging from the
-:ref:`django-logger` logger to a local file::
+:ref:`django-logger` logger to a local file:
- .. code-block:: python
+.. code-block:: python
:caption: settings.py
LOGGING = {
@@ -275,9 +275,9 @@ console (same as Django's default logging config, except that the default only
displays log records when ``DEBUG=True``). Django does not log many such
messages. With this config, however, you can also set the environment variable
``DJANGO_LOG_LEVEL=DEBUG`` to see all of Django's debug logging which is very
-verbose as it includes all database queries::
+verbose as it includes all database queries:
- .. code-block:: python
+.. code-block:: python
:caption: settings.py
import os
@@ -298,9 +298,9 @@ verbose as it includes all database queries::
},
}
-Finally, here's an example of a fairly complex logging setup::
+Finally, here's an example of a fairly complex logging setup:
- .. code-block:: python
+.. code-block:: python
:caption: settings.py
LOGGING = {