Fuzz Docs: Update crbug string

Change-Id: I5a89bd57a941378e355611067f2b978cf43413c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948049
Auto-Submit: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721245}

testing/libfuzzer/reproducing.md

@@ -21,7 +21,7 @@ That means there is a testcase that can be used to reliably reproduce the crash.
 
    For the rest of this walkthrough, we call the path of this
    file: `$TESTCASE_PATH` and the fuzz target you want to reproduce a
-   crash on: `$FUZZER_NAME` (provided as "Fuzz target binary" in the bug
+   crash on: `$FUZZER_NAME` (provided as "Fuzz Target" in the bug
    description).
 
 2. Generate gn build configuration:

third_party/sqlite/fuzz/README.md

@@ -38,7 +38,7 @@ more data is needed, reproduce a bit more manually by first building the target.
 To build the target, first set .gn args to match those in the clusterfuzz link,
 then build and run the fuzzer.
 
-1. `export FUZZER_NAME=sqlite3_fts3_lpm_fuzzer  # FUZZER_NAME is listed in the crbug as the "Fuzz target binary"`
+1. `export FUZZER_NAME=sqlite3_fts3_lpm_fuzzer  # FUZZER_NAME is listed in the crbug as the "Fuzz Target"`
 2. Download the clusterfuzz minimized testcase.
 3. `export CLUSTERFUZZ_TESTCASE=./clusterfuzz-testcase-minimized-sqlite3_fts3_lpm_fuzzer-5756437473656832  # Set the clusterfuzz testcase path to CLUSTERFUZZ_TESTCASE`
 3. `gn args out/Fuzzer  # Set arguments to matches those in the clusterfuzz "Detailed report"'s "GN CONFIG (ARGS.GN)" section`