doc: convert bare email addresses to mailto links

reflowed for line length after increased url size PR-URL: #32676 Reviewed-By: Rich Trott <[email protected]>
nodejs · Apr 28, 2020 · a5bed1e · a5bed1e
1 parent f7c7713
commit a5bed1e
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/doc/guides/cve-management-process.md b/doc/guides/cve-management-process.md
@@ -18,17 +18,17 @@ of contact points.  Email aliases have been setup for these as follows:
 
 * **Public contact points**. Email address to which people will be directed
   by Mitre when they are asked for a way to contact the Node.js team about
-  CVE-related issues. **[email protected]**
+  CVE-related issues. **[[email protected]][]**
 
 * **Private contact points**. Administrative contacts that Mitre can reach out
    to directly in case there are issues that require immediate attention.
-   **[email protected]**
+   **[[email protected]][]**
 
 * **Email addresses to add to the CNA email discussion list**. This address has
    been added to a closed mailing list that is used for announcements,
    sharing documents, or discussion relevant to the CNA community.
    The list rarely has more than ten messages a week.
-   **[email protected]**
+   **[[email protected]][]**
 
 ## CNA management processes
 
@@ -72,7 +72,7 @@ of CVEs should then be requested using the steps listed above.
 
 ### External CVE request process
 
-When a request for a CVE is received via the [email protected]
+When a request for a CVE is received via the [[email protected]][]
 email alias the following process will be followed (likely updated
 after we get HackerOne up and running).
 
@@ -135,3 +135,7 @@ following steps are used to assign, announce and report a CVE.
 * Move the CVE from the Pending section to the Announced section along
   with a link to the Node.js blog post announcing that releases
   are available.
+
+[[email protected]]: mailto:[email protected]
+[[email protected]]: mailto:[email protected]
+[[email protected]]: mailto:[email protected]