GeezerVison is showing github.com — doc: fix typo in contributing guides · nodejs/node@ee79e53
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/releases.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -851,7 +851,7 @@ reflect the newly used value. Ensure that the release commit removes the |
851 | 851 | `-pre` suffix for the major version being prepared. |
852 | 852 |
|
853 | 853 | It is current TSC policy to bump major version when ABI changes. If you |
854 | | -see a need to bump `NODE_MODULE_VERSION` outside of a majore release then |
| 854 | +see a need to bump `NODE_MODULE_VERSION` outside of a major release then |
855 | 855 | you should consult the TSC. Commits may need to be reverted or a major |
856 | 856 | version bump may need to happen. |
857 | 857 |
|
|
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/static-analysis.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -11,6 +11,6 @@ Any collaborator can ask to be added to the Node.js coverity project |
11 | 11 | by opening an issue in the [build](https://github.com/nodejs/build) repository |
12 | 12 | titled `Please add me to coverity`. A member of the build WG with admin |
13 | 13 | access will verify that the requestor is an existing collaborator as listed in |
14 | | -the [colloborators section](https://github.com/nodejs/node#collaborators) |
| 14 | +the [collaborators section](https://github.com/nodejs/node#collaborators) |
15 | 15 | on the nodejs/node project repo. Once validated the requestor will added |
16 | 16 | to to the coverity project. |