removed mention of $50 from retesting

stacyspiva · stacyspiva · commit 5f69509dd01b · 2020-09-24T15:26:43.000-07:00
diff --git a/docs/hackers/retesting.md b/docs/hackers/retesting.md
@@ -6,7 +6,7 @@ id: "hackers/retesting"
 
 As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Retesting enables programs to ask hackers to verify whether a vulnerability has been fixed in order to secure the protection of their data. If you submit a valid vulnerability report, programs can elect to invite you to retest the vulnerability to verify the fixes.
 
-Upon successful completion of a retest, you’ll receive $50 in bounty as well as +2 reputation.
+Upon successful completion of a retest, you’ll receive a bounty as well as +2 reputation.
 
 ### How it Works
 
@@ -32,9 +32,9 @@ The program can either approve or reject your results. If they choose to:
 
 Action | Scenario | Details
 ------ | -------- | -------
-**Approve and resolve** the retest | You say the vulnerability is fixed. | You’ll be awarded a $50 bounty. <br><br>The report will close and will be marked as *Resolved*.
+**Approve and resolve** the retest | You say the vulnerability is fixed. | You’ll be awarded a bounty. <br><br>The report will close and will be marked as *Resolved*.
 **Reject** the retest | You say the vulnerability is fixed. | The program will provide you with a summary explaining why they’ve rejected the retest. They can choose to request another retest for the vulnerability. <br><br>The status of the report will be changed to Triaged. the report will be changed to *Triaged*.
-**Approve** the retest | You say the vulnerability is not fixed. | You’ll be awarded a $50 bounty. <br><br>The report will move back to *Triaged* and will stay open for the program to implement a fix.
+**Approve** the retest | You say the vulnerability is not fixed. | You’ll be awarded a bounty. <br><br>The report will move back to *Triaged* and will stay open for the program to implement a fix.
 **Reject** the retest | You say the vulnerability is not fixed. | The program will provide you with a summary explaining why they’ve rejected the retest. The program can choose to request another retest for the report. <br><br>The status of the report will be changed to *Triaged*.
 
 ### Claiming Retest Opportunities
diff --git a/docs/programs/retesting.md b/docs/programs/retesting.md
@@ -35,7 +35,7 @@ If you choose to:
 
 Action | Scenario | Details
 ------ | -------- | --------
-**Approve and resolve** the retest | The hacker says the vulnerability is fixed. | The report will close and will be marked as *Resolved*. The hacker will also be awarded a $50 bounty.
+**Approve and resolve** the retest | The hacker says the vulnerability is fixed. | The report will close and will be marked as *Resolved*. The hacker will also be awarded a bounty.
 **Reject** the retest | The hacker says the vulnerability is fixed. | You’ll need to provide a summary to the hacker explaining why you’ve rejected the retest. You can choose to request another retest for the report, by going back to step 1. <br><br>The status of the report will be changed to *Triaged*.
 **Approve** the retest | The hacker says the vulnerability is not fixed. | The report will move back to *Triaged* and will stay open for the team to implement a fix. The hacker will be awarded a bounty.
 **Reject** the retest | The hacker says the vulnerability is not fixed. | You’ll need to provide a summary to the hacker explaining why you’ve rejected the retest. You can choose to request another retest for the report, by going back to step 1. <br><br>The status of the report will be changed to *Triaged*.
