Link fixes in create channel tutorial (#2661)

Signed-off-by: Nikhil Gupta <ngupta@symbridge.com>
hyperledger · Jun 9, 2021 · b4cd030 · b4cd030
1 parent dde41d9
commit b4cd030
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/source/create_channel/create_channel_test_net.md b/docs/source/create_channel/create_channel_test_net.md
@@ -228,7 +228,7 @@ export CORE_PEER_ADDRESS=localhost:7051
 
 In order to use the peer CLI, we also need to modify the `FABRIC_CONFIG_PATH`:
 ```
-FABRIC_CFG_PATH=$PWD/../config/
+export FABRIC_CFG_PATH=$PWD/../config/
 ```
 To join the test network peer from `Org1` to the channel `channel1` simply pass the genesis block in a join request:
 ```
@@ -293,7 +293,7 @@ We can now start using the `configtxlator` tool to start working with the channe
 
 ```
 configtxlator proto_decode --input config_block.pb --type common.Block --output config_block.json
-jq .data.data[0].payload.data.config config_block.json > config.json
+jq '.data.data[0].payload.data.config' config_block.json > config.json
 ```
 
 These commands convert the channel configuration block into a streamlined JSON, `config.json`, that will serve as the baseline for our update. Because we don't want to edit this file directly, we will make a copy that we can edit. We will use the original channel config in a future step.
@@ -357,7 +357,7 @@ cd channel-artifacts
 You can then decode and copy the configuration block.
 ```
 configtxlator proto_decode --input config_block.pb --type common.Block --output config_block.json
-jq .data.data[0].payload.data.config config_block.json > config.json
+jq '.data.data[0].payload.data.config' config_block.json > config.json
 cp config.json config_copy.json
 ```