PEPs 216, 235, 312: Fix more markup

pep-0216.txt

@@ -104,7 +104,7 @@ in docstrings.
 
 At least the following must be available:
 
-a. A tag that means "this is a Python `something`, guess what"
+a. A tag that means "this is a Python *something*, guess what"
 
    Example: In the sentence "The POP3 class", we need to markup "POP3"
    so. The parser will be able to guess it is a class from the contents

pep-0235.txt

@@ -74,11 +74,11 @@ the current rules for import on Windows:
 
        import file
 
-then if Python finds ``FiLe.py`` first, it raises a ``NameError``.  It
+   then if Python finds ``FiLe.py`` first, it raises a ``NameError``.
-does *not* go on to find ``file.py``; indeed, it's impossible to
+   It does *not* go on to find ``file.py``; indeed, it's impossible to
-import any but the first case-insensitive match on ``sys.path``,
+   import any but the first case-insensitive match on ``sys.path``,
-and then only if case matches exactly in the first
+   and then only if case matches exactly in the first
-case-insensitive match.
+   case-insensitive match.
 
 2. An ugly exception: if the first case-insensitive match on
    ``sys.path`` is for a file whose name is entirely in upper case

pep-0312.txt

@@ -185,7 +185,7 @@ thread "For review: PEP 308 - If-then-else expression" [2]_.
 References
 ==========
 
-.. [1] Guido van Rossum, Recommend accepting PEP 312 -- Simple Implicit	Lambda
+.. [1] Guido van Rossum, Recommend accepting PEP 312 -- Simple Implicit Lambda
        https://mail.python.org/pipermail/python-dev/2005-June/054304.html
 
 .. [2] Guido van Rossum, For review: PEP 308 - If-then-else expression