Fixed sentence structure in docs/internals/contributing/triaging-tickets.txt

This commit is contained in:
Cody Scott 2013-11-21 18:46:35 -05:00 committed by Tim Graham
parent 9c6b57f709
commit 4a54b69e88
1 changed files with 5 additions and 5 deletions

View File

@ -372,16 +372,16 @@ Then, you can help out by:
any activity in a long time, it's possible that the problem has been any activity in a long time, it's possible that the problem has been
fixed but the ticket hasn't yet been closed. fixed but the ticket hasn't yet been closed.
* Identifying trends and themes in the tickets. If there a lot of bug * Identifying trends and themes in the tickets. If there are a lot of bug
reports about a particular part of Django, it may indicate we should reports about a particular part of Django, it may indicate we should
consider refactoring that part of the code. If a trend is emerging, consider refactoring that part of the code. If a trend is emerging,
you should raise it for discussion (referencing the relevant tickets) you should raise it for discussion (referencing the relevant tickets)
on |django-developers|. on |django-developers|.
* Verify if patches submitted by other users are correct. If they do and * Verify if patches submitted by other users are correct. If they are correct
also contain appropriate documentation and tests then move them to the and also contain appropriate documentation and tests then move them to the
"Ready for Checkin" stage. If they don't then leave a comment to explain "Ready for Checkin" stage. If they are not correct then leave a comment to
why and set the corresponding flags ("Patch needs improvement", explain why and set the corresponding flags ("Patch needs improvement",
"Needs tests" etc.). "Needs tests" etc.).
.. note:: .. note::