[Python-checkins] devguide: Fixes as caught by Sandro Tosi.

brett.cannon python-checkins at python.org
Mon Jan 17 21:05:41 CET 2011


brett.cannon pushed d47c19bbcf61 to devguide:

http://hg.python.org/devguide/rev/d47c19bbcf61
changeset:   101:d47c19bbcf61
tag:         tip
user:        Brett Cannon <brett at python.org>
date:        Mon Jan 17 12:05:32 2011 -0800
summary:
  Fixes as caught by Sandro Tosi.

files:
  langchanges.rst
  stdlibchanges.rst

diff --git a/langchanges.rst b/langchanges.rst
--- a/langchanges.rst
+++ b/langchanges.rst
@@ -15,7 +15,7 @@
 **every** Python programmer already in existence and all Python programmers to
 come will end up eventually learning about the change you want to propose.
 Books will need updating, code will be changed, and a new way to do things will
-need to be learned. Change to the Python programing language are never taken
+need to be learned. Changes to the Python programing language are never taken
 lightly.
 
 Because of the seriousness that language changes carry, any change must be
diff --git a/stdlibchanges.rst b/stdlibchanges.rst
--- a/stdlibchanges.rst
+++ b/stdlibchanges.rst
@@ -39,7 +39,7 @@
 If a core developer decides that your code would be useful to the general
 Python community, they will then commit your code. If your code is not picked
 up by a core developer and committed then please do not take this personally.
-Through your public sharing of your code in order to gauage community support
+Through your public sharing of your code in order to gauge community support
 for it you at least can know that others will come across it who may find it
 useful.
 
@@ -81,7 +81,7 @@
 Requirements
 ''''''''''''''
 In order for a module to even be considered for inclusion into the stdlib, a
-couple requirements must be met.
+couple of requirements must be met.
 
 The most basic is that the code must meet
 :ref:`standard patch requirements <patch>`. For code that has
@@ -93,7 +93,7 @@
 a module its API becomes frozen. This means that a module should only enter the
 stdlib when it is mature and gone through its "growing pains".
 
-The module needs to be consideredbest-of-breed. When something is included in
+The module needs to be considered best-of-breed. When something is included in
 the stdlib it tends to be chosen first for products over other third-party
 solutions. By virtue of having been available to the public for at least a
 year, a module needs to have established itself as (one of) the top choices by
@@ -111,7 +111,7 @@
 module must promise to help maintain the module in the stdlib for two years.
 This not only helps out other core developers by alleviating workload from bug
 reports that arrive from the first Python release containing the module, but
-also help make sure that the overall design of the module continues to be
+also helps to make sure that the overall design of the module continues to be
 uniform.
 
 
@@ -138,7 +138,7 @@
 will once again receive a large amount of feedback and discussion. A PEP
 dictator will be assigned who make the final call on whether the PEP will be
 accepted or not. If the PEP dictator agrees to accept your PEP (which typically
-means that the core developers end up agreeng in general to accepting
+means that the core developers end up agreeing in general to accepting
 your PEP) then the module
 will be added to the stdlib once the creators of the module sign
 :ref:`contributor agreements <contributor_agreement>`.

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


More information about the Python-checkins mailing list