Removed versionadded/changed annotations for 4.1.

docs/topics/forms/formsets.txt

@@ -317,10 +317,6 @@ And here is a custom error message::
     >>> formset.non_form_errors()
     ['Sorry, something went wrong.']
 
-.. versionchanged:: 4.1
-
-    The ``'too_few_forms'`` and ``'too_many_forms'`` keys were added.
-
 Custom formset validation
 -------------------------
 
@@ -804,16 +800,8 @@ Formsets have the following attributes and methods associated with rendering:
     then each form in the formset as per the template defined by the form's
     :attr:`~django.forms.Form.template_name`.
 
-    .. versionchanged:: 4.1
-
-        In older versions ``template_name`` defaulted to the string value
-        ``'django/forms/formset/default.html'``.
-
-
 .. attribute:: BaseFormSet.template_name_div
 
-    .. versionadded:: 4.1
-
     The name of the template used when calling :meth:`.as_div`. By default this
     is ``"django/forms/formsets/div.html"``. This template renders the
     formset's management form and then each form in the formset as per the

docs/topics/forms/index.txt

@@ -552,11 +552,6 @@ the :meth:`.Form.render`. Here's an example of this being used in a view::
 
 See :ref:`ref-forms-api-outputting-html` for more details.
 
-.. versionchanged:: 4.1
-
-    The ability to set the default ``form_template_name`` on the form renderer
-    was added.
-
 Form rendering options
 ----------------------
 
@@ -754,15 +749,11 @@ Useful attributes on ``{{ field }}`` include:
 
 ``{{ field.legend_tag }}``
 
-    .. versionadded:: 4.1
-
     Similar to ``field.label_tag`` but uses a ``<legend>`` tag in place of
     ``<label>``, for widgets with multiple inputs wrapped in a ``<fieldset>``.
 
 ``{{ field.use_fieldset }}``
 
-    .. versionadded:: 4.1
-
     This attribute is ``True`` if the form field's widget contains multiple
     inputs that should be semantically grouped in a ``<fieldset>`` with a
     ``<legend>`` to improve accessibility. An example use in a template:

docs/topics/forms/media.txt

@@ -118,11 +118,6 @@ If this last CSS definition were to be rendered, it would become the following H
     <link href="http://static.example.com/lo_res.css" media="tv,projector" rel="stylesheet">
     <link href="http://static.example.com/newspaper.css" media="print" rel="stylesheet">
 
-.. versionchanged:: 4.1
-
-    In older versions, the ``type="text/css"`` attribute is included in CSS
-    links.
-
 ``js``
 ------
 
@@ -260,8 +255,6 @@ Or if :mod:`~django.contrib.staticfiles` is configured using the
 Paths as objects
 ----------------
 
-.. versionadded:: 4.1
-
 Asset paths may also be given as hashable objects implementing an
 ``__html__()`` method. The ``__html__()`` method is typically added using the
 :func:`~django.utils.html.html_safe` decorator. The object is responsible for

docs/topics/forms/modelforms.txt

@@ -995,8 +995,6 @@ of forms displayed (1000). In practice this is equivalent to no limit.
 Preventing new objects creation
 -------------------------------
 
-.. versionadded:: 4.1
-
 Using the ``edit_only`` parameter, you can prevent creation of any new
 objects::