diff options
| author | van Hauser <vh@thc.org> | 2022-01-11 19:35:04 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-11 19:35:04 +0100 |
| commit | 741dcabd5dfca3607a86acd916b3563e01c3ccea (patch) | |
| tree | 0a5082f8c79e2feee4ba1a1bf7a76d0e0d0030cb /docs/best_practices.md | |
| parent | c7dbeb856866b9ca8f9772ff965edce91ce71659 (diff) | |
| parent | d8920e31f861501156f366a54f80f9a9f9368df7 (diff) | |
| download | afl++-741dcabd5dfca3607a86acd916b3563e01c3ccea.tar.gz | |
Merge pull request #1248 from intrigus-lgtm/patch-2
Fix two typos.
Diffstat (limited to 'docs/best_practices.md')
| -rw-r--r-- | docs/best_practices.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/best_practices.md b/docs/best_practices.md index 96c6e3c2..133c645e 100644 --- a/docs/best_practices.md +++ b/docs/best_practices.md @@ -116,7 +116,7 @@ allows you to define network state with different type of data packets. ### Improving stability -For fuzzing a 100% stable target that covers all edges is the best case. A 90% +For fuzzing, a 100% stable target that covers all edges is the best case. A 90% stable target that covers all edges is, however, better than a 100% stable target that ignores 10% of the edges. @@ -189,4 +189,4 @@ coding and/or disassembly and is effectively possible only with `afl-clang-fast` Recompile, fuzz it, be happy :) This link explains this process for - [Fuzzbench](https://github.com/google/fuzzbench/issues/677). \ No newline at end of file + [Fuzzbench](https://github.com/google/fuzzbench/issues/677). |