[Python-checkins] devguide: fix a couple of typos
eli.bendersky
python-checkins at python.org
Fri Feb 4 13:10:38 CET 2011
eli.bendersky pushed 253dee176d55 to devguide:
http://hg.python.org/devguide/rev/253dee176d55
changeset: 230:253dee176d55
tag: tip
user: eli.bendersky
date: Fri Feb 04 14:10:31 2011 +0200
summary:
fix a couple of typos
files:
committing.rst
diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -34,7 +34,7 @@
As a core developer you will occasionally want to commit a patch created by
someone else. When doing so you will want to make sure of some things.
-First, make sure the patch in a good state. Both :ref:`patch` and
+First, make sure the patch is in a good state. Both :ref:`patch` and
:ref:`helptriage`
explain what is to be expected of a patch. Typically patches that get cleared by
triagers are good to go except maybe lacking ``Misc/ACKS`` and ``Misc/NEWS``
@@ -43,7 +43,7 @@
Second, make sure the patch does not break backwards-compatibility without a
good reason. This means :ref:`running the test suite <runtests>` to make sure
everything still passes. It also means that if semantics do change there must
-be a good reason for the the breakage of code the change will cause (and it
+be a good reason for the breakage of code the change will cause (and it
**will** break someone's code). If you are unsure if the breakage is worth it,
ask on python-dev.
--
Repository URL: http://hg.python.org/devguide
More information about the Python-checkins
mailing list