Correct GitHub capitalization

aesara/tensor/slinalg.py

@@ -396,7 +396,7 @@ class EigvalshGrad(Op):
     # But this can only be done once scipy.linalg.eigh is available as an Op
     # (currently the Eigh uses numpy.linalg.eigh, which doesn't let you
     # pass the right-hand-side matrix for a generalized eigenproblem.) See the
-    # discussion on github at
+    # discussion on GitHub at
     # https://github.com/Theano/Theano/pull/1846#discussion-diff-12486764
 
     __props__ = ("lower",)

doc/dev_start_guide.rst

@@ -14,7 +14,7 @@ Contributing
 You want to contribute to Aesara? That is great! This page explain our
 workflow and some resource for doing so.
 
-Looking for an idea for a first contribution? Check the `github issues
+Looking for an idea for a first contribution? Check the `GitHub issues
 <https://github.com/pymc-devs/aesara/issues>`_.
 
 We recommend creating an issue to discuss proposed changes before making them.
@@ -418,7 +418,7 @@ Submit your changes to the central repository
 ---------------------------------------------
 
 Once your code is ready for others to review, you need to commit all the changes and then push your
-branch to your github fork first:
+branch to your GitHub fork first:
 
 .. code-block:: bash
 
@@ -428,7 +428,7 @@ branch to your github fork first:
 
     git push -u origin my_shiny_feature
 
-Then, go to your fork's github page on the github website, select your
+Then, go to your fork's GitHub page on the GitHub website, select your
 feature branch and hit the "Pull Request" button in the top right
 corner.  This will signal the maintainers that you wish to submit your
 changes for inclusion in ``origin/main``.

doc/index.rst

@@ -68,7 +68,7 @@ Roughly in order of what you'll want to check out:
 
 * Ask/view questions/answers at `StackOverflow`_
 
-* We use `Github tickets <http://github.com/pymc-devs/aesara/issues>`__ to keep track of issues.
+* We use `GitHub tickets <http://github.com/pymc-devs/aesara/issues>`__ to keep track of issues.
 
 .. toctree::
    :maxdepth: 1

versioneer.py

@@ -37,7 +37,7 @@ Source trees come from a variety of places:
 
 * a version-control system checkout (mostly used by developers)
 * a nightly tarball, produced by build automation
-* a snapshot tarball, produced by a web-based VCS browser, like github's
+* a snapshot tarball, produced by a web-based VCS browser, like GitHub's
   "tarball from tag" feature
 * a release tarball, produced by "setup.py sdist", distributed through PyPI
 
@@ -165,7 +165,7 @@ which may help identify what went wrong).
 ## Known Limitations
 
 Some situations are known to cause problems for Versioneer. This details the
-most significant ones. More can be found on Github
+most significant ones. More can be found on GitHub
 [issues page](https://github.com/warner/python-versioneer/issues).
 
 ### Subprojects
@@ -1423,7 +1423,7 @@ def get_versions(verbose=False):
     # extract version from first of: _version.py, VCS command (e.g. 'git
     # describe'), parentdir. This is meant to work for developers using a
     # source checkout, for users of a tarball created by 'setup.py sdist',
-    # and for users of a tarball/zipball created by 'git archive' or github's
+    # and for users of a tarball/zipball created by 'git archive' or GitHub's
     # download-from-tag feature or the equivalent in other VCSes.
 
     get_keywords_f = handlers.get("get_keywords")