From 92a6c1429162d132a00c8b06efc960ba1d2dcc3e Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Fri, 24 Oct 2008 07:14:30 +0000 Subject: Fixed #9384 -- Fixed a couple of typos. Thanks, Thomas Güttler and romke. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit git-svn-id: http://code.djangoproject.com/svn/django/trunk@9255 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/forms/validation.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/ref/forms') diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt index af3b7f23f3..25b900e824 100644 --- a/docs/ref/forms/validation.txt +++ b/docs/ref/forms/validation.txt @@ -100,10 +100,10 @@ through the ``Form.non_field_errors()`` method. When you really do need to attach the error to a particular field, you should store (or amend) a key in the `Form._errors` attribute. This attribute is an -instance of a ``django.form.utils.ErrorDict`` class. Essentially, though, it's +instance of a ``django.forms.util.ErrorDict`` class. Essentially, though, it's just a dictionary. There is a key in the dictionary for each field in the form that has an error. Each value in the dictionary is a -``django.form.utils.ErrorList`` instance, which is a list that knows how to +``django.forms.util.ErrorList`` instance, which is a list that knows how to display itself in different ways. So you can treat `_errors` as a dictionary mapping field names to lists. -- cgit v1.3