summaryrefslogtreecommitdiff
path: root/docs/ref/forms
diff options
context:
space:
mode:
authorMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2008-12-22 04:19:41 +0000
committerMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2008-12-22 04:19:41 +0000
commit6dd5c855d41ce0e4153742e7dff3335ee194cc64 (patch)
treed28925bb29a3263d300d72678d8145ae9c734743 /docs/ref/forms
parent73534cd9420a27eda6c725635fa1e4a3f1f9fbac (diff)
[1.0.X] Changed some ReST formatting of headers (in forms/validation.txt).
Backport of r9666 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9667 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref/forms')
-rw-r--r--docs/ref/forms/validation.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/forms/validation.txt b/docs/ref/forms/validation.txt
index 3ad9ce956e..3cfd6e0bfb 100644
--- a/docs/ref/forms/validation.txt
+++ b/docs/ref/forms/validation.txt
@@ -90,7 +90,7 @@ already know which fields have passed their individual validation requirements.
.. _described later:
Form subclasses and modifying field errors
-==========================================
+------------------------------------------
Sometimes, in a form's ``clean()`` method, you will want to add an error
message to a particular field in the form. This won't always be appropriate
@@ -134,7 +134,7 @@ There is an example of modifying ``self._errors`` in the following section.
explanation makes you feel more comfortable. The result is the same.
Using validation in practice
-=============================
+----------------------------
The previous sections explained how validation works in general for forms.
Since it can sometimes be easier to put things into place by seeing each