summaryrefslogtreecommitdiff
path: root/docs/topics/forms/modelforms.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/forms/modelforms.txt')
-rw-r--r--docs/topics/forms/modelforms.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index 024479508a..7049464f86 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -705,14 +705,14 @@ There are three ways to render a formset in a Django template.
First, you can let the formset do most of the work::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset }}
</form>
Second, you can manually render the formset, but let the form deal with
itself::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form }}
@@ -725,7 +725,7 @@ form as shown above. See the :ref:`management form documentation
Third, you can manually render each field::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{% for field in form %}
@@ -738,7 +738,7 @@ If you opt to use this third method and you don't iterate over the fields with
a ``{% for %}`` loop, you'll need to render the primary key field. For example,
if you were rendering the ``name`` and ``age`` fields of a model::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form.id }}