diff options
| author | Markus Holtermann <info@markusholtermann.eu> | 2014-12-17 14:01:19 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-12-17 08:24:00 -0500 |
| commit | c7786550c4ed396b8580db58f7da60e850894d19 (patch) | |
| tree | e4e0920c0ab61d15b18fd7df50e8cf6b5a363c63 /docs/topics/forms | |
| parent | 1c5cbf5e5d5b350f4df4aca6431d46c767d3785a (diff) | |
Fixed display of lists after website redesign
Thanks Brian Jacobel for the report. refs django/djangoproject.com#197
Diffstat (limited to 'docs/topics/forms')
| -rw-r--r-- | docs/topics/forms/index.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index c11b96ba15..85c03a48b8 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -148,9 +148,9 @@ Instantiating, processing, and rendering forms When rendering an object in Django, we generally: - 1. get hold of it in the view (fetch it from the database, for example) - 2. pass it to the template context - 3. expand it to HTML markup using template variables +1. get hold of it in the view (fetch it from the database, for example) +2. pass it to the template context +3. expand it to HTML markup using template variables Rendering a form in a template involves nearly the same work as rendering any other kind of object, but there are some key differences. |