diff --git a/doc/productivity.md b/doc/productivity.md
index b25ddc94e5..39f3cdf194 100644
--- a/doc/productivity.md
+++ b/doc/productivity.md
@@ -73,9 +73,9 @@ When rebuilding during development, note that running `make`, without giving a t
 Obviously, it is important to build and run the tests at appropriate times -- but when you just want a quick compile to check your work, consider picking one or a set of build targets relevant to what you're working on, e.g.:
 
 ```sh
-make src/bitcoind src/bitcoin-cli
-make src/qt/bitcoin-qt
-make -C src bitcoin_bench
+make src/dashd src/dash-cli
+make src/qt/dash-qt
+make -C src dash_bench
 ```
 
 (You can and should combine this with `-j`, as above, for a parallel build.)
@@ -173,7 +173,7 @@ When looking at other's pull requests, it may make sense to add the following se
 ```
 [remote "upstream-pull"]
         fetch = +refs/pull/*:refs/remotes/upstream-pull/*
-        url = git@github.com:bitcoin/bitcoin.git
+        url = git@github.com:dashpay/dash.git
 ```
 
 This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER.