Updating copy after recent product changes

bwillis · web-flow · commit db6b88a0c6cd · 2022-03-28T14:02:35.000-07:00
diff --git a/docs/programs/retesting.md b/docs/programs/retesting.md
@@ -19,7 +19,7 @@ To have hackers retest a vulnerability:
 
 The original hacker that submitted the vulnerability will be invited to take part in the retest.
 
-After accepting the retest, the hacker will have 24 hours to confirm if the vulnerability has been properly fixed. If the hacker doesn’t finish the retest within 24 hours, their retest opportunity will expire and a different hacker will be able to claim the retest.
+After accepting the retest, the hacker will have 3 days to confirm if the vulnerability has been properly fixed. If the hacker doesn’t finish the retest within the time period, the retest opportunity will expire and a different hacker will be able to claim the retest.
 
 The hacker will submit their findings in the **Retest findings** form at the bottom of the report. The form consists of these fields:
 * Are you able to reproduce the vulnerability report?
