General spelling fixes

CHANGELOG.txt

@@ -126,7 +126,7 @@ Changelog
  * Fix: `wagtail.contrib.sitemaps` no longer depends on SiteMiddleware (Matt Westcott)
  * Fix: Purge image renditions cache when renditions are deleted (Pascal Widdershoven, Matt Westcott)
  * Fix: Image / document forms now display non-field errors such as `unique_together` constraints (Matt Westcott)
- * Fix: Make "Site" chooser in site settings translateable (Andreas Bernacca)
+ * Fix: Make "Site" chooser in site settings translatable (Andreas Bernacca)
  * Fix: Add missing dropdown icons to image upload, document upload, and site settings screens (Andreas Bernacca)
  * Fix: Prevent snippets’ bulk delete button from being present for screen reader users when it’s absent for sighted users (LB (Ben Johnston))
  * Fix: Fix group permission checkboxes not being clickable in IE11 (LB (Ben Johnston))
@@ -253,7 +253,7 @@ Changelog
  * Fix: Added `verbose_name_plural` to form submission model (Janneke Janssen)
  * Fix: Prevent `update_index` failures and incorrect front-end rendering on blank `TableBlock` (Carlo Ascani)
  * Fix: Dropdown initialisation on the search page after AJAX call (Eric Sherman)
- * Fix: Make sure all modal chooser search results correspond to the latest search by canceling previous requests (Esper Kuijs)
+ * Fix: Make sure all modal chooser search results correspond to the latest search by cancelling previous requests (Esper Kuijs)
 
 
 2.7.4 (20.07.2020)
@@ -398,7 +398,7 @@ Changelog
  * Fix: Avoid rendering entire form in EditHandler's `repr` method (Alex Tomkins)
  * Fix: Add empty alt attributes to HTML output of Embedly and oEmbed embed finders (Andreas Bernacca)
  * Fix: Add empty alt attributes to all images in the CMS admin (Andreas Bernacca)
- * Fix: Make URL generator preview image alt translateable (Thibaud Colas)
+ * Fix: Make URL generator preview image alt translatable (Thibaud Colas)
  * Fix: Clear pending AJAX request if error occurs on page chooser (Matt Westcott)
  * Fix: Prevent text from overlapping in focal point editing UI (Beth Menzies)
  * Fix: Screen readers now announce "Dashboard" for the main nav’s logo link instead of Wagtail’s version number (Thibaud Colas)
@@ -475,7 +475,7 @@ Changelog
  * Fix: `send_mail` now correctly uses the `html_message` kwarg for HTML messages (Tiago Requeijo)
  * Fix: Page copying no longer allowed if page model has reached its `max_count` (Andy Babic)
  * Fix: Don't show page type on page chooser button when multiple types are allowed (Thijs Kramer)
- * Fix: Make sure page chooser search results correspond to the latest search by canceling previous requests (Esper Kuijs)
+ * Fix: Make sure page chooser search results correspond to the latest search by cancelling previous requests (Esper Kuijs)
  * Fix: Inform user when moving a page from one parent to another where there is an already existing page with the same slug (Casper Timmers)
  * Fix: User add/edit forms now support form widgets with JS/CSS media (Damian Grinwis)
  * Fix: Rich text processing now preserves non-breaking spaces instead of converting them to normal spaces (Wesley van Lee)

docs/advanced_topics/customisation/page_editing_interface.rst

@@ -86,7 +86,7 @@ The feature identifiers provided on a default Wagtail installation are as follow
  * ``embed`` - embedded media (see :ref:`embedded_content`)
 
 
-We have few additional feature identifiers as well. They are not enabled by default, but you can use them in your list of identifers. These are as follows:
+We have few additional feature identifiers as well. They are not enabled by default, but you can use them in your list of identifiers. These are as follows:
 
 * ``code`` - inline code
 * ``superscript``, ``subscript``, ``strikethrough`` - text formatting

docs/contributing/css_guidelines.rst

@@ -49,7 +49,7 @@ Run the linter from the wagtail project root:
     $ npm run lint:css
 
 
-The linter is configured to check your code for adherance to the guidelines
+The linter is configured to check your code for adherence to the guidelines
 below, plus a little more.
 
 Formatting code

docs/contributing/issue_tracking.rst

