diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt
index 5f6db43..5f66e3b 100644
|
a
|
b
|
In this code, if the validation error is raised, the form will display an
|
| 372 | 372 | error message at the top of the form (normally) describing the problem. |
| 373 | 373 | |
| 374 | 374 | Note that the call to ``super(ContactForm, self).clean()`` in the example code |
| 375 | | ensures that any validation logic in parent classes is maintained. |
| | 375 | ensures that any validation logic in parent classes is maintained. If your form |
| | 376 | inherits another that doesn't return a ``cleaned_data`` dictionary in its |
| | 377 | ``clean()`` method, then don't assign ``cleaned_data`` to the result of the |
| | 378 | ``super()`` call and use ``self.cleaned_data`` instead:: |
| | 379 | |
| | 380 | def clean(self): |
| | 381 | super(ContactForm, self).clean() |
| | 382 | cc_myself = self.cleaned_data.get("cc_myself") |
| | 383 | ... |
| 376 | 384 | |
| 377 | 385 | The second approach might involve assigning the error message to one of the |
| 378 | 386 | fields. In this case, let's assign an error message to both the "subject" and |