6 files changed, 0 insertions, 54 deletions
diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt
index 640130beb0..fc2b00f109 100644
--- a/docs/topics/auth/default.txt
+++ b/docs/topics/auth/default.txt
@@ -823,12 +823,6 @@ access with an HTTP 403 Forbidden response. Anonymous users are redirected to
 the login page or shown an HTTP 403 Forbidden response, depending on the
 :attr:`~django.contrib.auth.mixins.AccessMixin.raise_exception` attribute.
 
-.. versionchanged:: 2.1
-
-    In older versions, authenticated users who lacked permissions were
-    redirected to the login page (which resulted in a loop) instead of
-    receiving an HTTP 403 Forbidden response.
-
 .. class:: AccessMixin
 
     .. attribute:: login_url
diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt
index 4a4497cf8a..1f86a1820c 100644
--- a/docs/topics/auth/passwords.txt
+++ b/docs/topics/auth/passwords.txt
@@ -412,14 +412,6 @@ from the ``User`` model.
     Returns ``False`` if the password is a result of
     :meth:`.User.set_unusable_password`.
 
-    .. versionchanged:: 2.1
-
-        In older versions, this also returns ``False`` if the password is
-        ``None`` or an empty string, or if the password uses a hasher that's
-        not in the :setting:`PASSWORD_HASHERS` setting. That behavior is
-        considered a bug as it prevents users with such passwords from
-        requesting a password reset.
-
 .. _password-validation:
 
 Password validation
@@ -538,10 +530,6 @@ Django includes four validators:
     common passwords. This file should contain one lowercase password per line
     and may be plain text or gzipped.
 
-    .. versionchanged:: 2.1
-
-        In older versions, a list of 1,000 common passwords is used.
-
 .. class:: NumericPasswordValidator()
 
     Validates whether the password is not entirely numeric.
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index 6827b3f40e..57c4a685eb 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -329,10 +329,6 @@ cross-process caching is possible. This obviously also means the local memory
 cache isn't particularly memory-efficient, so it's probably not a good choice
 for production environments. It's nice for development.
 
-.. versionchanged:: 2.1
-
-    Older versions use a pseudo-random culling strategy rather than LRU.
-
 Dummy caching (for development)
 -------------------------------
 
@@ -907,8 +903,6 @@ from the cache, not just the keys set by your application. ::
 
 .. method:: cache.touch(key, timeout=DEFAULT_TIMEOUT, version=None)
 
-.. versionadded:: 2.1
-
 ``cache.touch()`` sets a new expiration for a key. For example, to update a key
 to expire 10 seconds from now::
 
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index 04b1060909..3b09e41617 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -1778,10 +1778,6 @@ language choice in the user's session. It also saves the language choice in a
 cookie that is named ``django_language`` by default. (The name can be changed
 through the :setting:`LANGUAGE_COOKIE_NAME` setting.)
 
-.. versionchanged:: 2.1
-
-    In older versions, the cookie is only set if session support isn't enabled.
-
 After setting the language choice, Django looks for a ``next`` parameter in the
 ``POST`` or ``GET`` data. If that is found and Django considers it to be a safe
 URL (i.e. it doesn't point to a different host and uses a safe scheme), a
@@ -2098,10 +2094,6 @@ etc. Untranslated strings for territorial language variants use the translations
 of the generic language. For example, untranslated ``pt_BR`` strings use ``pt``
 translations.
 
-.. versionchanged:: 2.1
-
-    Fallback to the generic language as described above was added.
-
 This way, you can write applications that include their own translations, and
 you can override base translations in your project. Or, you can just build
 a big project out of several apps and put all translations into one big common
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 2f33b97878..ae9c92dc3b 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -683,10 +683,6 @@ Django can serialize the following:
 - Any class reference (must be in module's top-level scope)
 - Anything with a custom ``deconstruct()`` method (:ref:`see below <custom-deconstruct-method>`)
 
-.. versionchanged:: 2.1
-
-    Serialization support for :class:`functools.partialmethod` was added.
-
 .. versionchanged:: 2.2
 
     Serialization support for ``NoneType`` was added.
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index e656f89124..233edde2ce 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -128,10 +128,6 @@ Use the ``django.test.Client`` class to make requests.
     The ``json_encoder`` argument allows setting a custom JSON encoder for
     the JSON serialization that's described in :meth:`post`.
 
-    .. versionchanged:: 2.1
-
-        The ``json_encoder`` argument was added.
-
     Once you have a ``Client`` instance, you can call any of the following
     methods:
 
@@ -221,12 +217,6 @@ Use the ``django.test.Client`` class to make requests.
         :class:`Client`. This serialization also happens for :meth:`put`,
         :meth:`patch`, and :meth:`delete` requests.
 
-        .. versionchanged:: 2.1
-
-            The JSON serialization described above was added. In older versions,
-            you can call :func:`json.dumps` on ``data`` before passing it to
-            ``post()`` to achieve the same thing.
-
         .. versionchanged:: 2.2
 
             The JSON serialization was extended to support lists and tuples. In
@@ -1449,8 +1439,6 @@ your test suite.
 .. method:: SimpleTestCase.assertWarnsMessage(expected_warning, expected_message, callable, *args, **kwargs)
             SimpleTestCase.assertWarnsMessage(expected_warning, expected_message)
 
-    .. versionadded:: 2.1
-
     Analogous to :meth:`SimpleTestCase.assertRaisesMessage` but for
     :meth:`~unittest.TestCase.assertWarnsRegex` instead of
     :meth:`~unittest.TestCase.assertRaisesRegex`.
@@ -1755,12 +1743,6 @@ class. Given::
 ``SampleTestCaseChild.test`` will be labeled with ``'slow'``, ``'core'``,
 ``'bar'``, and ``'foo'``.
 
-.. versionchanged:: 2.1
-
-   In older versions, tagged tests don't inherit tags from classes, and
-   tagged subclasses don't inherit tags from superclasses. For example,
-   ``SampleTestCaseChild.test`` is labeled only with ``'bar'``.
-
 Then you can choose which tests to run. For example, to run only fast tests:
 
 .. console::