Removed versionadded/changed annotations for 4.1.

docs/ref/forms/api.txt

@@ -539,11 +539,6 @@ By default, a property returning the value of the renderer's
 as a string template name in order to override that for a particular form
 class.
 
-.. versionchanged:: 4.1
-
-    In older versions ``template_name`` defaulted to the string value
-    ``'django/forms/default.html'``.
-
 ``render()``
 ~~~~~~~~~~~~
 
@@ -604,14 +599,10 @@ template name.
 
 .. attribute:: Form.template_name_div
 
-.. versionadded:: 4.1
-
 The template used by ``as_div()``. Default: ``'django/forms/div.html'``.
 
 .. method:: Form.as_div()
 
-.. versionadded:: 4.1
-
 ``as_div()`` renders the form as a series of ``<div>`` elements, with each
 ``<div>`` containing one field, such as:
 
@@ -1196,8 +1187,6 @@ Attributes of ``BoundField``
 
 .. attribute:: BoundField.use_fieldset
 
-    .. versionadded:: 4.1
-
     Returns the value of this BoundField widget's ``use_fieldset`` attribute.
 
 .. attribute:: BoundField.widget_type
@@ -1292,14 +1281,8 @@ Methods of ``BoundField``
     overriding the default template, see also
     :ref:`overriding-built-in-form-templates`.
 
-    .. versionchanged:: 4.1
-
-        The ``tag`` argument was added.
-
 .. method:: BoundField.legend_tag(contents=None, attrs=None, label_suffix=None)
 
-    .. versionadded:: 4.1
-
     Calls :meth:`.label_tag` with ``tag='legend'`` to render the label with
     ``<legend>`` tags. This is useful when rendering radio and multiple
     checkbox widgets where ``<legend>`` may be more appropriate than a

docs/ref/forms/fields.txt

@@ -527,10 +527,6 @@ For each field, we describe the default widget used if you don't specify
 
         Limit valid inputs to an integral multiple of ``step_size``.
 
-    .. versionchanged:: 4.1
-
-        The ``step_size`` argument was added.
-
 ``DurationField``
 -----------------
 
@@ -662,8 +658,6 @@ For each field, we describe the default widget used if you don't specify
 
     .. attribute:: step_size
 
-        .. versionadded:: 4.1
-
         Limit valid inputs to an integral multiple of ``step_size``.
 
 ``GenericIPAddressField``
@@ -797,8 +791,6 @@ For each field, we describe the default widget used if you don't specify
 
     .. attribute:: step_size
 
-        .. versionadded:: 4.1
-
         Limit valid inputs to an integral multiple of ``step_size``.
 
 ``JSONField``

docs/ref/forms/models.txt

@@ -72,10 +72,6 @@ Model Form API reference. For introductory material about model forms, see the
 
     See :ref:`model-formsets` for example usage.
 
-    .. versionchanged:: 4.1
-
-        The ``edit_only`` argument was added.
-
 ``inlineformset_factory``
 =========================
 
@@ -89,7 +85,3 @@ Model Form API reference. For introductory material about model forms, see the
     the ``parent_model``, you must specify a ``fk_name``.
 
     See :ref:`inline-formsets` for example usage.
-
-    .. versionchanged:: 4.1
-
-        The ``edit_only`` argument was added.

docs/ref/forms/renderers.txt

@@ -49,8 +49,6 @@ should return a rendered templates (as a string) or raise
 
     .. attribute:: form_template_name
 
-        .. versionadded:: 4.1
-
         The default name of the template to use to render a form.
 
         Defaults to ``"django/forms/default.html"``, which is a proxy for
@@ -64,8 +62,6 @@ should return a rendered templates (as a string) or raise
 
     .. attribute:: formset_template_name
 
-        .. versionadded:: 4.1
-
         The default name of the template to use to render a formset.
 
         Defaults to ``"django/forms/formsets/default.html"``, which is a proxy
@@ -111,8 +107,6 @@ If you want to render templates with customizations from your
 
 .. class:: DjangoDivFormRenderer
 
-.. versionadded:: 4.1
-
 Subclass of :class:`DjangoTemplates` that specifies
 :attr:`~BaseRenderer.form_template_name` and
 :attr:`~BaseRenderer.formset_template_name` as ``"django/forms/div.html"`` and
@@ -147,8 +141,6 @@ widgets due to their usage of Django template tags.
 
 .. class:: Jinja2DivFormRenderer
 
-.. versionadded:: 4.1
-
 A transitional renderer as per :class:`DjangoDivFormRenderer` above, but
 subclassing :class:`Jinja2` for use with the Jinja2 backend.
 

docs/ref/forms/widgets.txt

@@ -318,8 +318,6 @@ foundation for custom widgets.
 
     .. attribute:: Widget.use_fieldset
 
-        .. versionadded:: 4.1
-
         An attribute to identify if the widget should be grouped in a
         ``<fieldset>`` with a ``<legend>`` when rendered. Defaults to ``False``
         but is ``True`` when the widget contains multiple ``<input>`` tags such as