about summary refs log tree commit diff
diff options
context:
space:
mode:
-rw-r--r--README.md2
-rw-r--r--docs/afl-fuzz_approach.md2
-rw-r--r--docs/fuzzing_in_depth.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 93c0dd10..08363149 100644
--- a/README.md
+++ b/README.md
@@ -86,7 +86,7 @@ Step-by-step quick start:
    ```
 
 2. Get a small but valid input file that makes sense to the program. When
-   fuzzing verbose syntax (SQL, HTTP, etc), create a dictionary as described in
+   fuzzing verbose syntax (SQL, HTTP, etc.), create a dictionary as described in
    [dictionaries/README.md](dictionaries/README.md), too.
 
 3. If the program reads from stdin, run `afl-fuzz` like so:
diff --git a/docs/afl-fuzz_approach.md b/docs/afl-fuzz_approach.md
index 702e020d..fefde029 100644
--- a/docs/afl-fuzz_approach.md
+++ b/docs/afl-fuzz_approach.md
@@ -523,7 +523,7 @@ into each of them or deploy scripts to read the fuzzer statistics. Using
 to your favorite StatsD server. Depending on your StatsD server, you will be
 able to monitor, trigger alerts, or perform actions based on these metrics (e.g:
 alert on slow exec/s for a new build, threshold of crashes, time since last
-crash > X, etc).
+crash > X, etc.).
 
 The selected metrics are a subset of all the metrics found in the status and in
 the plot file. The list is the following: `cycle_done`, `cycles_wo_finds`,
diff --git a/docs/fuzzing_in_depth.md b/docs/fuzzing_in_depth.md
index 011ba783..d408aa91 100644
--- a/docs/fuzzing_in_depth.md
+++ b/docs/fuzzing_in_depth.md
@@ -722,7 +722,7 @@ just for AFL++).
 Here are some of the most important caveats for AFL++:
 
 - AFL++ detects faults by checking for the first spawned process dying due to a
-  signal (SIGSEGV, SIGABRT, etc). Programs that install custom handlers for
+  signal (SIGSEGV, SIGABRT, etc.). Programs that install custom handlers for
   these signals may need to have the relevant code commented out. In the same
   vein, faults in child processes spawned by the fuzzed target may evade
   detection unless you manually add some code to catch that.