about summary refs log tree commit diff
path: root/docs/best_practices.md
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2022-01-20 16:17:08 +0100
committerGitHub <noreply@github.com>2022-01-20 16:17:08 +0100
commit7aced239e8a0855d87ecc921ba5691b29202ec1e (patch)
treea8e877a149495ea4ec48723d8af57426f8322a3a /docs/best_practices.md
parent9242e0db8ac8a0e82d78432af389108e74700f00 (diff)
parentd1de12d6175cd84357eadbf204e15b184b22ae42 (diff)
downloadafl++-7aced239e8a0855d87ecc921ba5691b29202ec1e.tar.gz
Merge pull request #1294 from AFLplusplus/dev
Push to stable
Diffstat (limited to 'docs/best_practices.md')
-rw-r--r--docs/best_practices.md4
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).