[llvm] r286299 - [libFuzzer] minor docs update

[Kostya Serebryany via llvm-commits]

Author: kcc
Date: Tue Nov  8 15:57:37 2016
New Revision: 286299

URL: http://llvm.org/viewvc/llvm-project?rev=286299&view=rev
Log:
[libFuzzer] minor docs update

Modified:
    llvm/trunk/docs/LibFuzzer.rst

Modified: llvm/trunk/docs/LibFuzzer.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/LibFuzzer.rst?rev=286299&r1=286298&r2=286299&view=diff
==============================================================================
--- llvm/trunk/docs/LibFuzzer.rst (original)
+++ llvm/trunk/docs/LibFuzzer.rst Tue Nov  8 15:57:37 2016
@@ -72,7 +72,7 @@ Like this:
   }
 
 Note that this fuzz target does not depend on libFuzzer in any way
-ans so it is possible and even desirable to use it with other fuzzing engines
+and so it is possible and even desirable to use it with other fuzzing engines
 e.g. AFL_ and/or Radamsa_.
 
 Some important things to remember about fuzz targets:
@@ -81,8 +81,8 @@ Some important things to remember about
 * It must tolerate any kind of input (empty, huge, malformed, etc).
 * It must not `exit()` on any input.
 * It may use threads but ideally all threads should be joined at the end of the function.
-* It must be as deterministic as possible. Non-determinism (e.g. random decisions not based on the input byte) will make fuzzing inefficient.
-* It must be fast. Try avoiding cubic or greater complexity.
+* It must be as deterministic as possible. Non-determinism (e.g. random decisions not based on the input bytes) will make fuzzing inefficient.
+* It must be fast. Try avoiding cubic or greater complexity, logging, or excessive memory consumption.
 * Ideally, it should not modify any global state (although that's not strict).