[FAB-6895] Update doc for chaincode mounting

This changes the manual peer chaincode install command
to reflect the correct path of the mounted volume on
the CLI container.
Also fixes an inline reference
[ci-skip]

Change-Id: I46472af16dbdfe7ece355ba8020137cea0510dce
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>

Author: nickgaski

docs/source/build_network.rst

@@ -495,7 +495,7 @@ Start your network:
 If you want to see the realtime logs for your network, then do not supply the ``-d`` flag.
 If you let the logs stream, then you will need to open a second terminal to execute the CLI calls.
 
-.. _peerenvvars::
+.. _peerenvvars:
 
 Environment variables
 ^^^^^^^^^^^^^^^^^^^^^
@@ -651,15 +651,15 @@ place the specified source code flavor onto our peer's filesystem.
 .. code:: bash
 
     # this installs the Go chaincode
-    peer chaincode install -n mycc -v 1.0 -p github.com/chaincode_example02/go/
+    peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/
 
 **Node.js**
 
 .. code:: bash
 
     # this installs the Node.js chaincode
     # make note of the -l flag; we use this to specify the language
-    peer chaincode install -n mycc -v 1.0 -l node -p /opt/gopath/src/github.com/chaincode_example02/node/
+    peer chaincode install -n mycc -v 1.0 -l node -p /opt/gopath/src/github.com/chaincode/chaincode_example02/node/
 
 Next, instantiate the chaincode on the channel. This will initialize the
 chaincode on the channel, set the endorsement policy for the chaincode, and