[DATALAD RUNCMD] chore: run codespell throughout fixing a few new typos automagically

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^

Author: yarikoptic

.github/ISSUE_TEMPLATE/feature.md

@@ -1,6 +1,6 @@
 ---
 name: Feature/improvement proposal
-about: Propose a new feauture or improvement for Read the Docs
+about: Propose a new feature or improvement for Read the Docs
 ---
 
 ## What's the problem this feature will solve?

docs/dev/aws-temporary-credentials.rst

@@ -2,7 +2,7 @@ AWS temporary credentials
 =========================
 
 Builders run arbitrary commands provided by the user, while we run the commands in a sandboxed environment (docker),
-that shouln't be the only line of defense, as we still interact with the files generated by the user outside docker for some operations.
+that shouldn't be the only line of defense, as we still interact with the files generated by the user outside docker for some operations.
 
 This is why instead of using credentials that have access to all the resources in AWS,
 we are using credentials that are generated by the `AWS STS service <https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html>`__,

docs/dev/design/build-images.rst

@@ -39,7 +39,7 @@ on each image without asking the users to change the image selected in their con
 Then, when a completely different image appeared and after testing ``testing`` image enough,
 we discarded ``stable``, old ``latest`` became the new ``stable`` and old ``testing`` became the new ``latest``.
 This produced issues to people pinning their images to any of these names because after this change,
-*we changed all the images for all the users* and many build issues arrised!
+*we changed all the images for all the users* and many build issues arose!
 
 
 Goals

docs/dev/design/future-builder.rst

@@ -256,6 +256,6 @@ Final notes
   - the project/build/user to expose a ``metadata.yaml`` with the contract that Read the Docs expects.
   - none, some or all the integrations will be added to the HTML output (these have to be implemented at Read the Docs core)
 - We are not responsible for extra formats (e.g. PDF, ePub, etc) on other tools.
-- Focus on support Sphinx with nice integrations made in a tool-agnostic way that can be re-used.
+- Focus on support Sphinx with nice integrations made in a tool-agnostic way that can be reused.
 - Removing the manipulation of ``conf.py.tmpl`` does not require us to implement the same manipulation
   for projects using the new potential feature ``sphinx.yaml`` file.

docs/dev/design/new-search-api.rst

@@ -142,7 +142,7 @@ now be objects.
 We could just reuse the old response too,
 since the only breaking changes would be the attributes now being objects,
 and we aren't adding any new information to those objects (yet).
-But also, re-using the current serializers shouldn't be a problem either.
+But also, reusing the current serializers shouldn't be a problem either.
 
 .. code-block:: json
 

docs/dev/github-app.rst

@@ -4,7 +4,7 @@ GitHub App
 Our GitHub App integration consists of a GitHub App (one for each platform, readthedocs.org and readthedocs.com),
 which can be installed on a user's account or organization.
 
-After installing the GitHub App, users can grant acccess to all repositories or select specific repositories,
+After installing the GitHub App, users can grant access to all repositories or select specific repositories,
 this allows Read the Docs to access the repositories and perform actions on them, such as reporting build statuses,
 and subscribe to events like push and pull request events.
 
@@ -42,5 +42,5 @@ Security
 - Since we make use of the installation to perform actions on the repositories instead of the user's OAuth2 token,
   we make sure that only users with admin permissions on the repository can link the repository to a Read the Docs project.
 - Once we lose access to a repository (e.g. the installation is uninstalled or revoked, or the project was deselected from the installation),
-  we remove the remote repository from the database, as we don't want to keep the relation bettween the project and the repository.
+  we remove the remote repository from the database, as we don't want to keep the relation between the project and the repository.
   This is to prevent connecting the repository to the project again without the user's consent if they grant access to the repository again.

docs/user/guides/creating-project-private-repository.rst

@@ -147,7 +147,7 @@ Configuring repository webhooks
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Your repository will also need to be configured to push updates via webhooks to Read the Docs on repository events.
-Webhook updates are used to automatically trigger new builds for your project and syncronize your repository's branches and tags.
+Webhook updates are used to automatically trigger new builds for your project and synchronize your repository's branches and tags.
 
 This step is the same for public repositories,
 follow the directions for :doc:`manually configuring a Git repository integration </guides/setup/git-repo-manual>`.

docs/user/img/screenshots/business.yml

@@ -12,7 +12,7 @@
   output: business-project-manual-team-select.png
 
 # Project manual creation form, have to submit with a team first. The JS looks
-# funny becuase Playwright needs to wait for the page to load before submitting.
+# funny because Playwright needs to wait for the page to load before submitting.
 - url: https://app.readthedocs.com/dashboard/import/manual/
   javascript: |-
     const _submit = () => {

readthedocs/api/v2/views/integrations.py

@@ -313,7 +313,7 @@ def get_closed_external_version_response(self, project):
 
     def update_default_branch(self, default_branch):
         """
-        Update the `Version.identifer` for `latest` with the VCS's `default_branch`.
+        Update the `Version.identifier` for `latest` with the VCS's `default_branch`.
 
         The VCS's `default_branch` is the branch cloned when there is no specific branch specified
         (e.g. `git clone <URL>`).

readthedocs/api/v2/views/model_views.py

@@ -173,7 +173,7 @@ def get_queryset(self):
         If an API key is present, we filter by the project associated with the key.
         Otherwise, we filter using our API manager method.
 
-        With this we check if the user/api key is authorized to acccess the object.
+        With this we check if the user/api key is authorized to access the object.
         """
         api_key = getattr(self.request, "build_api_key", None)
         if api_key:
@@ -263,7 +263,7 @@ def get_serializer_class(self):
         """
         Return the proper serializer for UI and Admin.
 
-        This ViewSet has a sligtly different pattern since we want to
+        This ViewSet has a slightly different pattern since we want to
         pre-process the `command` field before returning it to the user, and we
         also want to have a specific serializer for admins.
         """
@@ -370,7 +370,7 @@ def retrieve(self, *args, **kwargs):
         methods=["post"],
     )
     def reset(self, request, **kwargs):
-        """Reset the build so it can be re-used when re-trying."""
+        """Reset the build so it can be reused when re-trying."""
         instance = self.get_object()
         instance.reset()
         return Response(status=status.HTTP_204_NO_CONTENT)