From b6d065ff32427c5dbc5af40e83b545cda8330578 Mon Sep 17 00:00:00 2001
From: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Date: Wed, 28 Oct 2009 23:28:16 +0000
Subject: [PATCH] Issue 7199: Documentation made slightly more consistent
 w.r.t. logging level enumeration.

---
 Doc/library/logging.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index 9dc98fbe85b..5e77e137aaa 100644
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -119,7 +119,7 @@ Another useful feature of the logging API is the ability to produce different
 messages at different log levels.  This allows you to instrument your code with
 debug messages, for example, but turning the log level down so that those debug
 messages are not written for your production system.  The default levels are
-``CRITICAL``, ``ERROR``, ``WARNING``, ``INFO``, ``DEBUG`` and ``NOTSET``.
+``NOTSET``, ``DEBUG``, ``INFO``, ``WARNING``, ``ERROR`` and ``CRITICAL``.
 
 The logger, handler, and log message call each specify a level.  The log message
 is only emitted if the handler and logger are configured to emit messages of
-- 
2.30.9