diff --git a/docs/reference/contrib/forms/customization.md b/docs/reference/contrib/forms/customization.md
index 6126fc1cb0..64feb0f1ed 100644
--- a/docs/reference/contrib/forms/customization.md
+++ b/docs/reference/contrib/forms/customization.md
@@ -629,10 +629,6 @@ class FormPage(AbstractEmailForm):
     # content_panels = ...
 ```
 
-```{versionchanged} 6.1
-The `SubmissionsListView` class is now a subclass of Wagtail's generic `BaseListingView`. As a result, the `ordering` attribute has been renamed to `default_ordering`.
-```
-
 ## Adding a custom field type
 
 First, make the new field type available in the page editor by changing your `FormField` model.
diff --git a/docs/reference/settings.md b/docs/reference/settings.md
index 9511575637..b2ac511a48 100644
--- a/docs/reference/settings.md
+++ b/docs/reference/settings.md
@@ -676,10 +676,6 @@ WAGTAIL_PASSWORD_REQUIRED_TEMPLATE = 'myapp/password_required.html'
 
 This is the path to the Django template which will be used to display the "password required" form when a user accesses a private page. For more details, see the [](private_pages) documentation.
 
-```{versionchanged} 6.1
-`PASSWORD_REQUIRED_TEMPLATE` has been deprecated and renamed to `WAGTAIL_PASSWORD_REQUIRED_TEMPLATE`.
-```
-
 ### `WAGTAILDOCS_PASSWORD_REQUIRED_TEMPLATE`
 
 ```python
@@ -688,10 +684,6 @@ WAGTAILDOCS_PASSWORD_REQUIRED_TEMPLATE = 'myapp/document_password_required.html'
 
 As above, but for password restrictions on documents. For more details, see the [](private_pages) documentation.
 
-```{versionchanged} 6.1
-`DOCUMENT_PASSWORD_REQUIRED_TEMPLATE` has been deprecated and renamed to `WAGTAILDOCS_PASSWORD_REQUIRED_TEMPLATE`.
-```
-
 ### `WAGTAIL_FRONTEND_LOGIN_TEMPLATE`
 
 The basic login page can be customized with a custom template.
diff --git a/docs/topics/permissions.md b/docs/topics/permissions.md
index 5fd4f926ef..cb7d9cff49 100644
--- a/docs/topics/permissions.md
+++ b/docs/topics/permissions.md
@@ -63,10 +63,6 @@ Users are not allowed to move or delete the collection that is used to assign th
 
 See Django's documentation on [custom permissions](https://docs.djangoproject.com/en/stable/topics/auth/customizing/#custom-permissions) for details on how to set permissions up.
 
-```{versionadded} 6.1
-The ability to have custom permissions with codenames starting with `add_`, `change_`, or `delete_` was added.
-```
-
 Permissions for models registered with Wagtail will automatically show up in the Wagtail admin Group edit form. For other models, you can also add the permissions using the `register_permissions` hook (see [](register_permissions)).
 
 To add a custom permission to be used in the Wagtail admin without relating to a specific model, you can create it using the content type of the `wagtail.admin.models.Admin` model. For example:
@@ -87,10 +83,6 @@ permission = Permission.objects.create(
 
 After registering the permission using the `register_permissions` hook, it will be displayed in the Wagtail admin Group edit form under the 'Other permissions' section, alongside the 'Can access Wagtail admin' permission.
 
-```{versionadded} 6.1
-The ability to register custom permissions in the "Other permissions" section was added.
-```
-
 ## `FieldPanel` and `PanelGroup` permissions
 
 Permissions can be used to restrict access to fields within the editor interface. See `permission` on [FieldPanel](field_panel).