[1.11.x] Fixed #27931 -- Clarified the meaning of "django catch-all logger."

Backport of f21915bb3ad73001b7d987332b2b4a0ae4ec288d from master

docs/topics/logging.txt

@@ -456,8 +456,8 @@ Django provides several built-in loggers.
 ``django``
 ~~~~~~~~~~
 
-``django`` is the catch-all logger. No messages are posted directly to
+The catch-all logger for messages in the  ``django`` hierarchy. No messages are
-this logger.
+posted using this name but instead using one of the loggers below.
 
 .. _django-request-logger:
 
@@ -740,18 +740,19 @@ By default, Django configures the following logging:
 
 When :setting:`DEBUG` is ``True``:
 
-* The ``django`` catch-all logger sends all messages at the ``INFO`` level or
+* The ``django`` logger sends messages in the ``django`` hierarchy (except
-  higher to the console.
+  ``django.server``) at the ``INFO`` level or higher to the console.
 
 When :setting:`DEBUG` is ``False``:
 
-* The ``django`` logger send messages with ``ERROR`` or ``CRITICAL`` level to
+* The ``django`` logger sends messages in the ``django`` hierarchy (except
+  ``django.server``)  with ``ERROR`` or ``CRITICAL`` level to
   :class:`AdminEmailHandler`.
 
 Independent of the value of :setting:`DEBUG`:
 
-* The :ref:`django-server-logger` logger sends all messages at the ``INFO``
+* The :ref:`django-server-logger` logger sends messages at the ``INFO`` level
-  level or higher to the console.
+  or higher to the console.
 
 See also :ref:`Configuring logging <configuring-logging>` to learn how you can
 complement or replace this default logging configuration.