Fix typo in nodesdk docs and add line breaks

Change HLC -> HFC in the Running Unit Tests section
Also put line breaks at 80 characters to aid in readability
of the markdown source.

Change-Id: I29623eae09b3eac7d0a843907a5543e4a2b8218e
Signed-off-by: Julian Carrivick <[email protected]>

Author: juliancarrivick-ibm

docs/Setup/NodeSDK-setup.md

@@ -1,12 +1,18 @@
 ## Hyperledger Fabric Client (HFC) SDK for Node.js
 
-The Hyperledger Fabric Client (HFC) SDK provides a powerful and easy to use API to interact with a Hyperledger Fabric blockchain.
+The Hyperledger Fabric Client (HFC) SDK provides a powerful and easy to use API
+to interact with a Hyperledger Fabric blockchain.
 
-This document assumes that you already have set up a Node.js development environment. If not, go [here](https://nodejs.org/en/download/package-manager/) to download and install Node.js for your OS. You'll also want the latest version of `npm` installed. For that, execute `sudo npm install npm -g` to get the latest version.
+This document assumes that you already have set up a Node.js development
+environment. If not, go [here](https://nodejs.org/en/download/package-manager/)
+to download and install Node.js for your OS. You'll also want the latest version
+of `npm` installed. For that, execute `sudo npm install npm -g` to get the
+latest version.
 
 ### Installing the hfc module
 
-We publish the `hfc` node module to `npm`. To install `hfc` from npm simply execute the following command:
+We publish the `hfc` node module to `npm`. To install `hfc` from npm simply
+execute the following command:
 
 ```
 npm install -g hfc
@@ -16,24 +22,41 @@ npm install -g hfc
 
 The sections in this document are as follows:
 
-* The [Getting Started](#getting-started) section is intended to help you quickly get a feel for HFC, how to use it, and some of its common capabilities. This is demonstrated by example.
+* The [Getting Started](#getting-started) section is intended to help you
+quickly get a feel for HFC, how to use it, and some of its common capabilities.
+This is demonstrated by example.
 
-* The [Getting Set Up](#getting-set-up) section shows you how to set up up your environment and how to [run the unit tests](#running-unit-tests). Looking at the implementation of the unit tests will also help you learn more about the APIs by example, including asset management and confidentiality.
+* The [Getting Set Up](#getting-set-up) section shows you how to set up up your
+environment and how to [run the unit tests](#running-unit-tests). Looking at the
+implementation of the unit tests will also help you learn more about the APIs by
+example, including asset management and confidentiality.
 
 ## Getting Started
-This purpose of this section is to help you quickly get a feel for HFC and how you may use it. It is not intended to demonstrate all of its power, but to demonstrate common use cases by example.
+This purpose of this section is to help you quickly get a feel for HFC and how
+you may use it. It is not intended to demonstrate all of its power, but to
+demonstrate common use cases by example.
 
 ### Some basic terminology
-First, there is some basic terminology you should understand. In order to transact on a hyperledger blockchain, you must first have an identity which has been both **registered** and **enrolled**.
+First, there is some basic terminology you should understand. In order to
+transact on a hyperledger blockchain, you must first have an identity which has
+been both **registered** and **enrolled**.
 
-Think of **registration** as *issuing a user invitation* to join a blockchain. It consists of adding a new user name (also called an *enrollment ID*) to the membership service configuration. This can be done programatically with the `Member.register` method, or by adding the enrollment ID directly to the [membersrvc.yaml](https://github.com/hyperledger/fabric/blob/master/membersrvc/membersrvc.yaml) configuration file.
+Think of **registration** as *issuing a user invitation* to join a blockchain.
+It consists of adding a new user name (also called an *enrollment ID*) to the
+membership service configuration. This can be done programatically with the
+`Member.register` method, or by adding the enrollment ID directly to the
+[membersrvc.yaml](https://github.com/hyperledger/fabric/blob/master/membersrvc/membersrvc.yaml)
+configuration file.
 
-Think of **enrollment** as *accepting a user invitation* to join a blockchain. This is always done by the entity that will transact on the blockchain. This can be done programatically via the `Member.enroll` method.
+Think of **enrollment** as *accepting a user invitation* to join a blockchain.
+This is always done by the entity that will transact on the blockchain. This can
+be done programatically via the `Member.enroll` method.
 
 ### Learn by example
 The best way to quickly learn HFC is by example.
 
-The following example demonstrates a typical web app. The web app authenticates a user and then transacts on a blockchain on behalf of that user.
+The following example demonstrates a typical web app. The web app authenticates
+a user and then transacts on a blockchain on behalf of that user.
 
 ```
 /**
@@ -136,13 +159,22 @@ function handleUserRequest(userName, chaincodeID, fcn, args) {
 
 ## Getting Set Up
 
-First, you'll want to have a running peer node and CA. You can follow the instructions for setting up a network [here](https://github.com/hyperledger/fabric/blob/master/docs/Setup/ca-setup.md#Operating-the-CA), and start a single peer node and CA.
+First, you'll want to have a running peer node and CA. You can follow the
+instructions for setting up a network
+[here](https://github.com/hyperledger/fabric/blob/master/docs/Setup/ca-setup.md#Operating-the-CA),
+and start a single peer node and CA.
 
 ### Chaincode Deployment Directory Structure
 
-To have the chaincode deployment succeed in network mode, you must properly set up the chaincode project outside of your Hyperledger Fabric source tree. The following instructions will demonstrate how to properly set up the directory structure to deploy *chaincode_example02* in network mode.
+To have the chaincode deployment succeed in network mode, you must properly set
+up the chaincode project outside of your Hyperledger Fabric source tree. The
+following instructions will demonstrate how to properly set up the directory
+structure to deploy *chaincode_example02* in network mode.
 
-The chaincode project must be placed under the `$GOPATH/src` directory. For example, the [chaincode_example02](https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example02/chaincode_example02.go) project should be placed under `$GOPATH/src/` as shown below.
+The chaincode project must be placed under the `$GOPATH/src` directory. For
+example, the
+[chaincode_example02](https://github.com/hyperledger/fabric/blob/master/examples/chaincode/go/chaincode_example02/chaincode_example02.go)
+project should be placed under `$GOPATH/src/` as shown below.
 
 ```
 mkdir -p $GOPATH/src/github.com/chaincode_example02/
@@ -159,20 +191,29 @@ govendor init
 govendor fetch github.com/hyperledger/fabric
 ```
 
-Now, execute `go build` to verify that all of the chaincode dependencies are present.
+Now, execute `go build` to verify that all of the chaincode dependencies are
+present.
 
 ```
 go build
 ```
 
-Next, we will switch over to the node sdk directory in the fabric repo to run the node sdk tests, to make sure you have everything properly set up. Verify that the [chain-tests.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/chain-tests.js) unit test file points to the correct chaincode project path. The default directory is set to `github.com/chaincode_example02/` as shown below. If you placed the sample chaincode elsewhere, then you will need to change that.
+Next, we will switch over to the node sdk directory in the fabric repo to run
+the node sdk tests, to make sure you have everything properly set up. Verify
+that the
+[chain-tests.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/chain-tests.js)
+unit test file points to the correct chaincode project path. The default
+directory is set to `github.com/chaincode_example02/` as shown below. If you
+placed the sample chaincode elsewhere, then you will need to change that.
 
 ```
 // Path to the local directory containing the chaincode project under $GOPATH
 var testChaincodePath = "github.com/chaincode_example02/";
 ```
 
-**Note:** You will need to run `npm install` the first time you run the sdk tests, in order to install all of the dependencies. Set the `DEPLOY_MODE` environment variable to `net` and run the chain-tests as follows:
+**Note:** You will need to run `npm install` the first time you run the sdk
+tests, in order to install all of the dependencies. Set the `DEPLOY_MODE`
+environment variable to `net` and run the chain-tests as follows:
 
 ```
 cd $GOPATH/src/github.com/hyperledger/fabric/sdk/node
@@ -183,7 +224,8 @@ node test/unit/chain-tests.js | node_modules/.bin/tap-spec
 
 ### Enabling TLS
 
-If you wish to configure TLS with the Membership Services server, the following steps are required:
+If you wish to configure TLS with the Membership Services server, the following
+steps are required:
 
 - Modify `$GOPATH/src/github.com/hyperledger/fabric/membersrvc/membersrvc.yaml` as follows:
 
@@ -196,7 +238,8 @@ server:
             file: "/var/hyperledger/production/.membersrvc/tlsca.priv"
 ```
 
-To specify to the Membership Services (TLS) Certificate Authority (TLSCA) what X.509 v3 Certificate (with a corresponding Private Key) to use:
+To specify to the Membership Services (TLS) Certificate Authority (TLSCA) what
+X.509 v3 Certificate (with a corresponding Private Key) to use:
 
 - Modify `$GOPATH/src/github.com/hyperledger/fabric/peer/core.yaml` as follows:
 
@@ -209,39 +252,63 @@ peer:
                 file: "/var/hyperledger/production/.membersrvc/tlsca.cert"
 ```
 
-To configure the peer to connect to the Membership Services server over TLS (otherwise, the connection will fail).
+To configure the peer to connect to the Membership Services server over TLS
+(otherwise, the connection will fail).
 
-- Bootstrap your Membership Services and the peer. This is needed in order to have the file *tlsca.cert* generated by the member services.
+- Bootstrap your Membership Services and the peer. This is needed in order to
+have the file *tlsca.cert* generated by the member services.
 
-- Copy `/var/hyperledger/production/.membersrvc/tlsca.cert` to `$GOPATH/src/github.com/hyperledger/fabric/sdk/node`.
+- Copy `/var/hyperledger/production/.membersrvc/tlsca.cert` to
+`$GOPATH/src/github.com/hyperledger/fabric/sdk/node`.
 
-*Note:* If you cleanup the folder `/var/hyperledger/production` then don't forget to copy again the *tlsca.cert* file as described above.
+*Note:* If you cleanup the folder `/var/hyperledger/production` then don't
+forget to copy again the *tlsca.cert* file as described above.
 
 ## Running Unit Tests
-HLC includes a set of unit tests implemented with the [tape framework](https://github.com/substack/tape). The [unit test script](https://github.com/hyperledger/fabric/blob/master/sdk/node/bin/run-unit-tests.sh) builds and runs both the membership service server and the peer node for you, therefore you do not have to start those manually.
+HFC includes a set of unit tests implemented with the
+[tape framework](https://github.com/substack/tape). The
+[unit test script](https://github.com/hyperledger/fabric/blob/master/sdk/node/bin/run-unit-tests.sh)
+builds and runs both the membership service server and the peer node for you,
+therefore you do not have to start those manually.
 
 ### Running the SDK unit tests
-HFC includes a set of unit tests implemented with the [tape framework](https://github.com/substack/tape). To run the unit tests, execute the following commands:
+HFC includes a set of unit tests implemented with the
+[tape framework](https://github.com/substack/tape). To run the unit tests,
+execute the following commands:
 
     cd $GOPATH/src/github.com/hyperledger/fabric
     make node-sdk-unit-tests
 
-The following are brief descriptions of each of the unit tests that are being run.
+The following are brief descriptions of each of the unit tests that are being
+run.
 
 #### registrar
-The [registrar.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/registrar.js) test case exercises registering users with Membership Services. It also tests registering a designated registrar user which can then register additional users.
+The [registrar.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/registrar.js)
+test case exercises registering users with Membership Services. It also tests
+registering a designated registrar user which can then register additional users.
 
 #### chain-tests
-The [chain-tests.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/chain-tests.js) test case exercises the [chaincode_example02.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/chaincode_example02) chaincode when it has been deployed in both development mode and network mode.
+The [chain-tests.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/chain-tests.js)
+test case exercises the [chaincode_example02.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/chaincode_example02)
+chaincode when it has been deployed in both development mode and network mode.
 
 #### asset-mgmt
-The [asset-mgmt.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/asset-mgmt.js) test case exercises the [asset_management.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/asset_management) chaincode when it has been deployed in both development mode and network mode.
+The [asset-mgmt.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/asset-mgmt.js)
+test case exercises the [asset_management.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/asset_management)
+chaincode when it has been deployed in both development mode and network mode.
 
 #### asset-mgmt-with-roles
-The [asset-mgmt-with-roles.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/asset-mgmt-with-roles.js) test case exercises the [asset_management_with_roles.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/asset_management_with_roles) chaincode when it has been deployed in both development mode and network mode.
+The [asset-mgmt-with-roles.js](https://github.com/hyperledger/fabric/blob/master/sdk/node/test/unit/asset-mgmt-with-roles.js)
+test case exercises the [asset_management_with_roles.go](https://github.com/hyperledger/fabric/tree/master/examples/chaincode/go/asset_management_with_roles)
+chaincode when it has been deployed in both development mode and network mode.
 
 #### Troublingshooting
-If you see errors stating that the client has already been registered/enrolled, keep in mind that you can perform the enrollment process only once, as the enrollmentSecret is a one-time-use password. You will see these errors if you have performed a user registration/enrollment and subsequently deleted the cryptographic tokens stored on the client side. The next time you try to enroll, errors similar to the ones below will be seen.
+If you see errors stating that the client has already been registered/enrolled,
+keep in mind that you can perform the enrollment process only once, as the
+enrollmentSecret is a one-time-use password. You will see these errors if you
+have performed a user registration/enrollment and subsequently deleted the
+cryptographic tokens stored on the client side. The next time you try to enroll,
+errors similar to the ones below will be seen.
 
    ```
    Error: identity or token do not match
@@ -250,4 +317,8 @@ If you see errors stating that the client has already been registered/enrolled,
    Error: user is already registered
    ```
 
-To address this, remove any stored cryptographic material from the CA server by following the instructions [here](https://github.com/hyperledger/fabric/blob/master/docs/Setup/Chaincode-setup.md#removing-temporary-files-when-security-is-enabled). You will also need to remove any of the cryptographic tokens stored on the client side by deleting the KeyValStore directory. That directory is configurable and is set to `/tmp/keyValStore` within the unit tests.
+To address this, remove any stored cryptographic material from the CA server by
+following the instructions [here](https://github.com/hyperledger/fabric/blob/master/docs/Setup/Chaincode-setup.md#removing-temporary-files-when-security-is-enabled).
+You will also need to remove any of the cryptographic tokens stored on the
+client side by deleting the KeyValStore directory. That directory is
+configurable and is set to `/tmp/keyValStore` within the unit tests.