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

[brett.cannon]

brett.cannon pushed b4311bd83cea to devguide:

http://hg.python.org/devguide/rev/b4311bd83cea
changeset:   90:b4311bd83cea
tag:         tip
user:        Brett Cannon <brett at python.org>
date:        Fri Jan 14 17:47:36 2011 -0800
summary:
  Fixes suggested by Sandro Tosi.

files:
  languishing.rst

diff --git a/languishing.rst b/languishing.rst
--- a/languishing.rst
+++ b/languishing.rst
@@ -7,15 +7,15 @@
 cannot agree on the proper solution (or if a problem even exists). Other
 times a solution is agreed upon but writing the code for the solution would
 take too much effort for little gain, and so no one wants to do the work (or
-would simply break too much pre-existing code without a different solution.
+would simply break too much pre-existing code without a different solution).
 
-In these cases an issue will languish_ in the `issue tracker`_. In the case of
-an issue that is languishing, it should have its status set as such. This
+In these cases an issue will languish_ in the `issue tracker`_, and its
+status should should have its status set as such. This
 serves the purpose of preventing people who are trying to :ref:`fix issues
 <fixingissues>` from wasting time on issues that even core developers cannot
 come up with an agreed-upon solution for.
 
-A good way to tell if an issue is languishing is based on whether an issue had
+A good way to tell if an issue is languishing is based on whether it had
 an in-depth discussion that stalled several months ago. In that instance it is
 typically safe to set the status of the issue to "languishing". If you are
 unsure you can always leave a comment on the issue asking if others agree that

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