diff --git a/src/site/markdown/data/mirrornvd.md b/src/site/markdown/data/mirrornvd.md
index b7cbfd2e4..3e70542ed 100644
--- a/src/site/markdown/data/mirrornvd.md
+++ b/src/site/markdown/data/mirrornvd.md
@@ -4,13 +4,20 @@ Several organizations have opted to mirror the NVD on an internal server
 and have the dependency-check clients simply pull the updates from the
 mirror. This setup is fairly simple:
 
-1) Setup a nightly job to pull down the latest NVD files files from NIST
- * See the [Nist-Data-Mirror](https://github.com/stevespringett/nist-data-mirror/)
-   project on github.
- * All of the NVD
-2) Configure the dependency-check clients to use the internal CVE urls. Note, all four URLs
+<ol>
+<li>Setup a nightly job to pull down the latest NVD files files from NIST
+ <ul>
+   <li>Note, all of the NVD files must be downloaded: both 1.2 and 2.0 schema for 2002 on.</li>
+   <li>See the <a href="https://github.com/stevespringett/nist-data-mirror/">Nist-Data-Mirror</a> project on github.</li>
+ </ul>
+</li>
+<li>Configure the dependency-check clients to use the internal CVE urls. Note, all four URLs
    must be specified (see the configuration for the specific dependency-check client used):
- * cveUrl12Modified
- * cveUrl20Modified
- * cveUrl12Base
- * cveUrl20Base
+   <ul>
+     <li>cveUrl12Modified</li>
+     <li>cveUrl20Modified</li>
+     <li>cveUrl12Base</li>
+     <li>cveUrl20Base</li>
+   </ul>
+</li>
+</ol>