ManPython
diff --git a/‎docs/hackers/images/retesting-3c.png
183 KB b/‎docs/hackers/images/retesting-3c.png
183 KB
diff --git a/‎docs/hackers/images/retesting-5c.png
93.8 KB b/‎docs/hackers/images/retesting-5c.png
93.8 KB
diff --git a/‎docs/hackers/retesting.md
Lines changed: 2 additions & 2 deletions b/‎docs/hackers/retesting.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/programs/images/retesting-3.png
-118 KB b/‎docs/programs/images/retesting-3.png
-118 KB
diff --git a/‎docs/programs/images/retesting-5.png
-122 KB b/‎docs/programs/images/retesting-5.png
-122 KB
diff --git a/‎docs/programs/images/retesting-5c.png
183 KB b/‎docs/programs/images/retesting-5c.png
183 KB
diff --git a/‎docs/programs/images/retesting-6.png
-155 KB b/‎docs/programs/images/retesting-6.png
-155 KB
diff --git a/‎docs/programs/images/retesting-6d.png
93.8 KB b/‎docs/programs/images/retesting-6d.png
93.8 KB
@@ -27,15 +27,15 @@ 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-3b.png)
+![retesting-3](./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.
 
 ![retesting-4](./images/retesting-4b.png)
 
 7. Provide a short summary of how you retested the vulnerability and upload any attachments of your validations.
 
-![retesting summary and attachments example](./images/retesting-5b.png)
+![retesting summary and attachments example](./images/retesting-5c.png)
 
 8. Click <b>Submit</b>.
 9. Click <b>Yes!</b> to finalize your submission.