Clean up unintentional whitespace in documentation

docs/contributing/committing.md

@@ -72,11 +72,11 @@ The `CHANGELOG.txt` contains a short summary of each new feature, refactoring, o
 Each summary should be a single line.
 To easily identify the most relevant changes to users, items are grouped together in the following order:
 
-* Major features (no prefix) - things that will inspire users to upgrade to a new release
-* Minor enhancements (no prefix) - other improvements to the developer or end user experience
-* Bug fixes (prefixed with "Fix:") - things that address broken behaviour from previous releases
-* Documentation (prefixed with "Docs:") - changes to documentation that do not accompany a specific code change; reorganisations, tutorials, recipes and so on
-* Maintenance (prefixed with "Maintenance:") - cleanup, refactoring and other changes to code or tooling that are not intended to have a visible effect to developers or end users
+-   Major features (no prefix) - things that will inspire users to upgrade to a new release
+-   Minor enhancements (no prefix) - other improvements to the developer or end user experience
+-   Bug fixes (prefixed with "Fix:") - things that address broken behaviour from previous releases
+-   Documentation (prefixed with "Docs:") - changes to documentation that do not accompany a specific code change; reorganisations, tutorials, recipes and so on
+-   Maintenance (prefixed with "Maintenance:") - cleanup, refactoring and other changes to code or tooling that are not intended to have a visible effect to developers or end users
 
 The name of the contributor should be added at the end of the summary, in brackets.
 For example:

docs/releases/4.1.md

@@ -17,7 +17,7 @@ Wagtail 4.1 is designated a Long Term Support (LTS) release. Long Term Support r
 
 To help with onboarding new users, Wagtail now displays a banner on the dashboard, pointing users to our Editor Guide. The sidebar also contains a new "Help" menu item with a prominent indicator to call attention to the new content: a "What’s new" page showcasing new features, and a link to the Editor Guide.
 
-Users can dismiss the new banner and the sidebar items’ indicators by interacting with the corresponding UI element. We store the state in the user’s profile  so we only call attention to the content once.
+Users can dismiss the new banner and the sidebar items’ indicators by interacting with the corresponding UI element. We store the state in the user’s profile so we only call attention to the content once.
 
 To turn off the new banner, set [`WAGTAIL_ENABLE_WHATS_NEW_BANNER`](wagtail_enable_whats_new_banner) to `False` in your settings. The new menu items can be removed and customised with the following hooks:
 
@@ -43,7 +43,7 @@ Snippet models that inherit from `DraftStateMixin` can now be assigned go-live a
 
 ### Object usage reporting
 
-Images, documents and snippets now provide a usage report, listing the places where references to those objects appear.  This report is powered by a new `ReferenceIndex` model which records cross-references between objects whenever those objects to save; this allows it to work more efficiently than the old report available through the `WAGTAIL_USAGE_COUNT_ENABLED` setting, as well as handling references within StreamField and rich text fields.
+Images, documents and snippets now provide a usage report, listing the places where references to those objects appear. This report is powered by a new `ReferenceIndex` model which records cross-references between objects whenever those objects to save; this allows it to work more efficiently than the old report available through the `WAGTAIL_USAGE_COUNT_ENABLED` setting, as well as handling references within StreamField and rich text fields.
 
 Note that on first upgrading to Wagtail 4.1, you will need to run the `rebuild_references_index` management command to populate the references table and ensure that reference counts are displayed accurately.