Tweaked format of cookbook example.

diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst
index d20452e34a0d12510fc96595cd8467dd1d003d9b..a040aa4b80e741b8265ce8e38c819c8f80cb05fa 100644 (file)
--- a/Doc/howto/logging-cookbook.rst
+++ b/Doc/howto/logging-cookbook.rst
@@ -771,10 +771,10 @@ UTF-8, then you need to do the following:
    :class:`~logging.handlers.SysLogHandler` instance, with a format string
    such as::
 
-      u"ASCII section\ufeffUnicode section"
+      u'ASCII section\ufeffUnicode section'
 
    The Unicode code point ``u'\feff```, when encoded using UTF-8, will be
-   encoded as a UTF-8 BOM -- the bytestring ``'\xef\xbb\bf'``.
+   encoded as a UTF-8 BOM -- the byte-string ``'\xef\xbb\xbf'``.
 
 #. Replace the ASCII section with whatever placeholders you like, but make sure
    that the data that appears in there after substitution is always ASCII (that
@@ -785,7 +785,8 @@ UTF-8, then you need to do the following:
    encoded using UTF-8.
 
 If the formatted message is Unicode, it *will* be encoded using UTF-8 encoding
-by ``SysLogHandler``. If you follow these rules, you should be able to produce
-RFC 5424-compliant messages. If you don't, logging may not complain, but your
-messages will not be RFC 5424-compliant, and your syslog daemon may complain.
+by ``SysLogHandler``. If you follow the above rules, you should be able to
+produce RFC 5424-compliant messages. If you don't, logging may not complain,
+but your messages will not be RFC 5424-compliant, and your syslog daemon may
+complain.