doc: Github -> GitHub

README.md

@@ -139,7 +139,7 @@ various sub-teams. For more information, see [GOVERNANCE.md](./GOVERNANCE.md).
 
 ### Core Team
 
-| | Github | Name | Email | Pronouns |
+| | GitHub | Name | Email | Pronouns |
 | ---| --- | --- | --- | --- |
 | ![addaleax](https://avatars2.githubusercontent.com/u/899444?v=4&s=64) | [addaleax](https://github.com/addaleax) | **Anna Henningsen** | anna@addaleax.net | she/her |
 | ![aqrln](https://avatars0.githubusercontent.com/u/4923335?v=4&s=64) | [aqrln](https://github.com/aqrln) | **Alexey Orlenko** | eaglexrlnk@gmail.com | he/him |
@@ -151,7 +151,7 @@ various sub-teams. For more information, see [GOVERNANCE.md](./GOVERNANCE.md).
 
 ### Moderation Team
 
-| | Github | Name | Email | Pronouns |
+| | GitHub | Name | Email | Pronouns |
 | ---| --- | --- | --- | --- |
 | ![AgentAntelope](https://avatars1.githubusercontent.com/u/1962412?v=4&s=64) | [AgentAntelope](https://github.com/AgentAntelope) | **Fell Sunderland** | agentantelope+github@gmail.com | he/him |
 | ![janl](https://avatars1.githubusercontent.com/u/11321?v=4&s=64) | [janl](https://github.com/janl) | **Jan Lehnardt** | jan@apache.org | he/him |

RFC_PROCESS.md

@@ -45,7 +45,7 @@ externally should be recorded in the RFC itself, for record keeping.
 ## How do RFCs get ratified?
 
 RFCs have a minimum 24 hour waiting period before being accepted or rejected.
-Once an RFC has been reviewed on Github and at least one member from each
+Once an RFC has been reviewed on GitHub and at least one member from each
 relevant team has signed off on the changes, the PR will be accepted. Depending
 on the change, having a parallel PR may be requested by reviewers.
 

deps/node-inspect/CONTRIBUTING.md

@@ -48,7 +48,7 @@ By making a contribution to this project, I certify that:
 ### Reporting Issues
 
 If you find any mistakes in the docs or a bug in the code,
-please [open an issue in Github](https://github.com/nodejs/node-inspect/issues/new) so we can look into it.
+please [open an issue in GitHub](https://github.com/nodejs/node-inspect/issues/new) so we can look into it.
 You can also [create a PR](#contributing-code) fixing it yourself of course.
 
 If you report a bug, please follow these guidelines:
@@ -63,9 +63,9 @@ If you report a bug, please follow these guidelines:
 
 ### Improving Documentation
 
-For small documentation changes, you can use [Github's editing feature](https://help.github.com/articles/editing-files-in-another-user-s-repository/).
+For small documentation changes, you can use [GitHub's editing feature](https://help.github.com/articles/editing-files-in-another-user-s-repository/).
 The only thing to keep in mind is to prefix the commit message with "docs: ".
-The default commit message generated by Github will lead to a failing CI build.
+The default commit message generated by GitHub will lead to a failing CI build.
 
 For larger updates to the documentation
 it might be better to follow the [instructions for contributing code below](#contributing-code).
@@ -92,7 +92,7 @@ The general steps for creating a pull request are:
    This is expected until you commit your changes.
 1. Once you're done, `git add .` and `git commit`.
    Please follow the [commit message conventions](#commits--commit-messages) described below.
-1. Push your branch to Github & create a PR.
+1. Push your branch to GitHub & create a PR.
 
 #### Code Style
 

deps/npm/TROUBLESHOOTING.md

@@ -50,7 +50,7 @@ We have a [detailed guide](https://github.com/npm/npm/wiki/Troubleshooting#upgra
 
 npm might not be able to connect to the registry for various reasons. Perhaps your machine is behind a firewall that needs to be opened, or you require a corporate proxy to access the npm registry. This issue can manifest in a wide number of different ways. Usually, strange network errors are an instance of this specific problem.
 
-Sometimes, users may have install failures due to Git/Github access issues. Git/GitHub access is separate from npm registry access. For users in some locations (India in particular), problems installing packages may be due to connectivity problems reaching GitHub and not the npm registry.
+Sometimes, users may have install failures due to Git/GitHub access issues. Git/GitHub access is separate from npm registry access. For users in some locations (India in particular), problems installing packages may be due to connectivity problems reaching GitHub and not the npm registry.
 
 If you believe your network is configured and working correctly, and you're still having problems installing, please let the [registry team](https://github.com/npm/registry/issues) know you're having trouble.
 

deps/npm/changelogs/CHANGELOG-2.md

@@ -660,7 +660,7 @@ deps, as any good LTS release train should be. 🙆
   ([@reconbot](https://github.com/reconbot))
 * [`3cfe99e`](https://github.com/npm/npm/commit/3cfe99e3a757c5d8cbb1c2789410e9802563abac)
   [#12093](https://github.com/npm/npm/pull/12093)
-  Update `bugs` url in `package.json` to use the `https` URL for Github.
+  Update `bugs` url in `package.json` to use the `https` URL for GitHub.
   ([@watilde](https://github.com/watilde))
 * [`ecf865f`](https://github.com/npm/npm/commit/ecf865f4eed1419c75442e0d52bc34ba1647de15)
   [#12075](https://github.com/npm/npm/pull/12075)
@@ -3655,7 +3655,7 @@ the code that handles Git dependencies.
 
 * [`b747593`](https://github.com/npm/npm/commit/b7475936f473f029e6a027ba1b16277523747d0b)
   [#7630](https://github.com/npm/npm/issues/7630) Don't automatically log all
-  git failures as errors. `maybeGithub` needs to be able to fail without
+  git failures as errors. `maybeGitHub` needs to be able to fail without
   logging to support its fallback logic.
   ([@othiym23](https://github.com/othiym23))
 * [`cd67a0d`](https://github.com/npm/npm/commit/cd67a0db07891d20871822696c26692c8a84866a)

deps/npm/changelogs/CHANGELOG-3.md

@@ -1903,7 +1903,7 @@ like documentation are a huge help. And remember -- you get socks for it, too!
   ([@watilde](https://github.com/watilde))
 * [`60051c2`](https://github.com/npm/npm/commit/60051c25e2ab80c667137dfcd04b242eea25980e)
   [#12093](https://github.com/npm/npm/pull/12093)
-  Update `bugs` url in `package.json` to use the `https` URL for Github.
+  Update `bugs` url in `package.json` to use the `https` URL for GitHub.
   ([@watilde](https://github.com/watilde))
 * [`af30c37`](https://github.com/npm/npm/commit/af30c374ef22ed1a1c71b14fced7c4b8350e4e82)
   [#12075](https://github.com/npm/npm/pull/12075)

deps/npm/man/man1/npx.1

@@ -151,7 +151,7 @@ Huge thanks to Kwyn Meagher \fIhttps://blog\.kwyn\.io\fR for generously donating
 Written by Kat Marchan \fIhttps://github\.com/zkat\fR\|\.
 .SH REPORTING BUGS
 .P
-Please file any relevant issues on Github\. \fIhttps://github\.com/zkat/npx\fR
+Please file any relevant issues on GitHub\. \fIhttps://github\.com/zkat/npx\fR
 .SH LICENSE
 .P
 This work is released by its authors into the public domain under CC0\-1\.0\. See \fBLICENSE\.md\fP for details\.

doc/changelogs/CHANGELOG_IOJS.md

@@ -1511,7 +1511,7 @@ will be removed at a later point. (Roman Reiss) [#1363](https://github.com/nodej
   * ARMv6: [#1376](https://github.com/nodejs/node/issues/1376) reported a problem with `Math.exp()` on ARMv6 (incl Raspberry Pi). The culprit is erroneous codegen for ARMv6 when using the "fast math" feature of V8. `--nofast_math` has been turned on for all ARMv6 variants by default to avoid this, fast math can be turned back on with `--fast_math`. (Ben Noordhuis) [#1398](https://github.com/nodejs/node/pull/1398).
   * Tests: timeouts have been tuned specifically for slower platforms, detected as ARMv6 and ARMv7. (Roman Reiss) [#1366](https://github.com/nodejs/node/pull/1366).
 * **npm**: Upgrade npm to 2.7.6. See the [release notes](https://github.com/npm/npm/releases/tag/v2.7.6) for details. Summary:
-  * [`b747593`](https://github.com/npm/npm/commit/b7475936f473f029e6a027ba1b16277523747d0b)[#7630](https://github.com/npm/npm/issues/7630) Don't automatically log all git failures as errors. `maybeGithub` needs to be able to fail without logging to support its fallback logic. ([@othiym23](https://github.com/othiym23))
+  * [`b747593`](https://github.com/npm/npm/commit/b7475936f473f029e6a027ba1b16277523747d0b)[#7630](https://github.com/npm/npm/issues/7630) Don't automatically log all git failures as errors. `maybeGitHub` needs to be able to fail without logging to support its fallback logic. ([@othiym23](https://github.com/othiym23))
   * [`78005eb`](https://github.com/npm/npm/commit/78005ebb6f4103c20f077669c3929b7ea46a4c0d)[#7743](https://github.com/npm/npm/issues/7743) Always quote arguments passed to `npm run-script`. This allows build systems and the like to safely escape glob patterns passed as arguments to `run-scripts` with `npm run-script <script> -- <arguments>`. This is a tricky change to test, and may be reverted or moved to `npm@3` if it turns out it breaks things for users. ([@mantoni](https://github.com/mantoni))
   * [`da015ee`](https://github.com/npm/npm/commit/da015eee45f6daf384598151d06a9b57ffce136e)[#7074](https://github.com/npm/npm/issues/7074) `read-package-json@1.3.3`: `read-package-json` no longer caches `package.json` files, which trades a very small performance loss for the elimination of a large class of really annoying race conditions. See [#7074](https://github.com/npm/npm/issues/7074) for the grisly details. ([@othiym23](https://github.com/othiym23))
 

doc/onboarding.md

@@ -107,7 +107,7 @@ onboarding session.
         (especially if it just has nits left).
   * Approving a change
     * Collaborators indicate that they have reviewed and approve of the
-        the changes in a pull request using Github’s approval interface
+        the changes in a pull request using GitHub’s approval interface
     * Some people like to comment `LGTM` (“Looks Good To Me”)
     * You have the authority to approve any other collaborator’s work.
     * You cannot approve your own pull requests.

rfcs/moderation-log.md

@@ -49,11 +49,11 @@ The log will include the following columns:
 * **Date** - date of the *enforcement action* (not the event itself)
 * **Action Taken** - official action taken by the moderation team, in accordance
   with the moderation process.
-* **Venue** - Where the event that triggered moderation happened: Github,
+* **Venue** - Where the event that triggered moderation happened: GitHub,
   Discord, Conference, etc.
 * **Moderator(s)** - Moderation Team member or members who took the action.
 * **URL** - If the event happened on a URL-linkable **PUBLIC** location (such as
-  Github), the URL of the issue or issue comment in question.
+  GitHub), the URL of the issue or issue comment in question.
 * **Details** - Freeform description of the event, with specific parties
   omitted. This should be as dry and neutral as possible. This should use
   placeholders instead of names when referring to any involved parties except