nodejs
diff --git a/Collapse file
‎doc/guides/contributing/pull-requests.md‎
Copy file name to clipboardExpand all lines: doc/guides/contributing/pull-requests.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff b/Collapse file
‎doc/guides/contributing/pull-requests.md‎
Copy file name to clipboardExpand all lines: doc/guides/contributing/pull-requests.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
@@ -137,8 +137,8 @@ notes about [commit squashing](#commit-squashing)).
 A good commit message should describe what changed and why.
 
 1. The first line should:
-   - contain a short description of the change (preferably 50 characters or less,
-     and no more than 72 characters)
+   - contain a short description of the change (preferably 50 characters or
+     less, and no more than 72 characters)
    - be entirely in lowercase with the exception of proper nouns, acronyms, and
    the words that refer to code, like function/variable names
    - be prefixed with the name of the changed subsystem and start with an
@@ -456,7 +456,8 @@ Focus first on the most significant aspects of the change:
 1. Does this change make sense for Node.js?
 2. Does this change make Node.js better, even if only incrementally?
 3. Are there clear bugs or larger scale issues that need attending to?
-4. Is the commit message readable and correct? If it contains a breaking change is it clear enough?
+4. Is the commit message readable and correct? If it contains a breaking change
+   is it clear enough?
 
 When changes are necessary, *request* them, do not *demand* them, and do not
 assume that the submitter already knows how to add a test or run a benchmark.