about summary refs log tree commit diff
diff options
context:
space:
mode:
authorintrigus-lgtm <60750685+intrigus-lgtm@users.noreply.github.com>2022-01-11 17:13:25 +0100
committerGitHub <noreply@github.com>2022-01-11 17:13:25 +0100
commitd8920e31f861501156f366a54f80f9a9f9368df7 (patch)
tree74ebaa0b2bc9ce207a31c6ba7e2733e701f02910
parent6a7f184c4e27796734a1d8408c8f8abdfc04cad5 (diff)
downloadafl++-d8920e31f861501156f366a54f80f9a9f9368df7.tar.gz
Add a comma to make sentence easier to understand.
-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).