Fix link

README.md

@@ -47,7 +47,7 @@ $ docker-compose up
 After the cluster is synced, you can validate by deploying, invoking or querying chaincode from the container or from the
 host. See [hyperledger-peer](https://github .com/yeasy/docker-hyperledger-peer) if you've not familiar on that.
 
-This refers the example from the [hyperledger](https://github.com/hyperledger/fabric) project.
+This refers the example from the [hyperledger](https://github.com/hyperledger/fabric/tree/master/consensus/docker-compose-files) project.
 
 ## [mongo_cluster](mongo_cluster)
 Start 3 mongo instance to make a replica set.

hyperledger/compose-defaults.yml

@@ -2,7 +2,9 @@
 # Notice that chaincode is executed inside docker in default net mode
 # https://github.com/yeasy/docker-compose-files
 
-# validating node as a root
+# If you want enable consensus, just uncomment the
+# CORE_PEER_VALIDATOR_CONSENSUE=obcpbft line
+# See https://github.com/hyperledger/fabric/blob/master/docs/dev-setup/devnet-setup.md#using-consensus-plugin for more details.
 vp:
   image: yeasy/hyperledger-peer:latest
   restart: unless-stopped
@@ -10,7 +12,7 @@ vp:
     - CORE_PEER_ADDRESSAUTODETECT=true
     - CORE_PEER_NETWORKID=dev
     - CORE_LOGGING_LEVEL=warning
-    #- CORE_PEER_VALIDATOR_CONSENSUS=obcpbft
+    - CORE_PEER_VALIDATOR_CONSENSUS=obcpbft
   expose:
   - "30303"
   - "30304"