8000 grammar fix · csit-github/docs.hackerone.com@b5715db · GitHub
[go: up one dir, main page]

Skip to content

Commit b5715db

Browse files
committed
grammar fix
1 parent 4aabdf6 commit b5715db

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/programs/public-vs-private.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ As your private program becomes more proficient in handling reports, you can cho
1515

1616
### Public Programs
1717

18-
When programs become public, they open themselves up to report submissions from the entire hacker community. This means that all hackers on HackerOne are given rights to hack your program. Moving into a public program prematurely can be an overwhelming experience given the large influx of new report submissions and new hackers participating. Report volumes can spike up to 5x-10x, which highlights the importance of ensuring that your security team is prepared before launching publicly.
18+
When programs become public, they open themselves up to report submissions from the entire hacker community. This means that all hackers on HackerOne are given rights to hack your program. Moving into a public program prematurely can be an overwhelming experience given the large influx of new report submissions and new hackers participating. Report volumes can spike up to 5x-10x, which highlights the importance of ensuring that your security team is prepared before launching publicly.
1919

20-
Taking your bug bounty program public is completely optional. If your goal is to open up your program to the public, then some recommended success criteria are:
20+
Taking your bug bounty program public is completely optional. If your goal is to open up your program to the public, then some recommended success criteria to meet first are:
2121
* You've invited more than 100 hackers
2222
* You've received 10 vulnerability reports
2323
* Your program meets HackerOne's response standards

0 commit comments

Comments
 (0)
0