Manual fixes to pep 0002

Author: Carreau

pep-0002.txt

@@ -15,7 +15,7 @@ PEP Replacement
 ===============
 
 This PEP has been superseded by the updated material in the Python Developer's
-Guide [1].
+Guide [1]_.
 
 Introduction
 ============
@@ -34,10 +34,10 @@ equipped to detect and report gaps in the library; things that are missing but
 should be added.
 
 New functionality is commonly added to the library in the form of new modules.
-This PEP will describe the procedure for the _addition_ of new modules.  PEP 4
-deals with procedures for deprecation of modules; the _removal_ of old and
+This PEP will describe the procedure for the *addition* of new modules.  PEP 4
+deals with procedures for deprecation of modules; the *removal* of old and
 unused modules from the standard library.  Finally there is also the issue of
-_changing_ existing modules to make the picture of library evolution complete.
+*changing* existing modules to make the picture of library evolution complete.
 PEP 3 and PEP 5 give some guidelines on this. The continued maintenance of
 existing modules is an integral part of the decision on whether to add a new
 module to the standard library.  Therefore, this PEP also introduces concepts
@@ -65,7 +65,7 @@ Maintainer(s)
 All contributions to the standard library need one or more maintainers.  This
 can be an individual, but it is frequently a group of people such as the XML-
 SIG.  Groups may subdivide maintenance tasks among themselves.  One ore more
-maintainers shall be the _head maintainer_ (usually this is also the main
+maintainers shall be the *head maintainer* (usually this is also the main
 developer).  Head maintainers are convenient people the integrators can address
 if they want to resolve specific issues, such as the ones detailed later in
 this document.
@@ -102,7 +102,7 @@ document and a reference implementation.  The library PEP differs from a normal
 standard track PEP in that the reference implementation should in this case
 always already have been written before the PEP is to be reviewed for inclusion
 by the integrators and to be commented upon by the community; the reference
-implementation _is_ the proposed contribution.
+implementation *is* the proposed contribution.
 
 This different requirement exists for the following reasons:
 
@@ -184,7 +184,8 @@ Relationship to the mythical Catalog?
 References
 ==========
 
-[1] Adding to the Stdlib http://docs.python.org/devguide/stdlibchanges.html
+.. [1] Adding to the Stdlib
+   (http://docs.python.org/devguide/stdlibchanges.html)
 
 Copyright
 =========
@@ -196,4 +197,4 @@ This document has been placed in the public domain.
    mode: indented-text
    indent-tabs-mode: nil
    fill-column: 70
-   End:
+   End: