Merge pull request hyperledger#1734 from lynnbendixsen/newnetdocrepair

Hands on Walkthrough - moved some steps to fix an issue.

docs/source/NewNetwork/NewNetwork.md

@@ -37,7 +37,7 @@
    The Stewards must:
    1. Generate Steward DIDs as described in [Creating DID](./CreateDID.md).
    1. Install their node as described in [Installation and configuration of Indy-Node](../installation-and-configuration.md) (with some small adjustments):
-      1. Determine a name for the new network and have the stewards substitute it in the appropriate places in the guide, such as when setting the network name and creating the directory when creating the keys for the node.
+      1. Determine a name for the new network and have the stewards substitute it in the appropriate places in the guide, such as when setting the network name and creating the directory when creating the keys for the node. This step MUST be completed before running init_indy_node as part of step [3.2.3 Create the Key for the Validator Node](https://github.com/lynnbendixsen/indy-node/blob/master/docs/source/installation-and-configuration.md#323-create-the-key-for-the-validator-node). 
       1. They all need to stop at the normal place ([3.5. Add Node to a Pool](../installation-and-configuration.md#3.5.-Add-Node-to-a-Pool)) as instructed in the guide as the steps that follow differ when creating a new network.  The following sections of this guide describe the steps required to start the new network.
 
    Once the Stewards have created their DID and Verkey, and performed the initial setup of they node, give the Stewards access to a spreadsheet like [this one](https://docs.google.com/spreadsheets/d/1LDduIeZp7pansd9deXeVSqGgdf0VdAHNMc7xYli3QAY/edit#gid=0) and have them fill out their own row of the Stewards sheet.  The completed sheet will be used to generate the genesis transaction files for the network.   

docs/source/installation-and-configuration.md

@@ -254,7 +254,8 @@ Many providers, such as AWS, use local, non-routable IP addresses on their nodes
 
 Please run the following on the Validator before running `init_indy_node`.
 
-In the `/etc/indy/indy_config.py` file, change the Network name from “sandbox” (Sovrin StagingNet) to “net3” (Sovrin BuilderNet) (use sudo to edit the file or use `sudo sed -i -re "s/(NETWORK_NAME = ')\w+/\1net3/" /etc/indy/indy_config.py)` then run the following commands:
+In the `/etc/indy/indy_config.py` file, change the Network name from “sandbox” (Sovrin StagingNet) to “net3” (Sovrin BuilderNet) (use sudo to edit the file or use `sudo sed -i -re "s/(NETWORK_NAME = ')\w+/\1net3/" /etc/indy/indy_config.py)` then run the following commands:  
+Note: **This is where you would substitute the directory name of the new network if you were setting up a new network.**
 ```
 sudo -i -u indy mkdir /var/lib/indy/net3
 cd /var/lib/indy/net3
@@ -328,7 +329,8 @@ At this point you should have the following data available:
 #### 3.5.1 Configuration
 After you have been informed that your public key has been placed onto the ledger of the Network, you may complete the configuration steps to activate your Validator node on that network.
 
-Things to verify before activating the node:
+Things to verify before activating the node:  
+Note: If you are creating a new network, substitute the new networks directory name for 'net3' below.
 - `cat /etc/indy/indy_config.py`
   - Ensure the network configuration is correct.
 - `cat /etc/indy/indy.env`

sample/Network/README.md

@@ -42,7 +42,12 @@ For the sake of simplicity this walkthrough runs all of the nodes on the local m
    newNetwork:indy> did new seed=000000000000000000000000Steward4
    Did "TWwCRQRZ2ZHMJFn9TzLp7W" has been created with "~UhP7K35SAXbix1kCQV4Upx" verkey
    ```
-5. Create Validator Node keys
+5. Edit `/etc/indy/indy_config.py` and change the network name.
+   `NETWORK_NAME = "newNetwork"`
+
+6. `mkdir /var/lib/indy/newNetwork`
+
+7. Create Validator Node keys
 
    > The seed will be randomly generated. As mentioned above with the seed you can recreate the key!
 
@@ -100,9 +105,9 @@ For the sake of simplicity this walkthrough runs all of the nodes on the local m
    Proof of possession for BLS key is QsrUH1e5zsdiEGij1NeY9S7CwzUdU2rzjskHNGHCQ8rtgYZyBC99MgRPzgkJHP86nWQUo2fSRvyWLQdBwvWfNtSqUBQgVScQPHg9CJXWWohWnzSP4ViBo8EEeGXEoP2NPeRnFCCfuhYAC7stZgBATFyvdFRwG58ws76qQQQsfDDHBV
    ```
 
-6. Fill in the spreadsheet.
+8. Fill in the spreadsheet.
 
-7. Download the script from [https://github.com/sovrin-foundation/steward-tools/tree/master/create_genesis] and generate the genesis file.
+9. Download the script from [https://github.com/sovrin-foundation/steward-tools/tree/master/create_genesis] and generate the genesis file.
 
    ```
    $ python genesis_from_files.py --trustees Trustees.csv --stewards Stewards.csv 
@@ -115,11 +120,6 @@ For the sake of simplicity this walkthrough runs all of the nodes on the local m
    INFO:root:Recovering tree from transaction log
    INFO:root:Recovered tree in 0.000322740000228805 seconds
    ```
-8. Edit `/etc/indy/indy_config.py` and change the network name.
-   `NETWORK_NAME = "newNetwork"`
-
-9. `mkdir /var/lib/indy/newNetwork`
-
 10. `cp domain_transactions_genesis /var/lib/indy/newNetwork/ && cp pool_transactions_genesis /var/lib/indy/newNetwork/`
 
 11. Start the nodes:
@@ -129,4 +129,4 @@ For the sake of simplicity this walkthrough runs all of the nodes on the local m
     start_indy_node Steward2 0.0.0.0 9703 0.0.0.0 9704
     start_indy_node Steward3 0.0.0.0 9705 0.0.0.0 9706
     start_indy_node Steward4 0.0.0.0 9707 0.0.0.0 9708     
-    ```
+    ```