about summary refs log tree commit diff
path: root/qemu_mode
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2021-11-30 10:56:02 +0100
committerGitHub <noreply@github.com>2021-11-30 10:56:02 +0100
commitedbf41f78619162071987a44b46ab7f739bb85c1 (patch)
tree3be630bc3a5d1ea65f3bb49863b37ff5b9d688c4 /qemu_mode
parent235bb3235e45a81eb2b524f3a76346d91a163e3d (diff)
parent8968bee836ecde0fa2427b84b2f3ac85c276958f (diff)
downloadafl++-edbf41f78619162071987a44b46ab7f739bb85c1.tar.gz
Merge pull request #1172 from llzmb/docs_cleanup_folder_2
Clean up docs folder
Diffstat (limited to 'qemu_mode')
-rw-r--r--qemu_mode/README.md5
-rw-r--r--qemu_mode/libqasan/README.md2
2 files changed, 4 insertions, 3 deletions
diff --git a/qemu_mode/README.md b/qemu_mode/README.md
index d28479d9..c62309a2 100644
--- a/qemu_mode/README.md
+++ b/qemu_mode/README.md
@@ -217,5 +217,6 @@ them at run time, can be a faster alternative. That said, static rewriting is
 fraught with peril, because it depends on being able to properly and fully model
 program control flow without actually executing each and every code path.
 
-Checkout the "Fuzzing binary-only targets" section in our main README.md and
-the docs/binaryonly_fuzzing.md document for more information and hints.
+Check out
+[docs/fuzzing_binary-only_targets.md](../docs/fuzzing_binary-only_targets.md)
+for more information and hints.
diff --git a/qemu_mode/libqasan/README.md b/qemu_mode/libqasan/README.md
index 4a241233..6a65c12b 100644
--- a/qemu_mode/libqasan/README.md
+++ b/qemu_mode/libqasan/README.md
@@ -19,7 +19,7 @@ finding capabilities during fuzzing) is WIP.
 ### When should I use QASan?
 
 If your target binary is PIC x86_64, you should also give a try to
-[retrowrite](https://github.com/HexHive/retrowrite) for static rewriting.
+[RetroWrite](https://github.com/HexHive/retrowrite) for static rewriting.
 
 If it fails, or if your binary is for another architecture, or you want to use
 persistent and snapshot mode, AFL++ QASan mode is what you want/have to use.