about summary refs log tree commit diff
path: root/README.md
diff options
context:
space:
mode:
authorAndrea Fioraldi <andreafioraldi@gmail.com>2020-02-03 13:02:16 +0100
committerAndrea Fioraldi <andreafioraldi@gmail.com>2020-02-03 13:02:16 +0100
commite2eedefc65bec1a04605f117a11ca8bdf9d80323 (patch)
tree653e28fb2f74790ff35706c9c93ce91893f5a3a2 /README.md
parentfd03c64346ab3f63fc5ceafd891dee245121b5c9 (diff)
downloadafl++-e2eedefc65bec1a04605f117a11ca8bdf9d80323.tar.gz
docs to md
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index e2e073ac..00ae599c 100644
--- a/README.md
+++ b/README.md
@@ -433,11 +433,11 @@ see [http://lcamtuf.coredump.cx/afl/plot/](http://lcamtuf.coredump.cx/afl/plot/)
 Every instance of afl-fuzz takes up roughly one core. This means that on
 multi-core systems, parallelization is necessary to fully utilize the hardware.
 For tips on how to fuzz a common target on multiple cores or multiple networked
-machines, please refer to [docs/parallel_fuzzing.txt](docs/parallel_fuzzing.txt).
+machines, please refer to [docs/parallel_fuzzing.md](docs/parallel_fuzzing.md).
 
 The parallel fuzzing mode also offers a simple way for interfacing AFL to other
 fuzzers, to symbolic or concolic execution engines, and so forth; again, see the
-last section of [docs/parallel_fuzzing.txt](docs/parallel_fuzzing.txt) for tips.
+last section of [docs/parallel_fuzzing.md](docs/parallel_fuzzing.md) for tips.
 
 
 ## 10) Fuzzer dictionaries