summaryrefslogtreecommitdiff
path: root/docs/topics/forms/modelforms.txt
diff options
context:
space:
mode:
authorClifford Gama <53076065+cliff688@users.noreply.github.com>2025-03-13 20:18:35 +0200
committerGitHub <noreply@github.com>2025-03-13 15:18:35 -0300
commitefe3ca09e029c63e25f6e19843cb0c68cc7fa816 (patch)
treedfa385b0b2fea4caa7292915eb0a8b92b00e9b30 /docs/topics/forms/modelforms.txt
parente7a9d756eedd0317132c81c3695d4a34bba5dcd3 (diff)
Fixed incorrect formatting for inline pluralized code references in docs.
Diffstat (limited to 'docs/topics/forms/modelforms.txt')
-rw-r--r--docs/topics/forms/modelforms.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index ef916d882d..b320d7fc04 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -700,10 +700,10 @@ will be localized.
Form inheritance
----------------
-As with basic forms, you can extend and reuse ``ModelForms`` by inheriting
-them. This is useful if you need to declare extra fields or extra methods on a
-parent class for use in a number of forms derived from models. For example,
-using the previous ``ArticleForm`` class:
+As with basic forms, you can extend and reuse ``ModelForm`` classes by
+inheriting them. This is useful if you need to declare extra fields or extra
+methods on a parent class for use in a number of forms derived from models.
+For example, using the previous ``ArticleForm`` class:
.. code-block:: pycon
@@ -983,7 +983,7 @@ value (``instances``, in the above example).
When fields are missing from the form (for example because they have been
excluded), these fields will not be set by the ``save()`` method. You can find
more information about this restriction, which also holds for regular
-``ModelForms``, in `Selecting the fields to use`_.
+model forms, in `Selecting the fields to use`_.
Pass ``commit=False`` to return the unsaved model instances:
@@ -1104,7 +1104,7 @@ above, in :ref:`saving-objects-in-the-formset`.)
Overriding ``clean()`` on a ``ModelFormSet``
--------------------------------------------
-Just like with ``ModelForms``, by default the ``clean()`` method of a
+Just like with a ``ModelForm``, by default the ``clean()`` method of a
``ModelFormSet`` will validate that none of the items in the formset violate
the unique constraints on your model (either ``unique``, ``unique_together`` or
``unique_for_date|month|year``). If you want to override the ``clean()`` method