[Python-checkins] peps: Two typo corrections found by Terry Reedy.

[georg.brandl]

http://hg.python.org/peps/rev/16b507d846b6
changeset:   107:16b507d846b6
user:        Barry Warsaw <barry at python.org>
date:        Thu Aug 17 02:53:00 2000 +0000
summary:
  Two typo corrections found by Terry Reedy.

files:
  pep-0001.txt |  14 +++++++-------
  1 files changed, 7 insertions(+), 7 deletions(-)


diff --git a/pep-0001.txt b/pep-0001.txt
--- a/pep-0001.txt
+++ b/pep-0001.txt
@@ -11,7 +11,7 @@
 
 What is a PEP?
 
-    PEP standards for Python Enhancement Proposal.  A PEP is a design
+    PEP stands for Python Enhancement Proposal.  A PEP is a design
     document providing information to the Python community, or
     describing a new feature for Python.  The PEP should provide a
     concise technical specification of the feature and a rationale for
@@ -184,12 +184,12 @@
     Draft phase), a Discussions-To: header will indicate the mailing
     list or URL where the PEP is being discussed.
 
-    PEP heading should begin in column zero and should be capitalized.
-    The body of each section should be indented 4 spaces.  Code
-    samples inside body sections should be indented a further 4
-    spaces, and other indentation can be used as required to make the
-    text readable.  You should use two blank lines between the last
-    line of a section's body and the next section heading.
+    PEP headings should begin in column zero and should be
+    capitalized.  The body of each section should be indented 4
+    spaces.  Code samples inside body sections should be indented a
+    further 4 spaces, and other indentation can be used as required to
+    make the text readable.  You should use two blank lines between
+    the last line of a section's body and the next section heading.
 
     No tabs should appear in the document at all.  A PEP should
     include the Emacs stanza included by example in this PEP to aid

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