matplotlib · ksunden · Feb 2, 2023 · Feb 2, 2023
diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst
@@ -38,7 +38,7 @@ Contributor incubator
 The incubator is our non-public communication channel for new contributors. It
 is a private gitter room moderated by core Matplotlib developers where you can
 get guidance and support for your first few PRs. It's a place you can ask
-questions about anything: how to use git, github, how our PR review process
+questions about anything: how to use git, GitHub, how our PR review process
 works, technical questions about the code, what makes for good documentation
 or a blog post, how to get involved in community work, or get
 "pre-review" on your PR.
@@ -57,7 +57,7 @@ Among our attendees are fellow new contributors, as well as maintainers, and
 veteran contributors, who are keen to support onboarding of new folks and
 share their experience. You can find our community calendar link at the
 `Scientific Python website <https://scientific-python.org/calendars/>`_, and
-you can browse previous meeting notes on `github
+you can browse previous meeting notes on `GitHub
 <https://github.com/matplotlib/ProjectManagement/tree/master/
 new_contributor_meeting>`_.
 We recommend joining the meeting to clarify any doubts, or lingering

diff --git a/doc/devel/dependencies.rst b/doc/devel/dependencies.rst
@@ -215,10 +215,13 @@ Matplotlib requires a C++ compiler that supports C++11.
 
 - `gcc 4.8.1 <https://gcc.gnu.org/projects/cxx-status.html#cxx11>`_ or higher.  For gcc <6.5 you will
   need to set ``$CFLAGS=-std=c++11`` to enable C++11 support.
-- `clang 3.3 <https://clang.llvm.org/cxx_status.html>`_ or higher
+  `Installing GCC: Binaries <https://gcc.gnu.org/install/binaries.html>`_.
+- `clang 3.3 <https://clang.llvm.org/cxx_status.html>`_ or higher.
+  `LLVM Download Page <https://releases.llvm.org/download.html>`_.
 - `Visual Studio 2015
   <https://docs.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformance?view=msvc-140>`_
-  (aka VS 14.0) or higher
+  (aka VS 14.0) or higher. A free version of Build Tools for Visual Studio is available for
+  `download <https://visualstudio.microsoft.com/downloads/?q=build+tools>`_.
 
 
 .. _test-dependencies:
@@ -304,9 +307,10 @@ Additional external dependencies
 --------------------------------
 Required:
 
-* a minimal working LaTeX distribution
+* a minimal working LaTeX distribution, e.g., `TeX Live <https://www.tug.org/texlive/>`_ or
+  `MikTeX <https://miktex.org/>`_
 * `Graphviz <http://www.graphviz.org/download>`_
-* the following LaTeX packages (if your OS bundles TeXLive, the
+* the following LaTeX packages (if your OS bundles TeX Live, the
   "complete" version of the installer, e.g. "texlive-full" or "texlive-all",
   will often automatically include these packages):
 

diff --git a/doc/devel/development_workflow.rst b/doc/devel/development_workflow.rst
@@ -28,10 +28,10 @@ why you did it, we recommend the following:
 .. note::
 
    It may sound strange, but deleting your own ``main`` branch can help reduce
-   confusion about which branch you are on.  See `deleting main on github`_ for
+   confusion about which branch you are on.  See `deleting main on GitHub`_ for
    details.
 
-.. _deleting main on github: https://matthew-brett.github.io/pydagogue/gh_delete_master.html
+.. _deleting main on GitHub: https://matthew-brett.github.io/pydagogue/gh_delete_master.html
 
 .. _update-mirror-main:
 
@@ -134,7 +134,7 @@ In more detail
    description in the `tangled working copy problem`_. The
    `git commit <https://git-scm.com/docs/git-commit>`_ manual page might also be
    useful.
-#. To push the changes up to your forked repo on github, do a ``git
+#. To push the changes up to your forked repo on GitHub, do a ``git
    push``.
 
 .. _why the -a flag?: http://gitready.com/beginner/2009/01/18/the-staging-area.html

diff --git a/doc/devel/maintainer_workflow.rst b/doc/devel/maintainer_workflow.rst
@@ -50,7 +50,7 @@ If there are only a few commits, consider rebasing to upstream::
     git rebase upstream-rw/main
 
 Remember that, if you do a rebase, and push that, you'll have to close any
-github pull requests manually, because github will not be able to detect the
+GitHub pull requests manually, because GitHub will not be able to detect the
 changes have already been merged.
 
 A long series of commits
@@ -61,7 +61,7 @@ If there are a longer series of related commits, consider a merge instead::
     git fetch upstream-rw
     git merge --no-ff upstream-rw/main
 
-The merge will be detected by github, and should close any related pull requests
+The merge will be detected by GitHub, and should close any related pull requests
 automatically.
 
 Note the ``--no-ff`` above.  This forces git to make a merge commit, rather than

diff --git a/doc/devel/triage.rst b/doc/devel/triage.rst
@@ -87,7 +87,7 @@ Triaging operations for members of the core and triage teams
 In addition to the above, members of the core team and the triage team
 can do the following important tasks:
 
-- Update labels for issues and PRs: see the list of `available github
+- Update labels for issues and PRs: see the list of `available GitHub
   labels <https://github.com/matplotlib/matplotlib/labels>`_.
 
 - Triage issues: