Skip to content

Commit 8a17b7b

Browse files
TrottMylesBorins
authored andcommitted
doc: use correct and consistent typography for products
Use `GitHub` rather than `Github` and `Node.js` rather than `Node.JS`. PR-URL: #17492 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Jon Moss <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
1 parent ff59d3a commit 8a17b7b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

COLLABORATOR_GUIDE.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ change. In the case of pull requests proposed by an existing
8989
Collaborator, an additional Collaborator is required for sign-off.
9090

9191
In some cases, it may be necessary to summon a qualified Collaborator
92-
or a Github team to a pull request for review by @-mention.
92+
or a GitHub team to a pull request for review by @-mention.
9393
[See "Who to CC in issues"](./doc/onboarding-extras.md#who-to-cc-in-issues)
9494

9595
If you are unsure about the modification and are not prepared to take
@@ -160,7 +160,7 @@ trivial changes that do not require being tested on all platforms.
160160
* [`citgm-smoker`](https://ci.nodejs.org/job/citgm-smoker/)
161161
uses [`CitGM`](https://github.com/nodejs/citgm) to allow you to run `npm install && npm test`
162162
on a large selection of common modules. This is useful to check whether a
163-
change will cause breakage in the ecosystem. To test Node.JS ABI changes
163+
change will cause breakage in the ecosystem. To test Node.js ABI changes
164164
you can run [`citgm-abi-smoker`](https://ci.nodejs.org/job/citgm-abi-smoker/).
165165

166166
* [`node-stress-single-test`](https://ci.nodejs.org/job/node-stress-single-test/)
@@ -408,7 +408,7 @@ Changes" section of the release notes.
408408

409409
Collaborators may opt to elevate pull requests or issues to the [TSC][] for
410410
discussion by assigning the `tsc-review` label or @-mentioning the
411-
`@nodejs/tsc` Github team. This should be done where a pull request:
411+
`@nodejs/tsc` GitHub team. This should be done where a pull request:
412412

413413
- is labeled `semver-major`, or
414414
- has a significant impact on the codebase, or

0 commit comments

Comments
 (0)