From 1130f5e6b79588944ee3f72ff9fd698c7b97c9db Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Sat, 12 May 2007 17:11:19 +0000 Subject: [PATCH] Fixed some ReST errors in docs/newforms.txt from [5212] git-svn-id: http://code.djangoproject.com/svn/django/trunk@5213 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/newforms.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/newforms.txt b/docs/newforms.txt index a7c250be01..123b554bde 100644 --- a/docs/newforms.txt +++ b/docs/newforms.txt @@ -942,7 +942,8 @@ the full list of conversions: ``TimeField`` ``TimeField`` ``URLField`` ``URLField`` with ``verify_exists`` set to the model field's ``verify_exists`` - ``USStateField`` ``CharField with ``widget=USStateSelect`` + ``USStateField`` ``CharField`` with + ``widget=USStateSelect`` (``USStateSelect`` is from ``django.contrib.localflavor.us``) ``XMLField`` ``CharField`` with ``widget=Textarea`` @@ -1094,7 +1095,7 @@ The default field types, as described in the "Field types" table above, are sensible defaults; if you have a ``DateField`` in your model, chances are you'd want that to be represented as a ``DateField`` in your form. But ``form_for_model()`` gives you the flexibility of changing the form field type -for a given model field. You do this by specifying a *formfield callback*. +for a given model field. You do this by specifying a **formfield callback**. A formfield callback is a function that, when provided with a model field, returns a form field instance. When constructing a form, ``form_for_model()``