[Python-checkins] r55051 - peps/trunk/pep-0001.txt

david.goodger python-checkins at python.org
Tue May 1 17:37:46 CEST 2007


Author: david.goodger
Date: Tue May  1 17:37:43 2007
New Revision: 55051

Modified:
   peps/trunk/pep-0001.txt
Log:
spelling

Modified: peps/trunk/pep-0001.txt
==============================================================================
--- peps/trunk/pep-0001.txt	(original)
+++ peps/trunk/pep-0001.txt	Tue May  1 17:37:43 2007
@@ -63,7 +63,7 @@
 The PEP editors assign PEP numbers and change their status.  The
 current PEP editors are David Goodger and Barry Warsaw.  Please send
 all PEP-related email to <peps at python.org> (no cross-posting please).
-Also see `PEP Editor Reponsibilities & Workflow`_ below.
+Also see `PEP Editor Responsibilities & Workflow`_ below.
 
 The PEP process begins with a new idea for Python.  It is highly
 recommended that a single PEP contain a single key proposal or new
@@ -376,8 +376,8 @@
 decision (it's not like such decisions can't be reversed :).
 
 
-PEP Editor Reponsibilities & Workflow
-=====================================
+PEP Editor Responsibilities & Workflow
+======================================
 
 A PEP editor must subscribe to the <peps at python.org> list.  All
 PEP-related correspondence should be sent (or CC'd) to
@@ -432,7 +432,7 @@
 list for PEP changes, and correct any structure, grammar, spelling, or
 markup mistakes we see.
 
-The editors don't pass judgment on PEPs.  We merely do the
+The editors don't pass judgement on PEPs.  We merely do the
 administrative & editorial part.  Except for times like this, there's
 relatively low volume.
 


More information about the Python-checkins mailing list