Skip to content
This repository was archived by the owner on Feb 1, 2022. It is now read-only.

Commit 730691c

Browse files
authored
Merge pull request #17 from joshgav/governance-update
docs: minor edits to governance docs
2 parents a4b6551 + a70fe04 commit 730691c

File tree

2 files changed

+8
-11
lines changed

2 files changed

+8
-11
lines changed

CONTRIBUTING.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,18 @@
44

55
This document outlines some of the practices we care about.
66
If you have any questions or suggestions about the process,
7-
feel free to [open an issue](#reporting-issues)
8-
.
7+
feel free to [open an issue](#reporting-issues).
98

109
## Code of Conduct
1110

1211
The [Node.js Code of Conduct][] applies to this repo.
1312

1413
[Node.js Code of Conduct]: https://github.com/nodejs/node/blob/master/CODE_OF_CONDUCT.md
1514

16-
## Code Contributions
15+
## Governance
1716

18-
The nodereport project falls under the governance of the diagnostics
19-
working group which is documented in:
20-
https://github.com/nodejs/diagnostics/blob/master/GOVERNANCE.md.
17+
This project falls under the governance of the Node.js Diagnostics WG as
18+
described at <https://github.com/nodejs/diagnostics/blob/master/GOVERNANCE.md>.
2119

2220
## Developer's Certificate of Origin 1.1
2321

@@ -51,7 +49,7 @@ By making a contribution to this project, I certify that:
5149

5250
If you find any mistakes in the docs or a bug in the code,
5351
please [open an issue in Github](https://github.com/nodejs/node-inspect/issues/new) so we can look into it.
54-
You can also [create a PR](#contributing-code) fixing it yourself, or course.
52+
You can also [create a PR](#contributing-code) fixing it yourself of course.
5553

5654
If you report a bug, please follow these guidelines:
5755

@@ -67,7 +65,7 @@ If you report a bug, please follow these guidelines:
6765

6866
For small documentation changes, you can use [Github's editing feature](https://help.github.com/articles/editing-files-in-another-user-s-repository/).
6967
The only thing to keep in mind is to prefix the commit message with "docs: ".
70-
The detault commit message generated by Github will lead to a failing CI build.
68+
The default commit message generated by Github will lead to a failing CI build.
7169

7270
For larger updates to the documentation
7371
it might be better to follow the [instructions for contributing code below](#contributing-code).

GOVERNANCE.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
# node-inspect Project Governance
22

3-
The node-inspect project falls under the governance of the diagnostics
4-
working group which is documented in:
5-
https://github.com/nodejs/diagnostics/blob/master/GOVERNANCE.md.
3+
The node-inspect project is governed by the Node.js Diagnostics WG as described
4+
at <https://github.com/nodejs/diagnostics/blob/master/GOVERNANCE.md>.

0 commit comments

Comments
 (0)