From fbc06eef1af1d7ecf91fae5a94a1994f356ffd22 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 25 Dec 2012 09:56:22 -0500 Subject: [1.5.X] Fixed broken links, round 3. refs #19516 Backport of b3a8c9dab8 from master --- docs/ref/forms/api.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/ref/forms/api.txt') diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index dffef314b7..ab1f4b0eea 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -150,11 +150,11 @@ it's not necessary to include every field in your form. For example:: These values are only displayed for unbound forms, and they're not used as fallback values if a particular value isn't provided. -Note that if a :class:`~django.forms.fields.Field` defines -:attr:`~Form.initial` *and* you include ``initial`` when instantiating the -``Form``, then the latter ``initial`` will have precedence. In this example, -``initial`` is provided both at the field level and at the form instance level, -and the latter gets precedence:: +Note that if a :class:`~django.forms.Field` defines :attr:`~Form.initial` *and* +you include ``initial`` when instantiating the ``Form``, then the latter +``initial`` will have precedence. In this example, ``initial`` is provided both +at the field level and at the form instance level, and the latter gets +precedence:: >>> class CommentForm(forms.Form): ... name = forms.CharField(initial='class') -- cgit v1.3