Dashify a few docs and the use of an address

CONTRIBUTING.md

@@ -81,7 +81,7 @@ Project maintainers aim for a quick turnaround on refactoring pull requests, so
 "Decision Making" Process
 -------------------------
 
-The following applies to code changes to the Dash Core project (and related projects such as libsecp256k1), and is not to be confused with overall Bitcoin Network Protocol consensus changes.
+The following applies to code changes to the Dash Core project (and related projects such as libsecp256k1), and is not to be confused with overall Dash Network Protocol consensus changes.
 
 Whether a pull request is merged into Dash Core rests with the project merge maintainers and ultimately the project lead.
 

doc/benchmarking.md

@@ -1,10 +1,10 @@
 Benchmarking
 ============
 
-Bitcoin Core has an internal benchmarking framework, with benchmarks
+Dash Core has an internal benchmarking framework, with benchmarks
 for cryptographic algorithms such as SHA1, SHA256, SHA512 and RIPEMD160. As well as the rolling bloom filter.
 
-After compiling bitcoin-core, the benchmarks can be run with:
+After compiling dash-core, the benchmarks can be run with:
 `src/bench/bench_bitcoin`
 
 The output will look similar to:

src/rpc/misc.cpp

@@ -519,7 +519,7 @@ UniValue signmessagewithprivkey(const UniValue& params, bool fHelp)
             "\nCreate the signature\n"
             + HelpExampleCli("signmessagewithprivkey", "\"privkey\" \"my message\"") +
             "\nVerify the signature\n"
-            + HelpExampleCli("verifymessage", "\"1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ\" \"signature\" \"my message\"") +
+            + HelpExampleCli("verifymessage", "\"XwnLY9Tf7Zsef8gMGL2fhWA9ZmMjt4KPwg\" \"signature\" \"my message\"") +
             "\nAs json rpc\n"
             + HelpExampleRpc("signmessagewithprivkey", "\"privkey\", \"my message\"")
         );