diff options
| author | Min ho Kim <minho42@gmail.com> | 2019-09-11 20:55:17 +1000 |
|---|---|---|
| committer | Carlton Gibson <carlton@noumenal.es> | 2019-10-02 15:50:46 +0200 |
| commit | 103a6f4307b4402198b03d79c683e195686572e1 (patch) | |
| tree | a56a9fb838a38cbf8e44a114ed2ec9491213854d /docs/intro | |
| parent | f1d4a540b29c6766b988852bc302ac036a2d82e2 (diff) | |
Fixed some typos in comments and docs.
Thanks to Mads Jenson for review.
Diffstat (limited to 'docs/intro')
| -rw-r--r-- | docs/intro/contributing.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt index b21ec57f6d..02bed83e07 100644 --- a/docs/intro/contributing.txt +++ b/docs/intro/contributing.txt @@ -194,7 +194,7 @@ When contributing to Django it's very important that your code changes don't introduce bugs into other areas of Django. One way to check that Django still works after you make your changes is by running Django's test suite. If all the tests still pass, then you can be reasonably sure that your changes -work and haven't broken other parts Django. If you've never run Django's test +work and haven't broken other parts of Django. If you've never run Django's test suite before, it's a good idea to run it once beforehand to get familiar with its output. |
