Fix "local variables section".

pep-0421.txt

@@ -379,16 +379,16 @@ Open Issues
 * Do we really want to commit to using a dict for
   ``sys.implementation``?
 
-Backward compatibility issues will make it difficult to change our
-minds later.
+  Backward compatibility issues will make it difficult to change our
+  minds later.
 
-The type we use ultimately depends on how general we expect the
-consumption of ``sys.implementation`` to be.  If its practicality is
-oriented toward internal use then the data structure is not as
-critical.  However, ``sys.implementation`` is intended to have a
-non-localized impact across the standard library and the interpreter.
-It's better to *not* make hacking it become an attractive nuisance,
-regardless of our intentions for usage.
+  The type we use ultimately depends on how general we expect the
+  consumption of ``sys.implementation`` to be.  If its practicality is
+  oriented toward internal use then the data structure is not as
+  critical.  However, ``sys.implementation`` is intended to have a
+  non-localized impact across the standard library and the
+  interpreter.  It's better to *not* make hacking it become an
+  attractive nuisance, regardless of our intentions for usage.
 
 * use (immutable?) nameddict (analogous to namedtuple/structseq)?
 
@@ -425,14 +425,15 @@ References
 Copyright
 =========
 
-    This document has been placed in the public domain.
+This document has been placed in the public domain.
 
 
 
-Local Variables:
-mode: indented-text
-indent-tabs-mode: nil
-sentence-end-double-space: t
-fill-column: 70
-coding: utf-8
-End:
+..
+   Local Variables:
+   mode: indented-text
+   indent-tabs-mode: nil
+   sentence-end-double-space: t
+   fill-column: 70
+   coding: utf-8
+   End: