Commit 692a735
doc: use sentence-case for headers in SECURITY.md
Our doc style guide calls for sentence-case in headers.
PR-URL: #34525
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Stewart X Addison <sxa@uk.ibm.com>1 parent 465968c commit 692a735
1 file changed
Lines changed: 6 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,6 +1,6 @@ | |||
| 1 | 1 | # Security | |
| 2 | 2 | ||
| 3 | - ## Reporting a Bug in Node.js | ||
| 3 | + ## Reporting a bug in Node.js | ||
| 4 | 4 | ||
| 5 | 5 | Report security bugs in Node.js via [HackerOne](https://hackerone.com/nodejs). | |
| 6 | 6 | ||
@@ -13,13 +13,13 @@ you informed of the progress being made towards a fix and full announcement, | |||
| 13 | 13 | and may ask for additional information or guidance surrounding the reported | |
| 14 | 14 | issue. | |
| 15 | 15 | ||
| 16 | - ### Node.js Bug Bounty Program | ||
| 16 | + ### Node.js bug bounty program | ||
| 17 | 17 | ||
| 18 | 18 | The Node.js project engages in an official bug bounty program for security | |
| 19 | 19 | researchers and responsible public disclosures. The program is managed through | |
| 20 | 20 | the HackerOne platform. See <https://hackerone.com/nodejs> for further details. | |
| 21 | 21 | ||
| 22 | - ## Reporting a Bug in a third party module | ||
| 22 | + ## Reporting a bug in a third party module | ||
| 23 | 23 | ||
| 24 | 24 | Security bugs in third party modules should be reported to their respective | |
| 25 | 25 | maintainers and should also be coordinated through the Node.js Ecosystem | |
@@ -31,7 +31,7 @@ Details regarding this process can be found in the | |||
| 31 | 31 | Thank you for improving the security of Node.js and its ecosystem. Your efforts | |
| 32 | 32 | and responsible disclosure are greatly appreciated and will be acknowledged. | |
| 33 | 33 | ||
| 34 | - ## Disclosure Policy | ||
| 34 | + ## Disclosure policy | ||
| 35 | 35 | ||
| 36 | 36 | Here is the security disclosure policy for Node.js | |
| 37 | 37 | ||
@@ -60,14 +60,14 @@ Here is the security disclosure policy for Node.js | |||
| 60 | 60 | the release process above to ensure that the disclosure is handled in a | |
| 61 | 61 | consistent manner. | |
| 62 | 62 | ||
| 63 | - ## Receiving Security Updates | ||
| 63 | + ## Receiving security updates | ||
| 64 | 64 | ||
| 65 | 65 | Security notifications will be distributed via the following methods. | |
| 66 | 66 | ||
| 67 | 67 | * <https://groups.google.com/group/nodejs-sec> | |
| 68 | 68 | * <https://nodejs.org/en/blog/> | |
| 69 | 69 | ||
| 70 | - ## Comments on this Policy | ||
| 70 | + ## Comments on this policy | ||
| 71 | 71 | ||
| 72 | 72 | If you have suggestions on how this process could be improved please submit a | |
| 73 | 73 | [pull request](https://github.com/nodejs/nodejs.org) or | |
0 commit comments