Make PEP 9 one massive literal block (#437)

Closes #4.

pep-0009.txt

@@ -5,21 +5,20 @@ Last-Modified: $Date$
 Author: Barry Warsaw <barry@python.org>
 Status: Withdrawn
 Type: Process
-Content-Type: text/plain
+Content-Type: text/x-rst
 Created: 14-Aug-2001
 Post-History:
 Resolution: https://mail.python.org/mailman/private/peps/2016-January/001165.html
 
-
-Update
+::
+  Update
 
       As of 05-Jan-2016, this PEP is officially deprecated and replaced
       by PEP 12.  All PEPs should now use the reStructuredText format
       described by PEP 12, and plaintext PEPs will no longer be
-    accepted, however you may still see legacy PEPs written using the
-    plaintext style.
+      accepted.
 
-Abstract
+  Abstract
 
       This PEP provides a boilerplate or sample template for creating
       your own plaintext PEPs.  In conjunction with the content
@@ -38,7 +37,7 @@ Abstract
       see PEP 12, "Sample reStructuredText PEP Template" [2].
 
 
-Rationale
+  Rationale
 
       PEP submissions come in a wide variety of forms, not all adhering
       to the format guidelines set forth below.  Use this template, in
@@ -47,7 +46,7 @@ Rationale
       form.
 
 
-How to Use This Template
+  How to Use This Template
 
       To use this template you must first decide whether your PEP is
       going to be an Informational or Standards Track PEP.  Most PEPs
@@ -153,7 +152,7 @@ How to Use This Template
         to see if you were still awake. :)
 
 
-Plaintext PEP Formatting Requirements
+  Plaintext PEP Formatting Requirements
 
       PEP headings must begin in column zero and the initial letter of
       each word must be capitalized as in book titles.  Acronyms should
@@ -209,7 +208,7 @@ Plaintext PEP Formatting Requirements
       are never padded.
 
 
-References
+  References
 
       [1] PEP 1, PEP Purpose and Guidelines, Warsaw, Hylton
           http://www.python.org/dev/peps/pep-0001/
@@ -221,7 +220,7 @@ References
 
 
 
-Copyright
+  Copyright
 
       This document has been placed in the public domain.