[Python-checkins] cpython (2.7): Improved cookbook entry and fixed typo.

[vinay.sajip]

http://hg.python.org/cpython/rev/225bc86a0d75
changeset:   78292:225bc86a0d75
branch:      2.7
parent:      78288:c947f493ccec
user:        Vinay Sajip <vinay_sajip at yahoo.co.uk>
date:        Fri Jul 27 10:52:18 2012 +0100
summary:
  Improved cookbook entry and fixed typo.

files:
  Doc/howto/logging-cookbook.rst |  6 +++---
  1 files changed, 3 insertions(+), 3 deletions(-)


diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst
--- a/Doc/howto/logging-cookbook.rst
+++ b/Doc/howto/logging-cookbook.rst
@@ -763,7 +763,7 @@
 
 As this behaviour is broken, the incorrect BOM insertion code is being removed
 from Python 2.7.4 and later. However, it is not being replaced, and if you
-want to produce RFC 5424-compliant messages which includes a BOM, an optional
+want to produce RFC 5424-compliant messages which include a BOM, an optional
 pure-ASCII sequence before it and arbitrary Unicode after it, encoded using
 UTF-8, then you need to do the following:
 
@@ -781,8 +781,8 @@
    way, it will remain unchanged after UTF-8 encoding).
 
 #. Replace the Unicode section with whatever placeholders you like; if the data
-   which appears there after substitution is Unicode, that's fine -- it will be
-   encoded using UTF-8.
+   which appears there after substitution contains characters outside the ASCII
+   range, that's fine -- it will be encoded using UTF-8.
 
 If the formatted message is Unicode, it *will* be encoded using UTF-8 encoding
 by ``SysLogHandler``. If you follow the above rules, you should be able to

-- 
Repository URL: http://hg.python.org/cpython