updates

stacyspiva · stacyspiva · commit 997191ef662e · 2018-11-13T14:14:10.000-08:00
diff --git a/docs/hackers/retesting.md b/docs/hackers/retesting.md
@@ -27,7 +27,7 @@ To participate in the retest:
    * Are you able to reproduce the vulnerability?
    * Are you able to identify a bypass to the fix?
 
-![retesting-3](./images/retesting-3c.png)
+![retesting questionnaire](./images/retesting-3c.png)
 
 6. Submit a new report if you found a new vulnerability by clicking on the <b>submit a new report</b> link, and enter the report ID number in the <b>Report ID</b> field.
 
diff --git a/docs/programs/retesting.md b/docs/programs/retesting.md
@@ -42,15 +42,15 @@ The hacker will be asked to answer the following questions:
 * Are you able to reproduce the vulnerability?
 * Are you able to identify a bypass to the fix?
 
-![retest questionnaire](./images/retesting-5b.png)
+![retest questionnaire](./images/retesting-5c.png)
 
 If they were able to identify a bypass, they can can submit a new vulnerability report and enter the report ID in the questionnaire.
 
 ![submitting a new report through retest](./images/retesting-6b.png)
 
 Hackers are also asked to provide a short summary of how they retested the vulnerability, and are also able to upload any attachments of their validations.
 
-![summary and screenshots](./images/retesting-6c.png)
+![summary and screenshots](./images/retesting-6d.png)
 
 Upon submission of the questionnaire, you’ll be notified that a hacker has completed a retest of your report within the report timeline and also through email.
 
