commit c47ef307012e218bdeb7ad6e65a0c0e1773bf885
author Allen Webb <allenwebb@google.com> Wed Oct 31 22:01:40 2018
committer chrome-bot <chrome-bot@chromium.org> Thu Nov 01 00:52:53 2018
tree d45a0e45b1b3f7153cb68d67074df84e7c29be2d
parent 29ae16da4d97ff6a4d882b87584d9cf8a55545af

fuzzing: Add clarification to binary path.

This clarifies the absolute path where fuzzing targets are emerged.

Change-Id: Idce1b536591575dbcb73a2bad9a23996795a165b
Reviewed-on: https://chromium-review.googlesource.com/1311633
Commit-Ready: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Caroline Tice <cmtice@chromium.org>

fuzzing.md

diff --git a/fuzzing.md b/fuzzing.md
index c54b76b..7b1293f 100644
--- a/fuzzing.md
+++ b/fuzzing.md
@@ -242,9 +242,9 @@
     ```
 
     You should verify that your fuzzer was built and that it was installed in
-    `/usr/libexec/fuzzers/` (make sure the owners file was installed there as
-    well). To run your fuzzer locally, you first run this script *outside your
-    chroot* to set up your environment properly:
+    `/build/${BOARD}/usr/libexec/fuzzers/` (make sure the owners file was
+    installed there as well). To run your fuzzer locally, you first run this
+    script *outside your chroot* to set up your environment properly:
 
     ```bash
     $ path-to-chroot/chromite/bin/cros_fuzz_test_env --board=${BOARD}