1
1
# Issues
2
2
3
- * [ Asking for General Help ] ( #asking-for-general-help )
3
+ * [ Asking for general help ] ( #asking-for-general-help )
4
4
* [ Discussing non-technical topics] ( #discussing-non-technical-topics )
5
- * [ Submitting a Bug Report ] ( #submitting-a-bug-report )
6
- * [ Triaging a Bug Report ] ( #triaging-a-bug-report )
5
+ * [ Submitting a bug report ] ( #submitting-a-bug-report )
6
+ * [ Triaging a bug report ] ( #triaging-a-bug-report )
7
7
8
- ## Asking for General Help
8
+ ## Asking for general help
9
9
10
10
Because the level of activity in the ` nodejs/node ` repository is so high,
11
11
questions or requests for general help using Node.js should be directed at
@@ -16,7 +16,7 @@ the [Node.js help repository][].
16
16
Discussion of non-technical topics (such as intellectual property and trademark)
17
17
should be directed to the [ Technical Steering Committee (TSC) repository] [ ] .
18
18
19
- ## Submitting a Bug Report
19
+ ## Submitting a bug report
20
20
21
21
When opening a new issue in the ` nodejs/node ` issue tracker, users will be
22
22
presented with a choice of issue templates. If you believe that you have
@@ -37,7 +37,7 @@ Node.js changed that broke the module.
37
37
38
38
See [ How to create a Minimal, Complete, and Verifiable example] ( https://stackoverflow.com/help/mcve ) .
39
39
40
- ## Triaging a Bug Report
40
+ ## Triaging a bug report
41
41
42
42
Once an issue has been opened, it is common for there to be discussion
43
43
around it. Some contributors may have differing opinions about the issue,
0 commit comments