[FAB-9517] Correct Misspelling in Document

Correct misspellings in the document.
Checked by Code Spell Checker for Visual Studio Code.
British spelling remains.

Change-Id: I0bfe3f170dc872ca711307955e41eb4b706c6e62
Signed-off-by: Yuta Namiki <[email protected]>

docs/source/CONTRIBUTING.rst

@@ -193,7 +193,7 @@ What makes a good change request?
    too. If you send a 1,000 or 2,000 LOC change, how long do you think
    it takes to review all of that code? Keep your changes to < 200-300
    LOC, if possible. If you have a larger change, decompose it into
-   multiple independent changess. If you are adding a bunch of new
+   multiple independent changes. If you are adding a bunch of new
    functions to fulfill the requirements of a new capability, add them
    separately with their tests, and then write the code that uses them
    to deliver the capability. Of course, there are always exceptions. If

docs/source/Fabric-FAQ.rst

@@ -50,7 +50,7 @@ included in the submitted transaction,  versus just output data. Therefore,
 the input data can be private to the endorsers only.
 If you do not want the orderers to see chaincode output, then you can hash or
 encrypt the data before calling chaincode. If you hash the data then you will
-need to provide a meansto share the source data. If you encrypt the data then
+need to provide a means to share the source data. If you encrypt the data then
 you will need to provide a means to share the decryption keys.
 
 Application-side Programming Model

docs/source/commands/peerchaincode.md

@@ -57,7 +57,7 @@ flags are
 
 * `-o` or `--orderer <string>`
 
-  Ordering service endpoint specifed as `<hostname or IP address>:<port>`
+  Ordering service endpoint specified as `<hostname or IP address>:<port>`
 
 * `--ordererTLSHostnameOverride <string>`
 

docs/source/commands/peernode.md

@@ -42,7 +42,7 @@ The `peer node start` command has the following command specific flag:
 * `--peer-chaincodedev`
 
   starts peer node in chaincode development mode. Normally chaincode containers are started
-  and maintained by peer. However in devlopment mode, chaincode is built and started by the user.
+  and maintained by peer. However in development mode, chaincode is built and started by the user.
   This mode is useful during chaincode development phase for iterative development.
   See more information on development mode in the [chaincode tutorial](../chaincode4ade.html).
 

docs/source/config_update.md

@@ -794,7 +794,7 @@ pre-production environments with weak consortium `ChannelCreation` policies.
 mod_policy for the Application group of new channels for the consortium it is defined in.
 The signature set attached to the channel creation request will be checked against
 the instantiation of this policy in the new channel to ensure that the channel
-creation is authorized. Note that this config vzlue is only set in the orderer
+creation is authorized. Note that this config value is only set in the orderer
 system channel.
 
   ```

docs/source/identity/identity.md

@@ -222,7 +222,7 @@ it is inherently not capable of providing SSL certificates for general/automatic
 in browsers. However, because **some** CA must be used to manage identity
 (even in a test environment), fabric-ca can be used to provide and manage
 certificates. It is also possible -- and fully appropriate -- to use a
-public/commerical root or intermediate CA to provide identification.
+public/commercial root or intermediate CA to provide identification.
 
 If you're interested, you can read a lot more about fabric-ca
 [in the CA documentation section](http://hyperledger-fabric-ca.readthedocs.io/).

docs/source/ledger/ledger.md

@@ -224,7 +224,7 @@ In the above example, we can see the following fields:
 
 * **Signature**
 
-  This section, illustrated by S4, contains a cryptgraphic signature, created by
+  This section, illustrated by S4, contains a cryptographic signature, created by
   the client application. This field is used to check that the transaction
   details have not been tampered with, as it requires the application's private
   key to generate it.
@@ -282,7 +282,7 @@ between a network node and a CouchDB instance. All of this is invisible to
 chaincode. See [CouchDB as the StateDatabase](./couchdb_as_state_database.html)
 for more information on CouchDB.
 
-In LeveDB and CouchDB, we see an important aspect of Hyperledger Fabric -- it is
+In LevelDB and CouchDB, we see an important aspect of Hyperledger Fabric -- it is
 *pluggable*. The world state database could be a relational data store, or a
 graph store, or a temporal database.  This provides great flexibility in the
 types of ledger states that can be efficiently accessed, allowing Hyperledger
@@ -323,7 +323,7 @@ headers and hashes.  If you're interested in the precise details of these, you
 will find a dedicated reference topic elsewhere in the documentation. It gives
 you a fully worked example of an entire block with its transactions in glorious
 detail -- but for now, you have achieved a solid conceptual understanding of a
-Hypterledger Fabric ledger. Well done!
+Hyperledger Fabric ledger. Well done!
 
 ## More information
 

docs/source/peers/peers.md

@@ -92,7 +92,7 @@ many chaincodes which access it. In this example, we can see that peer P1
 hosts ledgers L1 and L2. L1 is accessed by chaincodes S1 and S2, whereas
 L2 is accessed by S3 and S1. We can see that S1 can access both L1 and L2.*
 
-We'll see a little later why the concept of **channels** in Hyperldeger Fabric
+We'll see a little later why the concept of **channels** in Hyperledger Fabric
 is important when hosting multiple ledgers or multiple chaincodes on a
 peer.