clarification

jessiwright · jessiwright · commit a5e76f624f3e · 2023-09-07T13:57:35.000-04:00
request from Will, info provided by Chris Bechtum
diff --git a/docs/organizations/retesting.md b/docs/organizations/retesting.md
@@ -6,7 +6,7 @@ id: "organizations/retesting"
 
 As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Retesting is a good way to secure the protection of your asset’s data by asking hackers to verify whether a fix has been made. With retesting, you can elect to have hackers retest your vulnerabilities to verify the fixes.
 
-> **Note:** For response programs using HackerOne's triage services, the triage team will retest the vulnerabilities to verify the fixes instead of hackers.  
+> **Note:** For response programs using HackerOne's triage services, the triage team will retest the vulnerabilities to verify the fixes instead of hackers when a retest is requested. 
 
 ### How it Works  
 To have hackers retest a vulnerability:
