summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSébastien Fievet <zyegfryed@gmail.com>2014-09-05 19:06:20 +0200
committerTim Graham <timograham@gmail.com>2014-09-05 14:28:46 -0400
commit0f90f741de913a4502adc51063df77278d01a5ca (patch)
tree91d77a7a15b8b0827847f49d71ebda45af5f55d3
parent885ff6845e54511022677c1f28b84ddd4f2165dd (diff)
Fixed typo in docs/topics/checks.txt.
-rw-r--r--docs/topics/checks.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt
index aabebd1db2..076b63483d 100644
--- a/docs/topics/checks.txt
+++ b/docs/topics/checks.txt
@@ -151,7 +151,7 @@ Fields, models, and model managers all implement a ``check()`` method that is
already registered with the check framework. If you want to add extra checks,
you can extend the implementation on the base class, perform any extra
checks you need, and append any messages to those generated by the base class.
-It's recommended the you delegate each check to a separate methods.
+It's recommended that you delegate each check to separate methods.
Consider an example where you are implementing a custom field named
``RangedIntegerField``. This field adds ``min`` and ``max`` arguments to the