added link and fixed line

stacyspiva · stacyspiva · commit 26e8358fe536 · 2020-03-12T15:02:13.000-07:00
diff --git a/docs/changelog/2019/november.md b/docs/changelog/2019/november.md
@@ -23,3 +23,5 @@ We added an **Experience by vulnerability type** section to the **Overview** pag
 We modified the layout of the profile section of the Hacker Dashboard and also expanded it with metrics on resolved reports that enables hackers to understand the percentage of their report submissions that are resolved.
 
 ![profile layout on hacker dashboard](./images/nov_2019_hackerdashboardprofile.png)
+
+###
diff --git a/docs/changelog/2020/march.md b/docs/changelog/2020/march.md
@@ -5,7 +5,7 @@ date: "2020-03"
 ---
 
 ### Updates to CVE IDs
-We've made these improvements to CVE IDs to help users get their CVE IDs faster and to simplify the publication process:
+We've made these improvements to [CVE IDs](/programs/cve-requests.html) to help users get their CVE IDs faster and to simplify the publication process:
 * **Immediate CVE ID assignments:** Users will no longer have to wait in getting their CVE IDs as HackerOne will now immediately and automatically assign a CVE ID to a request created through HackerOne.
-* **"Auto-Submission":** We now offer the new *Auto-submission* option in the CVE request process that'll enable CVE requests to be submitted automatically for approval and publication when the attached HackerOne report is publicly disclosed. 
+* **"Auto-Submission":** We now offer the new *Auto-submission* option in the CVE request process that'll enable CVE requests to be submitted automatically for approval and publication when the attached HackerOne report is publicly disclosed.
 * **Publication Reminder Emails:** HackerOne will now send users weekly reminder emails of their CVE IDs that have yet to publish an advisory.
diff --git a/docs/programs/cve-requests.md b/docs/programs/cve-requests.md
@@ -6,7 +6,7 @@ id: "programs/cve-requests"
 
 The CVE, short for common vulnerabilities and exposures, is a directory of publicly disclosed cybersecurity vulnerabilities that you can freely search, use, and incorporate into products and services.  Each vulnerability is referenced by a CVE ID to easily identify them. You can request to have CVE IDs associated with your program’s vulnerabilities, through which a CVE Assignment Authority (CNA) will then assign you a valid CVE ID and help you disclose the vulnerability.
 
-As HackerOne is a CNA empowered to assign and work with customers in assisting them to disclose vulnerabilities, you can request to have CVE IDs associated with your program’s vulnerabilities through the HackerOne platform. Upon request, HackerOne will approve and assign a CVE ID for your vulnerability and then send the ID to [MITRE](https://cve.mitre.org/) to publish publicly. The entire process takes about 7 business days after request.
+As HackerOne is a CNA empowered to assign and work with customers in assisting them to disclose vulnerabilities, you can request to have CVE IDs associated with your program’s vulnerabilities through the HackerOne platform. HackerOne will automatically assign a CVE ID for your vulnerability and publish it to [MITRE](https://cve.mitre.org/) when you've publicly posted your security advisory. 
 
 ><i>Note: To opt-in to this feature, talk to your program manager or email support@hackerone.com</i>.
 
