Update Readme.md (#874)

- remove reference to legacy nsp (Node Security Project) which was acquired by npm inc. (which was then acquired by GitHub)
- remove "ecosystem" prefix for the WG as this has been promoted & is canonically known as Node.js's "Security WG"

Co-authored-by: Ulises Gascón <UlisesGascon@users.noreply.github.com>

README.md

@@ -3,7 +3,8 @@
 [![Security WG Twitter Hashtag](https://img.shields.io/badge/Twitter-%23SecurityWG-blue.svg)](https://twitter.com/search?q=SecurityWG)
 [![OpenJS Slack Invite](https://img.shields.io/badge/join%20slack%20on-nodejs--security--wg-green.svg)](https://slack-invite.openjsf.org/)
 [![OpenSSF scorecard](https://api.securityscorecards.dev/projects/github.com/nodejs/security-wg/badge)](https://api.securityscorecards.dev/projects/github.com/nodejs/security-wg)
-# Ecosystem Security Working Group
+
+# Security Working Group
 
 Table of Contents
 
@@ -24,11 +25,9 @@ Table of Contents
 
 ## [Charter](https://github.com/nodejs/TSC/blob/master/WORKING_GROUPS.md#security)
 
-The Ecosystem Security Working Group works to improve the security of the Node.js Ecosystem.
+The Security Working Group works to improve the security of Node.js & its Ecosystem.
 
 Responsibilities include:
-* Work with the Node Security Platform to bring community vulnerability data into
-  the foundation as a shared asset.
 * Ensure the vulnerability data is updated in an efficient and timely manner. For example, ensuring there
   are well-documented processes for reporting vulnerabilities in community
   modules.