Clarify the initial participant/bootstrap registrar for deploying to …

…fabric via playground. (#3386)

* first pass bnd-deploy

Signed-off-by: EdProsser <[email protected]>

* quick edit

Signed-off-by: EdProsser <[email protected]>

* final edit

Signed-off-by: EdProsser <[email protected]>

* daves comments

Signed-off-by: EdProsser <[email protected]>

packages/composer-website/jekylldocs/business-network/bnd-deploy.md

@@ -27,6 +27,8 @@ In {{site.data.conrefs.hlf_full}} v1.0, peers enforce the concepts of administra
 To make that identity and its certificates available, you must create a Peer Admin business network card using the certificate and private key associated with the peer admin identity.
 {{site.data.conrefs.composer_full}} provides a sample {{site.data.conrefs.hlf_full}} v1.0 network. The peer administrator for this network is called `PeerAdmin`, and the identity is automatically imported for you when you use the sample scripts for starting the network. Please note that the peer administrator may be given a different name for other {{site.data.conrefs.hlf_full}} v1.0 networks.
 
+**Important**: When deploying a business network to {{site.data.conrefs.hlf_full}} v1.0 a bootstrap registrar is defined in the {{site.data.conrefs.hlf_full}} Certificate Authority (CA) configuration. The {{site.data.conrefs.composer_full}} development environment contains a preconfigured instance of {{site.data.conrefs.hlf_full}} with a specific enrollment ID and enrollment secret for the bootstrap registrar.
+
 ## Business network administrators
 
 When you deploy a business network, access controls are enforced as per the access control rules specified in the business network definition. Each business network must have at least one participant, and that participant must have a valid identity for accessing the business network. Otherwise, client applications cannot interact with the business network.
@@ -65,12 +67,13 @@ If the business network administrator has an enrollment ID and enrollment secret
 
 ## Deploying business networks using Playground locally
 
-When deploying a business network to {{site.data.conrefs.hlf_full}} v1.0 using the Playground locally, you must follow the process above to connect using the peer admin identity.
+**Please note**: When using a local Playground instance to deploy a business network to {{site.data.conrefs.hlf_full}} v1.0, as part of the deployment process you must choose how to provide credentials for the initial business network participant. The initial participant will be a [**NetworkAdmin**](https://github.com/hyperledger/composer/blob/master/packages/composer-common/lib/system/org.hyperledger.composer.system.cto).
 
-Identities in playground are associated with business network cards, comprising a connection profile, identity metadata, and certificates.
+When deploying a business network using playground, you will be prompted to enter the credentials for the initial participant. Credentials can be provided either as a certificate or as a pre-defined enrollment ID and enrollment secret. If you are using the instance of {{site.data.conrefs.hlf_full}} set up in the {{site.data.conrefs.composer_full}} development environment, the bootstrap registrar enrollment ID is `admin` and the bootstrap registrar enrollment secret is `adminpw`.  This initial participant uses the credentials set for the bootstrap registrar in the {{site.data.conrefs.hlf_full}} Certificate Authority (CA), and will be a [**NetworkAdmin**](https://github.com/hyperledger/composer/blob/master/packages/composer-common/lib/system/org.hyperledger.composer.system.cto).
 
 When deploying a business network using Playground locally, you must have at least one business network card with the `PeerAdmin` role and at least one business network card with the `ChannelAdmin` role. Each of these business network cards must contain the correct admin certificates.
 
+
 ## Errors deploying a business network to a local fabric using the {{site.data.conrefs.composer_full}} Playground
 
 When deploying a business network to an instance of {{site.data.conrefs.hlf_full}} by using a locally installed {{site.data.conrefs.composer_full}} Playground, you may encounter the following error:

packages/composer-website/jekylldocs/reference/connectionprofile.md

@@ -15,9 +15,8 @@ A Connection Profile is used by {{site.data.conrefs.composer_full}} to connect t
 
 ## Creating a Connection Profile
 
-1. Create a new file called `connection.json` which will define the connection profile that contains the following information for {{site.data.conrefs.hlf_full}} v1.0. 
+A connection profile for {{site.data.conrefs.hlf_full}} v1.0 uses the following format:
 
-A simple connection profile that doesn't use TLS has the following format:
 
         {
             "name": "my-fabric",
@@ -42,9 +41,10 @@ A simple connection profile that doesn't use TLS has the following format:
             "timeout": 300
         }
 
-If you are connecting to {{site.data.conrefs.hlf_full}} v1.0 and are not using TLS or if you don't need the trustedRoots and verify options of the Certificate Authority definition you can use the following simplified connection profile:
 
-A more complete example of a connection profile with all possible properties defined is shown here (property values are examples and not necessarily valid values)
+  A more complete example of a connection profile with all possible properties defined is shown here (property values are examples and not necessarily valid values)
+
+
 
          {
             "name": "my-fabric",
@@ -127,7 +127,7 @@ Support for HSM (Hardware Security Module)is now possible so long as you have PK
                 "pin": 98765432
             }
         };
- 
+
   - `library` is the absolute path to the pkcs#11 library required for communication with your specific HSM
   - `slot` is the configured slot number for the HSM
   - `pin` is the pin defined for access to that slot.

packages/composer-website/jekylldocs/tutorials/playground-tutorial.md

@@ -10,7 +10,7 @@ excerpt: The Playground tutorial runs through creating your first business netwo
 
 # Playground Tutorial
 
-In this step by step tutorial we'll walk through setting up a business network, defining our assets, participants and transactions, and testing our network by creating some participants and an asset, and submitting transactions to change the ownership of the asset from one to another.
+In this step by step tutorial we'll walk through setting up a business network, defining our assets, participants and transactions, and testing our network by creating some participants and an asset, and submitting transactions to change the ownership of the asset from one to another. This tutorial is intended to act as an introduction to {{site.data.conrefs.composer_full}} concepts using the online playground environment.
 
 ## Step One: Open the {{site.data.conrefs.composer_full}} Playground