diff --git a/README.md b/README.md
index 0fa53eb2..fa374b92 100644
--- a/README.md
+++ b/README.md
@@ -165,29 +165,7 @@ it is fairly simple to write API methods to expose database methods.
 Running private testnet
 -----------------------
 
-Normally `witness_node` assumes it won't be producing blocks from
-genesis, or against very old chain state.  We need to get `witness_node`
-to discard this assumption if we actually want to start a new chain,
-so we will need to specify in `config.ini`:
-
-    enable-stale-production = true
-
-We also need to specify which witnesses will produce blocks locally;
-`witness_node` does not assume that it should produce blocks for a given
-witness just because it has the correct private key to do so.  There are
-ten witnesses at genesis of the testnet, block production can be
-enabled for all of them by specifying multiple times in `config.ini`:
-
-    witness-id = "1.6.0"
-    witness-id = "1.6.1"
-    witness-id = "1.6.2"
-    witness-id = "1.6.3"
-    witness-id = "1.6.4"
-    witness-id = "1.6.5"
-    witness-id = "1.6.6"
-    witness-id = "1.6.7"
-    witness-id = "1.6.8"
-    witness-id = "1.6.9"
+See the [documentation](https://github.com/cryptonomex/graphene/wiki/private-testnet) if you want to run a private testnet.
 
 Questions
 ---------
diff --git a/docs b/docs
index cdc8ea81..c004ae42 160000
--- a/docs
+++ b/docs
@@ -1 +1 @@
-Subproject commit cdc8ea8133a999afef8051700a4ce8edb0988ec4
+Subproject commit c004ae42a72d86bbc6c7e8d065deed284fd093a5