#64 added links that were missing

_data/apidefinitions/broadcast_ops.yml

@@ -1954,7 +1954,7 @@
         
         VESTS were restored in a later transaction:
           
-        https://hiveblocks.com/tx/1d600db22fc6f9b362db36d9f0fc521b95f8894f
+        [https://hiveblocks.com/tx/1d600db22fc6f9b362db36d9f0fc521b95f8894f](https://hiveblocks.com/tx/1d600db22fc6f9b362db36d9f0fc521b95f8894f)
         
         See: [Block No. 47797680](https://hiveblocks.com/b/47797680), [!19](https://gitlab.syncad.com/hive/hive/-/merge_requests/19), [5edf4f0](https://gitlab.syncad.com/hive/hive/-/commit/5edf4f0ba04426982ba655bf83d5acd746736d49), [restore.js](https://github.com/drov0/restore-hf23-balances/blob/master/restore.js)
       roles:

_nodeop/setting-up-a-testnet.md

@@ -18,7 +18,7 @@ Setting up a testnet can be as simple as running a single Docker command, such a
 docker run -d -P inertia/tintoy:latest
 ```
 
-This docker command is useful for rapid testnet deploy because it only creates 2,000 accounts.
+This docker command is useful for rapid testnet deploy because it only creates 2,000 accounts.  See: [inertia/tintoy](https://hub.docker.com/r/inertia/tintoy)
 
 But in this tutorial, we will go over the **no docker** approach which will create all accounts that exist on mainnet.  The idea is to try to mirror the accounts and balances in proportion to the mainnet.
 

_nodeop/using-hivemind.md

@@ -112,6 +112,15 @@ Now that the basic setup is done you are able to sync the database.
 $ hive sync
 ```
 
+**Note:** Do not use a public node to `hive sync`.  Instead of doing an initial sync, you can use a data dump, to speed up the process: [Daily Hivemind backups
+ :: How to restore](https://peakd.com/hive-139531/@emrebeyler/daily-hivemind-backups#how-to-restore)
+ 
+```bash
+# Assunes 8 cpu cores:
+$ pg_restore -j 8 -U postgres -d hive path/to/dump_file.dump
+$ hive sync
+```
+
 You can also check the status of your synced database.
 
 ```bash