Minor documentation changes relating to NullHandler, the module used for handlers...

diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index 232c5b5acfa0f9749579b9df3c49917e97f229c4..e9675c1a4e26ef40dd0f64e52ea17666c61eca1b 100644 (file)
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -420,6 +420,7 @@ You can see that the config file approach has a few advantages over the Python
 code approach, mainly separation of configuration and code and the ability of
 noncoders to easily modify the logging properties.
 
+.. _library-config:
 Configuring Logging for a Library
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -463,6 +464,7 @@ just "foo".
 
 The :class:`NullHandler` class was not present in previous versions, but is now
 included, so that it need not be defined in library code.
+See :ref:`library-config` for more information.
 
 
 
@@ -560,7 +562,8 @@ provided:
 #. :class:`NullHandler` instances do nothing with error messages. They are used
    by library developers who want to use logging, but want to avoid the "No
    handlers could be found for logger XXX" message which can be displayed if
-   the library user has not configured logging.
+   the library user has not configured logging. See :ref:`library-config` for
+   more information.
 
 .. versionadded:: 3.1
 
@@ -1608,7 +1611,8 @@ for use by library developers.
 
       This method does nothing.
 
-
+See :ref:`library-config` for more information on how to use
+:class:`NullHandler`.
 
 WatchedFileHandler
 ^^^^^^^^^^^^^^^^^^