diff options
| -rw-r--r-- | docs/building_running_fuzzers.md | 2 | ||||
| -rw-r--r-- | docs/building_running_fuzzers_external.md | 2 | ||||
| -rw-r--r-- | docs/ideal_integration.md | 2 | ||||
| -rw-r--r-- | docs/new_target.md | 2 | ||||
| -rw-r--r-- | docs/reproducing.md | 2 |
5 files changed, 5 insertions, 5 deletions
diff --git a/docs/building_running_fuzzers.md b/docs/building_running_fuzzers.md index 83268736..a136c020 100644 --- a/docs/building_running_fuzzers.md +++ b/docs/building_running_fuzzers.md @@ -28,7 +28,7 @@ docker run -ti -v /tmp/out:/out ossfuzz/<b><i>$target_name</i></b> ## Running Fuzzers Fuzzers are statically linked executables and could be executed normally in Unbuntu-like environment. -When Ubuntu environment is not available (or a restricted environment is desirable), the fuzzer can easly be run inside docker +When Ubuntu environment is not available (or a restricted environment is desirable), the fuzzer can easily be run inside docker container: <pre> diff --git a/docs/building_running_fuzzers_external.md b/docs/building_running_fuzzers_external.md index 6752d5b0..5b0e95f7 100644 --- a/docs/building_running_fuzzers_external.md +++ b/docs/building_running_fuzzers_external.md @@ -48,7 +48,7 @@ INFO: Seed: 477892609 #4 NEW cov: 293 bits: 299 indir: 61 units: 4 exec/s: 0 L: 32 MS: 2 ChangeBit-EraseBytes- ``` -When Ubuntu environment is not aviable (or restricted environemnt is desirable), the fuzzer can easly be run inside docker +When Ubuntu environment is not aviable (or restricted environment is desirable), the fuzzer can easily be run inside docker container: <pre> diff --git a/docs/ideal_integration.md b/docs/ideal_integration.md index 80554b70..b01110f0 100644 --- a/docs/ideal_integration.md +++ b/docs/ideal_integration.md @@ -97,7 +97,7 @@ and the project maintainers are not interested in helping. In such cases we can host the fuzz targets, dictionaries, etc in this repository and mention them in the Dockerfile. Examples: [libxml2](../targets/libxml2), [c-ares](../targets/c-ares), [expat](../targets/expat). -This is far from ideal because the fuzz targets will not be continuosly tested +This is far from ideal because the fuzz targets will not be continuously tested and hence may quickly bitrot. If you are not a project maintainer we may not be able to CC you to security bugs found by OSS-Fuzz. diff --git a/docs/new_target.md b/docs/new_target.md index e8b0c7a2..cd3fc722 100644 --- a/docs/new_target.md +++ b/docs/new_target.md @@ -211,7 +211,7 @@ libfuzzerBuild { } ``` -Simply replace the the "git" entry with the correct git url for the target. +Simply replace the "git" entry with the correct git url for the target. *Note*: only git is supported right now. diff --git a/docs/reproducing.md b/docs/reproducing.md index 35fc8a55..79985cac 100644 --- a/docs/reproducing.md +++ b/docs/reproducing.md @@ -63,7 +63,7 @@ docker run --rm -v <b><i>$target_checkout_dir</i></b>:/src/<b><i>$target</i></b -v <b><i>$reproducer_file</i></b>:/testcase -t ossfuzz/<b><i>$target</i></b> reproduce <b><i>$fuzzer</i></b> </pre> - This is essentially the previous command that additonally mounts local sources into the running container. + This is essentially the previous command that additionally mounts local sources into the running container. - *Fix the issue.* Use the previous command to verify you fixed the issue locally. [Use gdb](debugging.md#debugging-fuzzers-with-gdb) if needed. - *Submit the fix.* ClusterFuzz will automatically pick up the changes, recheck the testcase |