Vulnerability-Remediation.md

@@ -29,17 +29,15 @@ Note: The following steps are only required if a vulnerability can be remediated
 
        7.2.	Rescan impacted software and dependencies to ensure vulnerabilities are no longer detected
 
-       7.3.	Update Issue status to Resolved
+       7.3.	Update Issue status to Resolved. The following steps are to be used to close out vulnerabilities in the compliance report after they have been remediated:
 
-The following steps are to be used to close out vulnerabilities after they have been remediated:
-
-1. Access the OSDU Vulnerability Report [Vulnerability Report · Platform · GitLab (opengroup.org)](https://community.opengroup.org/groups/osdu/platform/-/security/vulnerabilities).
-2. Local the vulnerability assigned to you or your team. This can be done by using the dropdown filters and/or scrolling though listed vulnerabilities.
+Access the OSDU Vulnerability Report [Vulnerability Report · Platform · GitLab (opengroup.org)](https://community.opengroup.org/groups/osdu/platform/-/security/vulnerabilities).
+Local the vulnerability assigned to you or your team. This can be done by using the dropdown filters and/or scrolling though listed vulnerabilities.
 
    ![VulnerabilityListCapture](uploads/010126d7101a79157157f28ed2718837/VulnerabilityListCapture.JPG)
-3. Click on vulnerability.
-4. Select the Status dropdown list which can be found in the upper right corner of the screen.
-5. Select the appropriate status (Dismiss, Confirm or Resolve)
+Click on vulnerability.
+Select the Status dropdown list which can be found in the upper right corner of the screen.
+Select the appropriate status (Dismiss, Confirm or Resolve)
 
    ![VulnerabilityScreenCapture](uploads/82e8008fc3e9a8515cbfa6ac5801acd2/VulnerabilityScreenCapture.JPG)
-6. Click Change status button
\ No newline at end of file
+Click Change status button
\ No newline at end of file