From 1cfb637cb1babcc7f0ecb1d48b6f3bb4d093e3a5 Mon Sep 17 00:00:00 2001 From: Tanya Schlusser Date: Sat, 17 Jan 2015 21:05:56 -0600 Subject: [PATCH] Removed a stray capitalization and improved the grammar in the 'print' vs 'logging' section --- docs/writing/logging.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/writing/logging.rst b/docs/writing/logging.rst index e138ad9..7faa553 100644 --- a/docs/writing/logging.rst +++ b/docs/writing/logging.rst @@ -28,8 +28,8 @@ Other reasons why logging is better than ``print``: - Events logged in included modules are automatically accessible via the root logger to your application's logging stream, unless you filter them out. -- Logging can be selectively silenced or disabled by using the method - :meth:`logging.Logger.setLevel` or setting the attribute +- Logging can be selectively silenced by using the method + :meth:`logging.Logger.setLevel` or disabled by setting the attribute :attr:`logging.Logger.disabled` to ``True``. @@ -37,8 +37,8 @@ Logging in a Library -------------------- Notes for `configuring logging for a library`_ are in the -`basic logging tutorial`_. Because the *user*, not the library, should -dictate what happens when a logging event occurs, One admonition bears +`logging tutorial`_. Because the *user*, not the library, should +dictate what happens when a logging event occurs, one admonition bears repeating: .. note:: @@ -86,6 +86,7 @@ There are at least three ways to configure a logger: - using a dictionary - using code + Example Configuration via an INI File ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~