FAB-406 node-sdk doc fixes

fixed broken links and formatted node-sdk documents. Copied new images
into images folder in both docs and nodeSDK folder to make images working
from both github and readthedocs. This is a duplicate effort while
submitting changes on these images.

https://jira.hyperledger.org/browse/FAB-406

Change-Id: Ia62ffcc602617574f9e685cfa3b44a3873877a84
Signed-off-by: rameshthoomu <[email protected]>

Author: rameshthoomu

docs/images/standalone-app-developer.png

@@ -1,33 +1,34 @@
 # Setting up the Full Hyperledger fabric Developer's Environment
 
-1. See [Setting Up The Development Environment](../dev-setup/devenv.md) to set up your development environment.
+ 1. See [Setting Up The Development Environment](../dev-setup/devenv.md) to set up your development environment.
 
-2. Issue the following commands to build the Hyperledger fabric client (HFC) Node.js SDK including the API reference documentation  
+ 2. Issue the following commands to build the Hyperledger fabric client (HFC) Node.js SDK including the API reference documentation
 
-   ```
+```
    cd /opt/gopath/src/github.com/hyperledger/fabric/sdk/node
    make all
-   ```
-   
-3. Issue the following command where your Node.js application is located if you wish to use the `require("hfc")`, this will install the HFC locally.  
-
-   ```
-   npm install /opt/gopath/src/github.com/hyperledger/fabric/sdk/node
-   ```
-   
+```
+ 3. Issue the following command where your Node.js application is located if you wish to use the `require("hfc")`, this will install the HFC locally.
+
+```
+  npm install /opt/gopath/src/github.com/hyperledger/fabric/sdk/node
+```
+
    Or use point directly to the HFC directly by using the following require in your code:
-   ```javascript
+
+```javascript
    require("/opt/gopath/src/github.com/hyperledger/fabric/sdk/node");
-   ```
-   
-      
-4. To see the API reference documentation which is built in step 2:
-   ```
+```
+
+ 4. To see the API reference documentation which is built in step 2:
+
+```
    cd /opt/gopath/src/github.com/hyperledger/fabric/sdk/node/doc
-   ```
+```
 
    The [Self Contained Node.js Environment](node-sdk-self-contained.md) will have the reference documentation already built and may be accessed by:
-   ```
+
+```
    docker exec -it nodesdk /bin/bash
    cd /opt/gopath/src/github.com/hyperledger/fabric/sdk/node/doc
-   ```
+```

docs/images/web-app-developer.png

@@ -2,18 +2,18 @@
 
 Hyperledger fabric supports two types of applications:
 
