Fuzzing documentation "PIVX-fication"

Author: furszy

doc/developer-notes.md

@@ -262,7 +262,7 @@ make cov
 ```
 
 **Sanitizers**
-Bitcoin can be compiled with various "sanitizers" enabled, which add
+PIVX can be compiled with various "sanitizers" enabled, which add
 instrumentation for issues regarding things like memory safety, thread race
 conditions, or undefined behavior. This is controlled with the
 `--with-sanitizers` configure flag, which should be a comma separated list of

doc/fuzzing.md

@@ -1,4 +1,4 @@
-Fuzz-testing Bitcoin Core
+Fuzz-testing PIVX Core
 ==========================
 
 A special test harness in `src/test/fuzz/` is provided for each fuzz target to
@@ -49,7 +49,7 @@ For macOS you may need to ignore x86 compilation checks when running `make`:
 
 ### Instrumentation
 
-To build Bitcoin Core using AFL instrumentation (this assumes that the
+To build PIVX Core using AFL instrumentation (this assumes that the
 `AFLPATH` was set as above):
 ```
 ./configure --disable-shared --enable-tests --enable-fuzz CC=${AFLPATH}/afl-gcc CXX=${AFLPATH}/afl-g++
@@ -125,7 +125,7 @@ example using `brew install llvm`.
 
 Should you run into problems with the address sanitizer, it is possible you
 may need to run `./configure` with `--disable-asm` to avoid errors
-with certain assembly code from Bitcoin Core's code. See [developer notes on sanitizers](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#sanitizers)
+with certain assembly code from PIVX Core's code. See [developer notes on sanitizers](https://github.com/PIVX-Project/PIVX/blob/master/doc/developer-notes.md#sanitizers)
 for more information.
 
 You may also need to take care of giving the correct path for clang and