Addressing more review comments

melissawm · melissawm · commit 1b7510d52959 · 2022-12-01T14:56:53.000-03:00
diff --git a/doc/devel/coding_guide.rst b/doc/devel/coding_guide.rst
@@ -13,7 +13,8 @@
 Pull request guidelines
 ***********************
 
-`Pull requests (PRs) on GitHub <https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests>`__
+`Pull requests (PRs) on GitHub
+<https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests>`__
 are the mechanism for contributing to Matplotlib's code and documentation.
 
 It is recommended to check that your contribution complies with the following
@@ -24,7 +25,8 @@ rules before submitting a pull request:
   in the pull request description to ensure that a link is created to the
   original issue (e.g. "Closes #8869" or "Fixes #8869"). This will ensure the
   original issue mentioned is automatically closed when your PR is merged. See
-  `the GitHub documentation <https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue>`__
+  `the GitHub documentation
+  <https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue>`__
   for more details.
 
 * Formatting should follow the recommendations of PEP8_, as enforced by
@@ -85,7 +87,7 @@ rules before submitting a pull request:
 .. note::
 
     The current state of the Matplotlib code base is not compliant with all
-    of those guidelines, but we expect that enforcing those constraints on all
+    of these guidelines, but we expect that enforcing these constraints on all
     new contributions will move the overall code base quality in the right
     direction.
 
diff --git a/doc/devel/development_setup.rst b/doc/devel/development_setup.rst
@@ -59,7 +59,7 @@ Change into this directory before continuing::
   For more information on ``git`` and ``GitHub``, check the following resources.
 
   * `Git documentation <https://git-scm.com/doc>`_
-  * `Git-Contributing to a Project <https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project>`_
+  * `GitHub-Contributing to a Project <https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project>`_
   * `Introduction to GitHub <https://lab.github.com/githubtraining/introduction-to-github>`_
   * :ref:`using-git`
   * :ref:`git-resources`
diff --git a/doc/devel/development_workflow.rst b/doc/devel/development_workflow.rst
@@ -21,7 +21,7 @@ why you did it, we recommend the following:
   ``bugfix-for-issue-14`` or ``refactor-database-code``.
 * If you get stuck, reach out on Gitter or
   `discourse <https://discourse.matplotlib.org>`__.
-* When your ready or need feedback on your code, open a pull request so that the
+* When you're ready or need feedback on your code, open a pull request so that the
   Matplotlib developers can give feedback and eventually include your suggested
   code into the ``main`` branch.
 
@@ -40,7 +40,7 @@ Update the ``main`` branch
 
 First make sure you have followed :ref:`installing_for_devs`.
 
-From time to time you should fetch the upstream changes from github::
+From time to time you should fetch the upstream changes from GitHub::
 
    git fetch upstream
 
