aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVitaly Buka <vitalybuka@google.com>2020-01-07 13:38:56 -0800
committerVitaly Buka <vitalybuka@gmail.com>2020-01-08 14:30:55 -0800
commitfbfc647d61a07c03d9c19cd171e614d5faf78002 (patch)
treec2485361d97522c7e0bfde1e3f8d35532bb26be1
parentba7c2ab5f41599e006eb438849c2518cd1a4ceb2 (diff)
downloadlibprotobuf-mutator-fbfc647d61a07c03d9c19cd171e614d5faf78002.tar.gz
Update README.md
Co-Authored-By: Bhargava Shastry <bshas3@gmail.com>
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index f22ef37..dd8bd97 100644
--- a/README.md
+++ b/README.md
@@ -92,7 +92,7 @@ Please see [libfuzzer_example.cc](/examples/libfuzzer/libfuzzer_example.cc) as a
Sometimes it's necessary to keep particular values in some fields without which the proto
is going to be rejected by fuzzed code. E.g. code may expect consistency between some fields
or it may use some fields as checksums. Such constraints are going to be significant bottleneck
-for fuzzer even if it's capabale to get acceptable values with time.
+for fuzzer even if it's capable of inserting acceptable values with time.
PostProcessorRegistration can be used to avoid such issue and guide your fuzzer towards interesing
code. It registers callback which will be called for each message of particular type after each mutation.