aboutsummaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorCraig de Stigter2014-10-03 08:41:18 +1300
committerCraig de Stigter2014-10-03 08:41:18 +1300
commitdfab9af294972720f59890967cd9ae1a6c0796b6 (patch)
tree587fb81fc26d401870f860afb400fa027441b403 /CONTRIBUTING.md
parentffc6aa3abcb0f823b43b63db1666913565e6f934 (diff)
downloaddjango-rest-framework-dfab9af294972720f59890967cd9ae1a6c0796b6.tar.bz2
Minor: fix spelling and grammar, mostly in 3.0 announcement
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a6dd05a0..1b199534 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -75,7 +75,7 @@ You can also use the excellent [`tox`][tox] testing tool to run the tests agains
It's a good idea to make pull requests early on. A pull request represents the start of a discussion, and doesn't necessarily need to be the final, finished submission.
-It's also always best to make a new branch before starting work on a pull request. This means that you'll be able to later switch back to working on another seperate issue without interfering with an ongoing pull requests.
+It's also always best to make a new branch before starting work on a pull request. This means that you'll be able to later switch back to working on another separate issue without interfering with an ongoing pull requests.
It's also useful to remember that if you have an outstanding pull request then pushing new commits to your GitHub repo will also automatically update the pull requests.