Skip to content

Commit 6d06eef

Browse files
committed
doc: use serial comma in pull request doc
1 parent 45d7ca9 commit 6d06eef

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/contributing/pull-requests.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Node.js has many channels on the
4646
[OpenJS Foundation Slack](https://slack-invite.openjsf.org/). Interesting
4747
channels are:
4848
[#nodejs](https://openjs-foundation.slack.com/archives/CK9Q4MB53) for general
49-
help, questions and discussions.
49+
help, questions, and discussions.
5050
[#nodejs-dev](https://openjs-foundation.slack.com/archives/C019Y2T6STH) for
5151
development of Node.js core specifically.
5252

@@ -190,7 +190,7 @@ A good commit message should describe what changed and why.
190190

191191
5. If your commit introduces a breaking change (`semver-major`), it should
192192
contain an explanation about the reason of the breaking change, which
193-
situation would trigger the breaking change and what is the exact change.
193+
situation would trigger the breaking change, and what is the exact change.
194194

195195
Sample complete commit message:
196196

@@ -393,7 +393,7 @@ Focus first on the most significant aspects of the change:
393393
When changes are necessary, _request_ them, do not _demand_ them, and do not
394394
assume that the submitter already knows how to add a test or run a benchmark.
395395

396-
Specific performance optimization techniques, coding styles and conventions
396+
Specific performance optimization techniques, coding styles, and conventions
397397
change over time. The first impression you give to a new contributor never does.
398398

399399
Nits (requests for small changes that are not essential) are fine, but try to

0 commit comments

Comments
 (0)