Fix typos and clarify grammar and word choice throughout the OSS-Fuzz docs. (#363)

1 files changed, 8 insertions, 8 deletions

diff --git a/README.md b/README.md
index fa3dea987..c1cbd0f1f 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # OSS-Fuzz - Continuous Fuzzing for Open Source Software
 
-> *Status*: Beta. We are now accepting applications from widely used open source projects.
+> *Status*: Beta. We are now accepting applications from widely-used open source projects.
 
 [FAQ](docs/faq.md)
 | [Ideal Fuzzing Integration](docs/ideal_integration.md)
@@ -32,7 +32,7 @@ At the first stage of the project we use
 [libFuzzer](http://llvm.org/docs/LibFuzzer.html) with
 [Sanitizers](https://github.com/google/sanitizers). More fuzzing engines will be added later.
 [ClusterFuzz](docs/clusterfuzz.md)
-provides distributed fuzzer execution environment and reporting.
+provides a distributed fuzzer execution environment and reporting.
 
 Currently OSS-Fuzz supports C and C++ code (other languages supported by [LLVM](http://llvm.org) may work too).
 
@@ -47,7 +47,7 @@ and [integrates](docs/ideal_integration.md) them with the project's build and te
 - When [ClusterFuzz](docs/clusterfuzz.md) finds a bug, an issue is automatically
   reported in the OSS-Fuzz [issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) 
   ([example](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9)).
-  ([Why different tracker?](docs/faq.md#why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects)).
+  ([Why use a different tracker?](docs/faq.md#why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects)).
   Project owners are CC-ed to the bug report.
 - The project developer fixes the bug upstream and credits OSS-Fuzz for the discovery (commit message should contain
   the string **'Credit to OSS-Fuzz'**).
@@ -72,7 +72,7 @@ To submit a new project:
     If this is not you or the email address differs from VCS, an informal e-mail verification will be required.
   * Note that `project_name` can only contain alphanumeric characters, underscores(_) or dashes(-).
 - Once accepted by an OSS-Fuzz project member, follow the [New Project Guide](docs/new_project_guide.md)
-  to write the code.
+  to configure your project.
 
 
 ## Bug Disclosure Guidelines
@@ -80,7 +80,7 @@ To submit a new project:
 Following [Google's standard disclosure policy](https://googleprojectzero.blogspot.com/2015/02/feedback-and-data-driven-updates-to.html)
 OSS-Fuzz will adhere to following disclosure principles:
   - **90-day deadline**. After notifying project authors, we will open reported
-    issues in 90 days, or 7 days after the fix is released.
+    issues to the public in 90 days, or 7 days after the fix is released.
   - **Weekends and holidays**. If a deadline is due to expire on a weekend,
     the deadline will be moved to the next normal work day.
   - **Grace period**. We have a 14-day grace period. If a 90-day deadline
@@ -97,9 +97,9 @@ OSS-Fuzz will adhere to following disclosure principles:
 * [Accessing corpora](docs/corpora.md) describes how to access the corpora we use for fuzzing.
 * [Fuzzer execution environment](docs/fuzzer_environment.md) documents the
   environment under which your fuzzers will be run.
-* [Projects](projects) lists OSS projects currently added to OSS-Fuzz.
+* [Projects](projects) lists OSS projects currently analyzed by OSS-Fuzz.
 * [Chrome's Efficient Fuzzer Guide](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/efficient_fuzzer.md) 
-  while contains some chrome-specifics, is an excellent documentation on making your fuzzer better.
+  while containing some Chrome-specific bits, is an excellent guide to making your fuzzer better.
 * Blog posts: 2016-12-01 ([1](https://opensource.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html),
 [2](https://testing.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html),
 [3](https://security.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html))
@@ -111,7 +111,7 @@ gives the latest build logs for each project.
 ## Trophies
 
 [This page](https://bugs.chromium.org/p/oss-fuzz/issues/list?can=1&q=status%3AFixed%2CVerified+Type%3ABug%2CBug-Security+-component%3AInfra+)
-gives a list of publically viewable fixed bugs found by OSS-Fuzz.
+gives a list of publicly-viewable fixed bugs found by OSS-Fuzz.
 
 ## References
 * [libFuzzer documentation](http://libfuzzer.info)