aboutsummaryrefslogtreecommitdiffstats
path: root/docs/topics/contributing.md
diff options
context:
space:
mode:
authorPascal Borreli2013-05-28 15:09:23 +0100
committerPascal Borreli2013-05-28 15:09:23 +0100
commit8f35ac4f93c608eaced3f48a46e8922104e09182 (patch)
tree55b394b57fc7b0e40283d89dc23dd0b41dfc074d /docs/topics/contributing.md
parent7123f0b1e6b29778c41476341bd2370f60c279fa (diff)
downloaddjango-rest-framework-8f35ac4f93c608eaced3f48a46e8922104e09182.tar.bz2
Fixed typos
Diffstat (limited to 'docs/topics/contributing.md')
-rw-r--r--docs/topics/contributing.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/contributing.md b/docs/topics/contributing.md
index 1d1fe892..fd60daea 100644
--- a/docs/topics/contributing.md
+++ b/docs/topics/contributing.md
@@ -22,9 +22,9 @@ It's really helpful if you make sure you address issues to the correct channel.
Some tips on good issue reporting:
-* When decribing issues try to phrase your ticket in terms of the *behavior* you think needs changing rather than the *code* you think need changing.
+* When describing issues try to phrase your ticket in terms of the *behavior* you think needs changing rather than the *code* you think need changing.
* Search the issue list first for related items, and make sure you're running the latest version of REST framework before reporting an issue.
-* If reporting a bug, then try to include a pull request with a failing test case. This'll help us quickly identify if there is a valid issue, and make sure that it gets fixed more quickly if there is one.
+* If reporting a bug, then try to include a pull request with a failing test case. This will help us quickly identify if there is a valid issue, and make sure that it gets fixed more quickly if there is one.