From 7e1b178fb637abc68b1d4da1363a19db7ad02d6c Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 31 Oct 2018 21:57:58 -0700 Subject: doc: streamline CONTRIBUTING.md PR-URL: https://github.com/nodejs/node/pull/24010 Reviewed-By: James M Snell Reviewed-By: Daniel Bevenius --- doc/guides/contributing/pull-requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/guides/contributing') diff --git a/doc/guides/contributing/pull-requests.md b/doc/guides/contributing/pull-requests.md index 15c31cec71..2c0d8d6ccb 100644 --- a/doc/guides/contributing/pull-requests.md +++ b/doc/guides/contributing/pull-requests.md @@ -29,7 +29,7 @@ so that you can make the actual changes. This is where we will start. * [Accept that there are different opinions about what belongs in Node.js](#accept-that-there-are-different-opinions-about-what-belongs-in-nodejs) * [Performance is not everything](#performance-is-not-everything) * [Continuous Integration Testing](#continuous-integration-testing) -* [Additional Notes](#additional-notes) +* [Notes](#notes) * [Commit Squashing](#commit-squashing) * [Getting Approvals for your Pull Request](#getting-approvals-for-your-pull-request) * [CI Testing](#ci-testing) @@ -531,7 +531,7 @@ specific platforms or for so-called "flaky" tests to fail ("be red"). It is vital to visually inspect the results of all failed ("red") tests to determine whether the failure was caused by the changes in the Pull Request. -## Additional Notes +## Notes ### Commit Squashing -- cgit v1.2.3