Two typo corrections found by Terry Reedy.

This commit is contained in:
Barry Warsaw 2000-08-17 02:53:00 +00:00
parent fc3c3bfeef
commit eac1680c48
1 changed files with 7 additions and 7 deletions

View File

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