@@ -12,7 +12,7 @@ Do not use issues for support queries or other questions ("How do I do X?" - alt
 
 As soon as a ticket is opened - ideally within one day - a member of the core team will give it an initial classification, by either closing it as invalid or assigning it to a milestone. Don't be discouraged if you feel that your ticket has been given a lower priority than it deserves - this decision isn't permanent. We will consider all feedback, and reassign or reopen tickets where appropriate.
 
-(From the other side, this means that the core team member doing the classification should feel free to make bold unilateral decisions - there's no need to seek consensus first. If they make the wrong judgment call, that can always be reversed later.)
+(From the other side, this means that the core team member doing the classification should feel free to make bold unilateral decisions - there's no need to seek consensus first. If they make the wrong judgement call, that can always be reversed later.)
 
 The possible milestones that it might be assigned to are as follows:
 

docs/contributing/security.rst

@@ -8,7 +8,7 @@ Most normal bugs in Wagtail are reported as `GitHub issues <https://github.com/w
 
 Instead, if you believe you’ve found something in Wagtail which has security implications, please send a description of the issue via email to `security@wagtail.io <mailto:security@wagtail.io>`_. Mail sent to that address reaches a subset of the core team, who can forward security issues to other core team members for broader discussion if needed.
 
-Once you’ve submitted an issue via email, you should receive an acknowledgment from a member of the security team within 48 hours, and depending on the action to be taken, you may receive further followup emails.
+Once you’ve submitted an issue via email, you should receive an acknowledgement from a member of the security team within 48 hours, and depending on the action to be taken, you may receive further followup emails.
 
 If you want to send an encrypted email (optional), the public key ID for security@wagtail.io is ``0x6ba1e1a86e0f8ce8``, and this public key is available from most commonly-used keyservers.
 

docs/reference/contrib/modeladmin/menu_item.rst

@@ -69,7 +69,7 @@ If you'd like the menu item for your model to appear in Wagtail's 'Settings'
 sub-menu instead of at the top level, add ``add_to_settings_menu = True`` to
 your ``ModelAdmin`` class.
 
-This will only work for indivdual ``ModelAdmin`` classes registered with their
+This will only work for individual ``ModelAdmin`` classes registered with their
 own ``modeladmin_register`` call. It won't work for members of a
 ``ModelAdminGroup``.
 

docs/reference/settings.rst

@@ -459,7 +459,7 @@ Static file URLs within the Wagtail admin are given a version-specific query str
 API Settings
 ============
 
-For full documenation on API configuration, including these settings, see :ref:`api_v2_configuration` documentation.
+For full documentation on API configuration, including these settings, see :ref:`api_v2_configuration` documentation.
 
 .. code-block:: python
 
@@ -485,12 +485,12 @@ Default is true, setting this to false will disable full text search on all endp
 
     WAGTAILAPI_USE_FRONTENDCACHE = True
 
-Requires ``wagtailfrontendcache`` app to be installed, inidicates the API should use the frontend cache.
+Requires ``wagtailfrontendcache`` app to be installed, indicates the API should use the frontend cache.
 
 Frontend cache
 ==============
 
-For full documenation on frontend cache invalidation, including these settings, see :ref:`frontend_cache_purging`.
+For full documentation on frontend cache invalidation, including these settings, see :ref:`frontend_cache_purging`.
 
 
 .. code-block:: python

docs/releases/1.0.rst

@@ -191,7 +191,7 @@ You no longer need ``LOGIN_URL`` and ``LOGIN_REDIRECT_URL`` to point to Wagtail
 
 If you are upgrading from an older version of Wagtail, you probably want to remove these from your project settings.
 
-Prevously, these two settings needed to be set to ``wagtailadmin_login`` and ``wagtailadmin_dashboard``
+Previously, these two settings needed to be set to ``wagtailadmin_login`` and ``wagtailadmin_dashboard``
 respectively or Wagtail would become very tricky to log in to. This is no longer the case and Wagtail
 should work fine without them.
 

docs/releases/1.1.rst

@@ -41,7 +41,7 @@ A number of inconsistencies around permissions in the admin interface were fixed
  * Removed all permissions for "User profile" (not used)
  * Removed "delete" permission for Images and documents (not used)
  * Users can now access images and documents when they only have the "change" permission (previously required "add" permission as well)
- * Permissions for Users now taken from custom user model, if set (previously always used permissions on Djangos builtin User model)
+ * Permissions for Users now taken from custom user model, if set (previously always used permissions on Django's builtin User model)
  * Groups and Users now respond consistently to their respective "add", "change" and "delete" permissions
 
 Searchable snippets

docs/releases/2.10.rst

@@ -119,7 +119,7 @@ Bug fixes
  * ``wagtail.contrib.sitemaps`` no longer depends on SiteMiddleware (Matt Westcott)
  * Purge image renditions cache when renditions are deleted (Pascal Widdershoven, Matt Westcott)
  * Image / document forms now display non-field errors such as ``unique_together`` constraints (Matt Westcott)
- * Make "Site" chooser in site settings translateable (Andreas Bernacca)
+ * Make "Site" chooser in site settings translatable (Andreas Bernacca)
  * Fix group permission checkboxes not being clickable in IE11 (LB (Ben Johnston))
 
 

docs/releases/2.11.rst

@@ -67,7 +67,7 @@ you run the following command in each environment:
 
 Previously, collections were stored in the order in which they were created - and then sorted by name where displayed in the CMS. Collections are now ordered by treebeard path by default, so the above command must be run to retain alphabetical ordering.
 
-Failure to do this won't affect your current colllections, but may affect your ability to add new ones.
+Failure to do this won't affect your current collections, but may affect your ability to add new ones.
 
 
 ``Site.get_site_root_paths`` now returns language code

docs/releases/2.5.rst

@@ -76,7 +76,7 @@ Bug fixes
  * ``send_mail`` now correctly uses the ``html_message`` kwarg for HTML messages (Tiago Requeijo)
  * Page copying no longer allowed if page model has reached its ``max_count`` (Andy Babic)
  * Don't show page type on page chooser button when multiple types are allowed (Thijs Kramer)
- * Make sure page chooser search results correspond to the latest search by canceling previous requests (Esper Kuijs)
+ * Make sure page chooser search results correspond to the latest search by cancelling previous requests (Esper Kuijs)
  * Inform user when moving a page from one parent to another where there is an already existing page with the same slug (Casper Timmers)
  * User add/edit forms now support form widgets with JS/CSS media (Damian Grinwis)
  * Rich text processing now preserves non-breaking spaces instead of converting them to normal spaces (Wesley van Lee)

docs/releases/2.6.rst

@@ -35,7 +35,7 @@ This release also contains many big improvements for screen reader users:
 * Add empty alt attributes to all images in the CMS admin (Andreas Bernacca)
 * Fixed focus not moving to the pages explorer menu when open (Helen Chapman)
 
-We’ve also had a look at how controls are labeled across the UI for screen reader users:
+We’ve also had a look at how controls are labelled across the UI for screen reader users:
 
 * Add image dimensions in image gallery and image choosers for screen reader users (Helen Chapman)
 * Add more contextual information for screen readers in the explorer menu's links (Helen Chapman)

docs/releases/2.8.rst

@@ -61,7 +61,7 @@ Bug fixes
  * Added ``verbose_name_plural`` to form submission model (Janneke Janssen)
  * Prevent ``update_index`` failures and incorrect front-end rendering on blank ``TableBlock`` (Carlo Ascani)
  * Dropdown initialisation on the search page after AJAX call (Eric Sherman)
- * Make sure all modal chooser search results correspond to the latest search by canceling previous requests (Esper Kuijs)
+ * Make sure all modal chooser search results correspond to the latest search by cancelling previous requests (Esper Kuijs)
 
 
 Upgrade considerations

docs/topics/writing_templates.rst

@@ -17,7 +17,7 @@ Templates
 
 Every type of page or "content type" in Wagtail is defined as a "model" in a file called ``models.py``. If your site has a blog, you might have a ``BlogPage``  model and another called ``BlogPageListing``. The names of the models are up to the Django developer.
 
-For each page model in ``models.py``, Wagtail assumes an HTML template file exists of (almost) the same name. The Front End developer may need to create these templates themselves by refering to ``models.py`` to infer template names from the models defined therein.
+For each page model in ``models.py``, Wagtail assumes an HTML template file exists of (almost) the same name. The Front End developer may need to create these templates themselves by referring to ``models.py`` to infer template names from the models defined therein.
 
 To find a suitable template, Wagtail converts CamelCase names to snake_case. So for a ``BlogPage``, a template ``blog_page.html`` will be expected. The name of the template file can be overridden per model if necessary.
 

wagtail/contrib/routable_page/models.py

@@ -140,7 +140,7 @@ class RoutablePageMixin:
                     'events': EventPage.objects.live().future(),
                 })
 
-        You can also use the ``template`` arguement to specify an alternative
+        You can also use the ``template`` argument to specify an alternative
         template to use for rendering. For example:
 
         .. code-block:: python

wagtail/core/models.py

@@ -1100,7 +1100,7 @@ class Page(AbstractPage, index.Indexed, ClusterableModel, metaclass=PageBase):
         If the page was originally created using a page type that has since
         been removed from the codebase, a generic ``Page`` object will be
         returned (without any custom field values or other functionality
-        present on the orginal class). Usually, deleting these pages is the
+        present on the original class). Usually, deleting these pages is the
         best course of action, but there is currently no safe way for Wagtail
         to do that at migration time.
         """
@@ -2097,7 +2097,7 @@ class Page(AbstractPage, index.Indexed, ClusterableModel, metaclass=PageBase):
         this page can be displayed for preview/moderation purposes. Ordinarily a page
         will only have one display mode, but subclasses of Page can override this -
         for example, a page containing a form might have a default view of the form,
-        and a post-submission 'thankyou' page
+        and a post-submission 'thank you' page
         """
         return Page.DEFAULT_PREVIEW_MODES