-   * A standalone application that interacts directly with a blockchain.  
+   * A standalone application that interacts directly with a blockchain.
      See the [Standalone Application](#standaloneApp) section.
 
-   * A web application that interacts with a blockchain on behalf of its web application users.  
+   * A web application that interacts with a blockchain on behalf of its web application users.
      See the [Web Application](#webApp) section.
 
 <a name="standaloneApp"></a>
 ## Standalone Application
 
 The following diagram provides an overview of the major components of Hyperledger fabric for the standalone application developer.
 
-![Reference architecture](../images/standalone-app-developer.png)
+<img src="../images/standalone-app-developer.png" width="900" height="456">
 
 In the diagram above, the blue boxes are Hyperledger fabric components and the green boxes are application developer components.  Each outer box represents a separate process.
 
@@ -24,14 +24,16 @@ The **Standalone Application** may be developed in Node.js by using the Hyperled
 
 The **SDK** interacts with a **Peer** process.  If the Peer process fails, the Node.js Client SDK can fail-over to another Peer as shown by the dotted line from the Node.js Client SDK to another Peer.
 
-This interaction with the Peer consists of submitting transactions to the blockchain.  There are three types of transactions:  
- * deploy - to deploy developer's chaincode as depicted by the green **CC1** boxes in the diagram;    
- * invoke - to execute a chaincode function which changes the state of the *blockchain database*;  
+This interaction with the Peer consists of submitting transactions to the blockchain.  There are three types of transactions:
+
+ * deploy - to deploy developer's chaincode as depicted by the green **CC1** boxes in the diagram;
+ * invoke - to execute a chaincode function which changes the state of the *blockchain database*;
  * query - to execute a chaincode function which may return state information related to the *blockchain database*.
 
 The **SDK** also interacts with a **Membership Services** process.  In fact, if security is enabled in the Peer (strongly recommended), the Node.js client SDK must interact with Membership Services first in order to retrieve *credentials* which are then used to interact with the Peer.  These *credentials* consist of certificates as described in [Membership Services](membership-services.md).
 
 The interaction with the Membership Services consists of:
+
  * register - to indicate a new user to the blockchain
  * enroll - to get access to the blockchain
 
@@ -41,14 +43,14 @@ The interaction with the Membership Services consists of:
 The following diagram provides an overview of the major components of Hyperledger fabric for the web application developer.
 
 At a high-level, you can think of the Block Chain as a database with which the web application interacts; therefore, it is similar to the following topology.
+
 ```
 browser --> web tier --> database tier
-```
 
+```
 
-![Reference architecture](../images/web-app-developer.png)
+<img src="../images/web-app-developer.png" width="900" height="456">
 
 In the diagram above, the blue boxes are Hyperledger fabric components and the green boxes are application developer components.  Each outer box represents a separate process.
 
 The browser interacts with the developer's Node.js web application using the Hyperledger fabric's Node.js client SDK.  The SDK handles all interactions with other Hyperledger fabric components in the same manor as described in the [SDK interactions](#sdk-interactions) section of [Standalone Application](#standaloneApp).
-

docs/nodeSDK/app-developer-env-setup.md

@@ -4,11 +4,12 @@ The Hyperledger fabric Client (HFC) SDK provides a powerful and easy to use API
 
 ## Installing only the SDK
 
-If you are an experienced node.js developer and already have a blockchain environment set up and running elsewhere, you can set up a client-only environment to run the node.js client by installing the HFC node module as shown below.  This assumes npm version 2.11.3 and node.js version 0.12.7 are already installed.    
- 
+If you are an experienced node.js developer and already have a blockchain environment set up and running elsewhere, you can set up a client-only environment to run the node.js client by installing the HFC node module as shown below.  This assumes npm version 2.11.3 and node.js version 0.12.7 are already installed.
+
 * To install the latest HFC module of Hyperledger fabric
+
 ```
-npm install hfc
+  npm install hfc
 ```
 
 ### Terminology
@@ -49,7 +50,8 @@ The following is a high-level description of the HFC objects (classes and interf
 
 HFC was designed to support two pluggable components:
 
-1. Pluggable `KeyValStore` key value store which is used to retrieve and store keys associated with a member. The key value store is used to store sensitive private keys, so care must be taken to properly protect access.  
+1. Pluggable `KeyValStore` key value store which is used to retrieve and store keys associated with a member. The key value store is used to store sensitive private keys, so care must be taken to properly protect access.
+
   **IMPORTANT NOTE**: The default KeyValStore is file-based.  If multiple instances of a web application run in a cluster, you must provide an implementation of the KeyValStore which is used by all members of the cluster.
 
 2. Pluggable `MemberServices` which is used to register and enroll members. Member services enables hyperledger to be a permissioned blockchain, providing security services such as anonymity, unlinkability of transactions, and confidentiality
@@ -63,40 +65,40 @@ up the chaincode project outside of your Hyperledger fabric source tree to inclu
 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)
+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/
-cd $GOPATH/src/github.com/chaincode_example02
-curl GET https://raw.githubusercontent.com/hyperledger/fabric/master/examples/chaincode/go/chaincode_example02/chaincode_example02.go > chaincode_example02.go
+  mkdir -p $GOPATH/src/github.com/chaincode_example02/
+  cd $GOPATH/src/github.com/chaincode_example02
+  curl GET https://raw.githubusercontent.com/hyperledger/fabric/master/examples/chaincode/go/chaincode_example02/chaincode_example02.go > chaincode_example02.go
 ```
 
 After you have placed your chaincode project under the `$GOPATH/src`, you will need to vendor the dependencies. From the directory containing your chaincode source, run the following commands:
 
 ```
-go get -u github.com/kardianos/govendor
-cd $GOPATH/src/github.com/chaincode_example02
-govendor init
-govendor fetch github.com/hyperledger/fabric
+  go get -u github.com/kardianos/govendor
+  cd $GOPATH/src/github.com/chaincode_example02
+  govendor init
+  govendor fetch github.com/hyperledger/fabric
 ```
 
 Now, execute `go build` to verify that all of the chaincode dependencies are
 present.
 
 ```
-go build
+  go build
 ```
 
 #### 'dev' mode
 For deploying chaincode in development mode see [Writing, Building, and Running Chaincode in a Development Environment](../Setup/Chaincode-setup.md). 
 The chaincode must be running and connected to the peer before issuing the `deploy()` from the Node.js application. The hfc `chain` object must be set to dev mode.
+
 ```javascript
 chain.setDevMode(true);
 ```
 The deploy request must include the `chaincodeName` that the chaincode registered with the peer. The built-in chaincode example checks an environment variable `CORE_CHAINCODE_ID_NAME=mycc` when it starts.
+
 ```json
    var deployRequest = {
        chaincodeName: 'mycc',
@@ -112,11 +114,11 @@ If you wish to configure TLS with the Membership Services server, the following
 - Modify `$GOPATH/src/github.com/hyperledger/fabric/membersrvc/membersrvc.yaml` as follows:
 
 ```
-server:
-     tls:
-        cert:
+  server:
+      tls:
+         cert:
             file: "/var/hyperledger/production/.membersrvc/tlsca.cert"
-        key:
+         key:
             file: "/var/hyperledger/production/.membersrvc/tlsca.priv"
 ```
 
@@ -125,12 +127,12 @@ To specify to the Membership Services (TLS) Certificate Authority (TLSCA) what X
 - Modify `$GOPATH/src/github.com/hyperledger/fabric/peer/core.yaml` as follows:
 
 ```
-peer:
-    pki:
-        tls:
-            enabled: true
-            rootcert:
-                file: "/var/hyperledger/production/.membersrvc/tlsca.cert"
+   peer:
+      pki:
+          tls:
+             enabled: true
+             rootcert:
+                 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).
@@ -140,19 +142,18 @@ To configure the peer to connect to the Membership Services server over TLS (oth
 - 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.
-   
-
-
-
 
 ### 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.
 
-   ```
+```
    Error: identity or token do not match
-   ```
-   ```
+
+```
+
+```
    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.