Update HACKTOBERFEST2021.md (semgrep#1517)

Grayson H · web-flow · commit 6b2299563e25 · 2021-10-04T23:10:30.000Z
diff --git a/HACKTOBERFEST2021.md b/HACKTOBERFEST2021.md
@@ -59,4 +59,4 @@ To scan open source code, use whatever infrastructure you have at your disposal.
 
 ### What to do if you find a security vulnerability
 
-If you find a security vulnerability in an open source project, always follow a [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) policy. If the project as a method for reporting security vulnerabilities privately, use that to work with the maintainers to issue a fix. If a method for privately reporting doesn't exist, do your best to privately contact the maintainers. E.g., check the `git log` for emails. Make a pull request fixing the problem or file an issue on the repository as a last resort!
+If you find a security vulnerability in an open source project, always follow a [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) policy. If the project has a method for reporting security vulnerabilities privately, use that to work with the maintainers to issue a fix. If a method for privately reporting doesn't exist, do your best to privately contact the maintainers. E.g., check the `git log` for emails. Make a pull request fixing the problem or file an issue on the repository as a last resort!

Original file line number	Diff line number	Diff line change
`@@ -59,4 +59,4 @@ To scan open source code, use whatever infrastructure you have at your disposal.`
`59`	`59`
`60`	`60`	`### What to do if you find a security vulnerability`
`61`	`61`
`62`		-If you find a security vulnerability in an open source project, always follow a [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) policy. If the project as a method for reporting security vulnerabilities privately, use that to work with the maintainers to issue a fix. If a method for privately reporting doesn't exist, do your best to privately contact the maintainers. E.g., check the `git log` for emails. Make a pull request fixing the problem or file an issue on the repository as a last resort!
	`62`	+If you find a security vulnerability in an open source project, always follow a [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) policy. If the project has a method for reporting security vulnerabilities privately, use that to work with the maintainers to issue a fix. If a method for privately reporting doesn't exist, do your best to privately contact the maintainers. E.g., check the `git log` for emails. Make a pull request fixing the problem or file an issue on the repository as a last resort!