diff options
| author | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 21:23:22 +0100 |
|---|---|---|
| committer | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 21:23:22 +0100 |
| commit | aa6586a761c47da1f202221c9a449b692cacbcae (patch) | |
| tree | f643712e4a2cf16491449c74a118253cb001dc5d /docs | |
| parent | 377adb776ee2adb3cb17a174279e384ae9dd590c (diff) | |
| download | afl++-aa6586a761c47da1f202221c9a449b692cacbcae.tar.gz | |
Fix typos - 1st run
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/FAQ.md | 2 | ||||
| -rw-r--r-- | docs/fuzzing_in_depth.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md index 27250415..671957ef 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -125,7 +125,7 @@ If you find an interesting or important question missing, submit it via If, however, randomness happens, e.g., a thread reading other external data, reaction to timing, etc., then in some of the re-executions with the same data - the edge coverage result will be different accross runs. Those edges that + the edge coverage result will be different across runs. Those edges that change are then flagged "unstable". The more "unstable" edges, the more difficult for AFL++ to identify valid new paths. diff --git a/docs/fuzzing_in_depth.md b/docs/fuzzing_in_depth.md index 7c464d81..011ba783 100644 --- a/docs/fuzzing_in_depth.md +++ b/docs/fuzzing_in_depth.md @@ -131,7 +131,7 @@ The following options are available when you instrument with LTO mode have to compile the target twice, once specifically with/for this mode by setting `AFL_LLVM_CMPLOG=1`, and pass this binary to afl-fuzz via the `-c` parameter. Note that you can compile also just a cmplog binary and use that - for both, however, there will be a performance penality. You can read more + for both, however, there will be a performance penalty. You can read more about this in [instrumentation/README.cmplog.md](../instrumentation/README.cmplog.md). |