diff --git a/packages/composer-website/jekylldocs/tutorials/developer-guide.md b/packages/composer-website/jekylldocs/tutorials/developer-guide.md index 9f93e244ce..8310d722d3 100644 --- a/packages/composer-website/jekylldocs/tutorials/developer-guide.md +++ b/packages/composer-website/jekylldocs/tutorials/developer-guide.md @@ -490,12 +490,12 @@ _Note: You'll notice that the flag '-p' specifies that we should use a v1 connec After approximately 30 seconds or so, the business network should have been deployed to your local {{site.data.conrefs.hlf_full}}. You should see output as follows: ``` -user@ubuntu $ composer network deploy -a my-network.bna -p hlfv1 -i admin -s adminpw +user@ubuntu $ composer network deploy -a my-network.bna -p hlfv1 -i PeerAdmin -s randomString Deploying business network from archive: my-network.bna Business network definition: -Identifier: my-network@0.0.1 -Description: My very first Hyperledger Composer Network + Identifier: my-network@0.1.3 + Description: The Hello World of Hyperledger Composer samples ✔ Deploying business network definition. This may take a minute... @@ -515,8 +515,8 @@ Which should give the following output: user@ubuntu $ composer network ping -n my-network -p hlfv1 -i admin -s adminpw The connection to the network was successfully tested: my-network -version: 0.7.2 -participant: + version: 0.10.0 + participant: Command succeeded ```