[Python-checkins] peps: Fix markup.

[georg.brandl]

http://hg.python.org/peps/rev/cd6a32d7a3a3
changeset:   4140:cd6a32d7a3a3
user:        Georg Brandl <georg at python.org>
date:        Thu Mar 15 08:23:23 2012 +0100
summary:
  Fix markup.

files:
  pep-0008.txt |  15 ++++++++-------
  1 files changed, 8 insertions(+), 7 deletions(-)


diff --git a/pep-0008.txt b/pep-0008.txt
--- a/pep-0008.txt
+++ b/pep-0008.txt
@@ -543,12 +543,12 @@
 Names to Avoid
 ~~~~~~~~~~~~~~
 
-Never use the characters `l' (lowercase letter el), `O' (uppercase
-letter oh), or `I' (uppercase letter eye) as single character variable
+Never use the characters 'l' (lowercase letter el), 'O' (uppercase
+letter oh), or 'I' (uppercase letter eye) as single character variable
 names.
 
 In some fonts, these characters are indistinguishable from the
-numerals one and zero.  When tempted to use `l', use `L' instead.
+numerals one and zero.  When tempted to use 'l', use 'L' instead.
 
 Package and Module Names
 ~~~~~~~~~~~~~~~~~~~~~~~~
@@ -588,10 +588,11 @@
 (Let's hope that these variables are meant for use inside one module
 only.)  The conventions are about the same as those for functions.
 
-Modules that are designed for use via "from M import *" should use the
-``__all__`` mechanism to prevent exporting globals, or use the older
-convention of prefixing such globals with an underscore (which you
-might want to do to indicate these globals are "module non-public").
+Modules that are designed for use via ``from M import *`` should use
+the ``__all__`` mechanism to prevent exporting globals, or use the
+older convention of prefixing such globals with an underscore (which
+you might want to do to indicate these globals are "module
+non-public").
 
 Function Names
 ~~~~~~~~~~~~~~

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