From 0c3a23d2b9fd5399c2cdda8c72d43c960040886a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Fievet?= Date: Fri, 5 Sep 2014 19:06:20 +0200 Subject: [PATCH] [1.7.x] Fixed typo in docs/topics/checks.txt. Backport of 0f90f741de from master --- docs/topics/checks.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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