doc: remove unnecessary contributing.md section

CONTRIBUTING.md

@@ -15,7 +15,6 @@ See [details on our policy on Code of Conduct](./doc/guides/contributing/code-of
 
 ## [Issues](./doc/guides/contributing/issues.md)
 
-* [How to Contribute in Issues](./doc/guides/contributing/issues.md#how-to-contribute-in-issues)
 * [Asking for General Help](./doc/guides/contributing/issues.md#asking-for-general-help)
 * [Discussing non-technical topics](./doc/guides/contributing/issues.md#discussing-non-technical-topics)
 * [Submitting a Bug Report](./doc/guides/contributing/issues.md#submitting-a-bug-report)

doc/guides/contributing/issues.md

@@ -1,28 +1,11 @@
 # Issues
 
-* [How to Contribute in Issues](#how-to-contribute-in-issues)
 * [Asking for General Help](#asking-for-general-help)
 * [Discussing non-technical topics](#discussing-non-technical-topics)
 * [Submitting a Bug Report](#submitting-a-bug-report)
 * [Triaging a Bug Report](#triaging-a-bug-report)
 * [Resolving a Bug Report](#resolving-a-bug-report)
 
-## How to Contribute in Issues
-
-For any issue, there are fundamentally three ways an individual can
-contribute:
-
-1. By opening the issue for discussion: For instance, if you believe that you
-   have uncovered a bug in Node.js, creating a new issue in the `nodejs/node`
-   issue tracker is the way to report it.
-2. By helping to triage the issue: This can be done either by providing
-   supporting details (a test case that demonstrates a bug), or providing
-   suggestions on how to address the issue.
-3. By helping to resolve the issue: Typically this is done either in the form
-   of demonstrating that the issue reported is not a problem after all, or more
-   often, by opening a Pull Request that changes some bit of something in
-   `nodejs/node` in a concrete and reviewable manner.
-
 ## Asking for General Help
 
 Because the level of activity in the `nodejs/node` repository is so high,