From b05d5d8b269b3152b35f2a3c0e8678d4831c748b Mon Sep 17 00:00:00 2001 From: Luca Berton Date: Wed, 7 Nov 2018 15:20:13 +0100 Subject: [PATCH] Fix typos in docs (#1934) --- docs/faq.md | 4 ++-- docs/reference.md | 2 +- infra/README.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index badc61d6f..5798fc79f 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -28,7 +28,7 @@ We will reconsider the GitHub issue tracker once the ## Why do you require a Google account for authentication? -Our [ClusterFuzz](clusterfuzz.md) fuzzing infrastructure and [issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) require a Google account for authentication. Note that an alternate email address associated with a Google acount does not work due to appengine api limitations. +Our [ClusterFuzz](clusterfuzz.md) fuzzing infrastructure and [issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) require a Google account for authentication. Note that an alternate email address associated with a Google account does not work due to appengine api limitations. ## Why do you use Docker? @@ -78,7 +78,7 @@ Using that, you can debug the root cause and see which category the bug falls in - If this is a bug is due to an incorrect usage of the dependent project's API in your project, then you need to fix your usage to call the API correctly. - If this is a real bug in the dependent project, then you should CC the maintainers -of that project on the bug. Once cced, they will get automatic access to all the +of that project on the bug. Once CCed, they will get automatic access to all the information necessary to reproduce the issue. If this project is maintained in OSS-Fuzz, you can search for contacts in the respective project.yaml file. diff --git a/docs/reference.md b/docs/reference.md index 2e6ff20e8..9cac9d4dd 100644 --- a/docs/reference.md +++ b/docs/reference.md @@ -19,7 +19,7 @@ Supported sanitizers: | `profile` | Used for generating code coverage reports. See [Code Coverage doc](code_coverage.md). Compiler flag values for predefined configurations are specified in the [Dockerfile](../infra/base-images/base-builder/Dockerfile). -These flags can be overriden by specifying `$SANITIZER_FLAGS` directly. +These flags can be overridden by specifying `$SANITIZER_FLAGS` directly. You can choose which configurations to automatically run your fuzzers with in `project.yaml` file (e.g. [sqlite3](../projects/sqlite3/project.yaml)): diff --git a/infra/README.md b/infra/README.md index 4d881c36f..bee42ce87 100644 --- a/infra/README.md +++ b/infra/README.md @@ -5,7 +5,7 @@ Core infrastructure: * [`base-images`](base-images/) - docker images for building fuzz targets & corresponding jenkins pipeline. -Continuous Integration infrastracture: +Continuous Integration infrastructure: * [`libfuzzer-pipeline.groovy`](libfuzzer-pipeline.groovy/) - jenkins pipeline that runs for each OSS-Fuzz project.