aboutsummaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorGravatar Luca Berton <luca@lucaberton.it>2018-11-07 15:20:13 +0100
committerGravatar jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>2018-11-07 06:20:13 -0800
commitb05d5d8b269b3152b35f2a3c0e8678d4831c748b (patch)
treef80c28b8b8f9fda95666c3b0c698d783ddf5722a /docs
parent8bbf279cc3426b8f2a9ee1d2e338fae1952fdd4e (diff)
Fix typos in docs (#1934)
Diffstat (limited to 'docs')
-rw-r--r--docs/faq.md4
-rw-r--r--docs/reference.md2
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/faq.md b/docs/faq.md
index badc61d6..5798fc79 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 2e6ff20e..9cac9d4d 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)):