From f6af24fe4007d5eb52c919c2db5d493de06080d8 Mon Sep 17 00:00:00 2001 From: Jon Dufresne Date: Wed, 17 Aug 2016 07:27:33 -0700 Subject: [PATCH] [1.10.x] Fixed incorrect doc reference to Field.initial. Backport of 4773ed2e313c67ed9d4a77d5fe24ca7ed34172cf from master --- docs/ref/forms/api.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt index c468dc38a0..c9e627ddcc 100644 --- a/docs/ref/forms/api.txt +++ b/docs/ref/forms/api.txt @@ -231,8 +231,8 @@ 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.Field` defines :attr:`~Form.initial` *and* -you include ``initial`` when instantiating the ``Form``, then the latter +If a :class:`~django.forms.Field` defines :attr:`~Field.initial` *and* you +include :attr:`~Form.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::