about summary refs log tree commit diff
path: root/docs/FAQ.md
diff options
context:
space:
mode:
authorllzmb <46303940+llzmb@users.noreply.github.com>2021-12-02 21:23:22 +0100
committerllzmb <46303940+llzmb@users.noreply.github.com>2021-12-02 21:23:22 +0100
commitaa6586a761c47da1f202221c9a449b692cacbcae (patch)
treef643712e4a2cf16491449c74a118253cb001dc5d /docs/FAQ.md
parent377adb776ee2adb3cb17a174279e384ae9dd590c (diff)
downloadafl++-aa6586a761c47da1f202221c9a449b692cacbcae.tar.gz
Fix typos - 1st run
Diffstat (limited to 'docs/FAQ.md')
-rw-r--r--docs/FAQ.md2
1 files changed, 1 insertions, 1 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.