more fixes

stacyspiva · stacyspiva · commit af0c1cae06c8 · 2020-05-14T11:28:25.000-07:00
diff --git a/docs/hackers/retesting.md b/docs/hackers/retesting.md
@@ -8,7 +8,7 @@ As programs receive vulnerability reports and work on deploying fixes, they need
 
 Upon successful completion of a retest, you’ll receive $50 in bounty as well as +2 reputation.
 
-### How it works
+### How it Works
 
 If you’ve submitted a valid vulnerability for a report, the program can request to have you retest the vulnerability to make sure it’s been fixed.
 
diff --git a/docs/programs/retesting.md b/docs/programs/retesting.md
@@ -4,11 +4,11 @@ path: "/programs/retesting.html"
 id: "programs/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 vulnerability has been fixed. With retesting, you can elect to have hackers retest your vulnerabilities to verify the fixes. The hacker that participates in the retest will receive a $50 bounty upon completion.
+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. The hacker that participates in the retest will receive a $50 bounty upon completion.
 
 > Retesting is available as an add-on. To learn more about adding Retesting to your program, contact your account manager.
 
-### How It Works
+### How it Works
 To have hackers retest a vulnerability:
 1. Choose the report in your inbox that you want to assign a hacker to retest.
 2. Change the action picker to **Request retest**.
@@ -41,5 +41,5 @@ If the original hacker declines to take part in the retest and your program is:
 
 Program Type | Details
 ------------ | --------
-Private | Another hacker that's part of your program will have the opportunity to claim and perform the retest. 
+Private | Another hacker that's part of your program will have the opportunity to claim and perform the retest.
 Public | Any hacker with at least 1 *Resolved* or *Triaged* report will be able to claim the retest.
