From c5479ba663ac88b0e78cc144b6f272553c107cf2 Mon Sep 17 00:00:00 2001 From: Alex Groce Date: Thu, 3 Jan 2019 20:19:06 -0700 Subject: [PATCH] Typos --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 82d41a2..980681b 100644 --- a/README.md +++ b/README.md @@ -120,9 +120,9 @@ DeepState consists of a static library, used to write test harnesses, and comman By default, DeepState is not very verbose about testing activity, other than failing tests. The `--log-level` argument lowers the threshold for output, with 0 = `DEBUG`, 1 = `TRACE` (output from the -tests, including `printf`s), and 2 = INFO (DeepState messages, the default), 3 = `WARNING`, -4 = `ERROR`, and 5 = `EXTERNAL` (output from other programs such as -libFuzzer), and 6 = `CRITICAL`/`FATAL` messages. +tests, including from `printf`), 2 = INFO (DeepState messages, the default), 3 = `WARNING`, +4 = `ERROR`, 5 = `EXTERNAL` (output from other programs such as +libFuzzer), and 6 = `CRITICAL` messages. ## A Note on Mac OS and Forking @@ -140,7 +140,7 @@ generates tests using completely random data. Using this fuzzer is as simple as calling the native executable with the `--fuzz` argument. The fuzzer also takes a `seed` and `timeout` (default of two minutes) to control the fuzzing. If you want to actually save the test cases -generated, you need to add a `--output_test_dir` arument to tell +generated, you need to add a `--output_test_dir` argument to tell DeepState where to put the generated tests. By default fuzzing saves only failing and crashing tests and only when given an output directory.