11# Security
22
3- ## Reporting a Bug in Node.js
3+ ## Reporting a bug in Node.js
44
55Report security bugs in Node.js via [ HackerOne] ( https://hackerone.com/nodejs ) .
66
@@ -13,13 +13,13 @@ you informed of the progress being made towards a fix and full announcement,
1313and may ask for additional information or guidance surrounding the reported
1414issue.
1515
16- ### Node.js Bug Bounty Program
16+ ### Node.js bug bounty program
1717
1818The Node.js project engages in an official bug bounty program for security
1919researchers and responsible public disclosures. The program is managed through
2020the HackerOne platform. See < https://hackerone.com/nodejs > for further details.
2121
22- ## Reporting a Bug in a third party module
22+ ## Reporting a bug in a third party module
2323
2424Security bugs in third party modules should be reported to their respective
2525maintainers and should also be coordinated through the Node.js Ecosystem
@@ -31,7 +31,7 @@ Details regarding this process can be found in the
3131Thank you for improving the security of Node.js and its ecosystem. Your efforts
3232and responsible disclosure are greatly appreciated and will be acknowledged.
3333
34- ## Disclosure Policy
34+ ## Disclosure policy
3535
3636Here is the security disclosure policy for Node.js
3737
@@ -60,14 +60,14 @@ Here is the security disclosure policy for Node.js
6060 the release process above to ensure that the disclosure is handled in a
6161 consistent manner.
6262
63- ## Receiving Security Updates
63+ ## Receiving security updates
6464
6565Security notifications will be distributed via the following methods.
6666
6767* < https://groups.google.com/group/nodejs-sec >
6868* < https://nodejs.org/en/blog/ >
6969
70- ## Comments on this Policy
70+ ## Comments on this policy
7171
7272If you have suggestions on how this process could be improved please submit a
7373[ pull request] ( https://github.com/nodejs/nodejs.org ) or
0 commit comments