@@ -326,7 +326,7 @@ Install git pre-commit hooks
 
 `prek <https://prek.j178.dev/>`_ hooks save time in the review process by
 identifying issues with the code before a pull request is formally opened. Most
-hooks can also aide in fixing the errors, and the checks should have
+hooks can also aid in fixing the errors, and the checks should have
 corresponding :ref:`development workflow <development-workflow>` and
 :ref:`pull request <pr-guidelines>` guidelines. Hooks are configured in
 `.pre-commit-config.yaml <https://github.com/matplotlib/matplotlib/blob/main/.pre-commit-config.yaml?>`_
 
@@ -318,7 +318,7 @@ before the section
    Summary for pull request authors
    ================================
 
-and then link to with ``:ref:`label-name```
+and then link to it with ``:ref:`label-name```
 
 .. code-block:: rst
 
@@ -396,7 +396,7 @@ commands::
 Include figures and files
 -------------------------
 
-Image files can directly included in pages with the ``image::`` directive.
+Image files can directly be included in pages with the ``image::`` directive.
 e.g., :file:`tutorials/intermediate/constrainedlayout_guide.py` displays
 a couple of static images::
 
 
@@ -66,7 +66,7 @@ Test and documentation dependencies
 As these packages are only needed for testing or building the docs and
 not needed by end-users, we can be more aggressive about dropping
 support for old versions.  However, we need to be careful to not
-over-run what down-stream packagers support (as most of the run the
+over-run what down-stream packagers support (as most of them run the
 tests and build the documentation as part of the packaging process).
 
 We will support at least minor versions of the development dependencies
 
@@ -360,7 +360,7 @@ Automated backports
 -------------------
 
 We use MeeseeksDev bot to automatically backport merges to the correct
-maintenance branch base on the milestone.  To work properly the
+maintenance branch based on the milestone.  To work properly the
 milestone must be set before merging.  If you have commit rights, the
 bot can also be manually triggered after a merge by leaving a message
 ``@meeseeksdev backport to BRANCH`` on the PR.  If there are conflicts
 
@@ -289,7 +289,7 @@ CI with GitHub Actions
 "in the cloud".
 
 GitHub Actions is configured to receive notifications of new commits to GitHub
-repos and to run builds or tests when it sees these new commits. It looks for a
+repos and to run builds or tests when it sees these new commits. It looks for 
 YAML files in ``.github/workflows`` to see how to test the project.
 
 GitHub Actions is already enabled for the `main Matplotlib GitHub repository
@@ -384,7 +384,7 @@ To do so, either download the matching source distribution
 ``matplotlib-X.Y.Z.tar.gz`` from `PyPI <https://pypi.org/project/matplotlib/>`_
 or alternatively, clone the git repository and ``git checkout vX.Y.Z``. Copy
 the folder :file:`lib/matplotlib/tests/baseline_images` to the folder
-:file:`matplotlib/tests` of your the matplotlib installation to test.
+:file:`matplotlib/tests` of the matplotlib installation to test.
 The correct target folder can be found using::
 
     python -c "import matplotlib.tests; print(matplotlib.tests.__file__.rsplit('/', 1)[0])"