Update NPM_Security_Cheat_Sheet.md

[wittjoe1]

Responsibly disclosure security vulnerabilities:

security vulnerabilities are a potentially serious threat for users who cannot protect themselves

Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.

:triangular_flag_on_post: If your PR is related to grammar/typo mistakes, please double-check the file for other mistakes in order to fix all the issues in the current cheat sheet.

Please make sure that for your contribution:

• [ ] In case of a new Cheat Sheet, you have used the Cheat Sheet template.
• [ ] All the markdown files do not raise any validation policy violation, see the policy.
• [ ] All the markdown files follow these format rules.
• [ ] All your assets are stored in the assets folder.
• [ ] All the images used are in the PNG format.
• [ ] Any references to websites have been formatted as [TEXT](URL)
• [ ] You verified/tested the effectiveness of your contribution (e.g., the defensive code proposed is really an effective remediation? Please verify it works!).
• [ ] The CI build of your PR pass, see the build status here.

If your PR is related to an issue, please finish your PR text with the following line:

none

Thank you again for your contribution :smiley:

[szh]

@jmanico can you please explain why you chose to merge this without two reviewers?

[jmanico]

It was just one line of text modification that was very minor. I’m happy to hold off on even these small changes in the future though!

[szh]

@jmanico I understand it's minor, but I had an unresolved comment on it already. I would appreciate if you could at least address any questions from other reviewers before merging. The proposed change also contains a spelling issue (publicised vs publicized - we usually standardize on US) but I was hoping to address the question of need before going into making spelling nits.

[jmanico]

Gotchya. I’ll hold back on merging until we get the needed reviews moving forward.

[szh]

Thanks @jmanico, I appreciate it 👍