about summary refs log tree commit diff
path: root/docs/rpc_statsd.md
diff options
context:
space:
mode:
authorKuang-che Wu <kcwu@chromium.org>2021-10-10 21:03:43 +0800
committerKuang-che Wu <kcwu@chromium.org>2021-10-10 21:03:43 +0800
commitf6fbbf8150c8a41b7cd40a2413b1c6f66b24c6c8 (patch)
tree2d0bbe30278b50a681519a765aafb4a7eb739051 /docs/rpc_statsd.md
parent158e881ad46d96d06f70e5c3bdf661ac59981c3c (diff)
downloadafl++-f6fbbf8150c8a41b7cd40a2413b1c6f66b24c6c8.tar.gz
Fix document paths.
Diffstat (limited to 'docs/rpc_statsd.md')
-rw-r--r--docs/rpc_statsd.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/rpc_statsd.md b/docs/rpc_statsd.md
index 288d56cb..9b3d8d40 100644
--- a/docs/rpc_statsd.md
+++ b/docs/rpc_statsd.md
@@ -50,7 +50,7 @@ Depending on your StatsD server, you will be able to monitor, trigger alerts, or
     -  `librato`
     -  `signalfx`
     
-    For more information on environment variables, see [docs/env_variables.md](docs/env_variables.md).
+    For more information on environment variables, see [env_variables.md](env_variables.md).
 
     Note: When using multiple fuzzer instances with StatsD it is *strongly* recommended to set up `AFL_STATSD_TAGS_FLAVOR` to match your StatsD server. This will allow you to see individual fuzzer performance, detect bad ones, and see the progress of each strategy.
 
@@ -152,4 +152,4 @@ To run your fuzzing instances:
 AFL_STATSD_TAGS_FLAVOR=dogstatsd AFL_STATSD=1 afl-fuzz -M test-fuzzer-1 -i i -o o [./bin/my-application] @@
 AFL_STATSD_TAGS_FLAVOR=dogstatsd AFL_STATSD=1 afl-fuzz -S test-fuzzer-2 -i i -o o [./bin/my-application] @@
 ...
-```
\ No newline at end of file
+```