Fix natural laguague issues

Author: electrocucaracha

bench/README.md

@@ -14,7 +14,7 @@ Run (consider to use virtual environment):
 pip3 install -r bench/requirements.txt
 ```
 
-**Optional** If you need to monitor server side metrics please install [Prometheus](https://prometheus.io/docs/prometheus/latest/getting_started/).
+**Optional** If you need to monitor server-side metrics please install [Prometheus](https://prometheus.io/docs/prometheus/latest/getting_started/).
 
 ## Preparation
 
@@ -59,7 +59,7 @@ Here the following (**optional**) inputs are considered:
 prometheus --config.file=bench/prometheus.yml
 ```
 
-And open `http://localhost:9090/` to query and monitor the server side metrics.
+And open `http://localhost:9090/` to query and monitor the server-side metrics.
 
 ### Headless
 

dcl-ui/ansible/README.md

@@ -1,6 +1,6 @@
 # Deploying DC Ledger UI
 
-1. Run `dclcli` rest service on the client machine. See `deployment/ansible` folder in the `dc-ledger` repo.
+1. Run `dclcli` rest service on the client machine. See `deployment/ansible` folder in the `dc-ledger` repository.
 2. Build the app by running `ng build --prod`.
 3. Execute playbooks in the following order: `content`, `nginx`, `config`, `reload`.
 4. Use certbot to obtain a certificate and don't forger to open `443` port.

docs/advanced/running-genesis-node.md

@@ -75,7 +75,7 @@ must have a unique chain ID.
         * `sudo ufw allow 26656/tcp`
         * `sudo ufw allow 26657/tcp`
     * Edit `dcld.service`
-        * Replace `ubuntu` with a user name you want to start service on behalf
+        * Replace `ubuntu` with a username you want to start service on behalf
     * Copy service configuration.
         * `cp dcld.service /etc/systemd/system/`
     * Make your node public:

docs/advanced/running-observer-node.md

@@ -68,7 +68,7 @@ and contains the genesis and persistent_peers files.
         * `sudo ufw allow 26656/tcp`
         * `sudo ufw allow 26657/tcp`
     * Edit `dcld.service` (Only needed for Ubuntu).
-        * Replace `ubuntu` with a user name you want to start service on behalf
+        * Replace `ubuntu` with a username you want to start service on behalf
     * Copy service configuration. (Only needed for Ubuntu).
         * `cp dcld.service /etc/systemd/system/`
 

docs/advanced/running-validator-node.md

@@ -105,7 +105,7 @@ and contains the genesis and persistent_peers files.
         * `sudo ufw allow 26656/tcp`
         * `sudo ufw allow 26657/tcp`
     * Edit `dcld.service`
-        * Replace `ubuntu` with a user name you want to start service on behalf
+        * Replace `ubuntu` with a username you want to start service on behalf
     * Copy service configuration.
         * `cp dcld.service /etc/systemd/system/`
 

docs/design/benchmarking.md

@@ -14,16 +14,16 @@
    - simulate deployment as close to production as possible
 
 
-## Client Side Metrics
+## Client-side Metrics
 
 *   `response time` (percentiles): the time between client's initial request and the last byte of a validator response
 *   `requests per second (RPS)`: number of requests per second
 *   `transactions per second (TPS)`: number of write requests (txns) per second
-    *   **Note** to measure that on a client side write requests should use `broadcast_tx_commit` requests
+    *   **Note** to measure that on a client-side write requests should use `broadcast_tx_commit` requests
 *   `number of clients`: number of concurrent clients that ledger serves
 *   (optional) `throughtput` (in/out): number of KB per second. Marked as optional since we don't expect much in/out data due to relatively small txns payloads.
 
-## Server Side Metrics
+## Server-side Metrics
 
 ### Tendermint metrics
 
@@ -43,7 +43,7 @@ The following ones makes sense to track:
 
 ### Cosmos SDK metrics
 
-Starting from `v0.40.0` Cosmos SDK provides [telemetry](https://docs.cosmos.network/master/core/telemetry.html) package as a server side support for application performance and behavior explorations.
+Starting from `v0.40.0` Cosmos SDK provides [telemetry](https://docs.cosmos.network/master/core/telemetry.html) package as a server-side support for application performance and behavior explorations.
 
 The following [metrics](https://docs.cosmos.network/master/core/telemetry.html#supported-metrics) make sense to track:
 

docs/monitoring.md

@@ -5,7 +5,7 @@
 As long as DCLedger is built on top of Cosmos SDK and Tendermint their monitoring abilities can be considered for DCLedger as well.
 
 *   Starting from `v0.21.0` Tendermint provides Prometheus compatible [metrics](https://docs.tendermint.com/master/nodes/metrics.html#metrics).
-*   Starting from `v0.40.0` Cosmos SDK provides [telemetry](https://docs.cosmos.network/master/core/telemetry.html) package as a server side support for application performance and behavior explorations.
+*   Starting from `v0.40.0` Cosmos SDK provides [telemetry](https://docs.cosmos.network/master/core/telemetry.html) package as a server-side support for application performance and behavior explorations.
 
 ## Installation & Configuration
 
@@ -31,4 +31,4 @@ Run
 prometheus --config.file=prometheus.yml
 ```
 
-And open `http://localhost:9090/` to query and monitor the server side metrics.
+And open `http://localhost:9090/` to query and monitor the server-side metrics.

docs/transactions.md

@@ -177,7 +177,7 @@ Not all fields can be edited (see `EDIT_MODEL`).
   - productName: `string` -  model name
   - productLabel: `string` -  model description (string or path to file containing data)
   - partNumber: `string` -  stock keeping unit
-  - commissioningCustomFlow: `optional(uint8)` - A value of 1 indicates that user interaction with the device (pressing a button, for example) is required before commissioning can take place. When CommissioningCustomflow is set to a value of 2, the commissioner SHOULD attempt to obtain a URL which MAY be used to provide an end-user with the necessary details for how to configure the product for initial commissioning
+  - commissioningCustomFlow: `optional(uint8)` - A value of 1 indicates that user interaction with the device (pressing a button, for example) is required before commissioning can take place. When CommissioningCustomflow is set to a value of 2, the commissioner SHOULD attempt to obtain a URL which MAY be used to provide an end user with the necessary details for how to configure the product for initial commissioning
   - commissioningCustomFlowURL: `optional(string)` - commissioningCustomFlowURL SHALL identify a vendor specific commissioning URL for the device model when the commissioningCustomFlow field is set to '2'
   - commissioningModeInitialStepsHint: `optional(uint32)` - commissioningModeInitialStepsHint SHALL identify a hint for the steps that can be used to put into commissioning mode a device that has not yet been commissioned. This field is a bitmap with values defined in the Pairing Hint Table. For example, a value of 1 (bit 0 is set) indicates that a device that has not yet been commissioned will enter Commissioning Mode upon a power cycle.
   - commissioningModeInitialStepsInstruction: `optional(string)` - commissioningModeInitialStepsInstruction SHALL contain text which relates to specific values of CommissioningModeInitialStepsHint. Certain values of CommissioningModeInitialStepsHint, as defined in the Pairing Hint Table, indicate a Pairing Instruction (PI) dependency, and for these values the commissioningModeInitialStepsInstruction SHALL be set
@@ -769,7 +769,7 @@ The revocation is not applied until sufficient number of Trustees approve it.
 #### GET_X509_CERT
 **Status: Implemented**
 
-Gets a certificate (either root, intermediate or leaf) by the given subject and subject key id attributes.
+Gets a certificate (either root, intermediate or leaf) by the given subject and subject key ID attributes.
 Revoked certificates are not returned. 
 Use `GET_ALL_REVOKED_X509_CERTS` to get a list of all revoked certificates. 
 
@@ -813,7 +813,7 @@ Revoked certificates are not returned.
 #### GET_PROPOSED_X509_ROOT_CERT
 **Status: Implemented**
 
-Gets a proposed but not approved root certificate with the given subject and subject key id attributes.
+Gets a proposed but not approved root certificate with the given subject and subject key ID attributes.
 
 - Parameters:
   - subject: `string`  - certificates's `Subject`
@@ -826,7 +826,7 @@ Gets a proposed but not approved root certificate with the given subject and sub
 #### GET_REVOKED_CERT
 **Status: Implemented**
 
-Gets a revoked certificate (either root, intermediate or leaf) by the given subject and subject key id attributes.
+Gets a revoked certificate (either root, intermediate or leaf) by the given subject and subject key ID attributes.
 
 - Parameters:
   - subject: `string`  - certificates's `Subject`
@@ -949,7 +949,7 @@ will be in a pending state until sufficient number of approvals is received.
 - Parameters:
     - address: `string` - account address; Bench32 encoded
     - pub_key: `string` - account's Protobuf JSON encoded public key
-    - vid: `optional(uint16)` - vendor id (only needed for vendor role)
+    - vid: `optional(uint16)` - vendor ID (only needed for vendor role)
     - roles: `array<string>` - the list of roles, comma-separated, assigning to the account. Supported roles: `Vendor`, `TestHouse`, `CertificationCenter`, `Trustee`, `NodeAdmin`. 
     - info: `optional(string)` - information/notes for the proposal
     - time: `optional(int64)` - proposal time (number of nanoseconds elapsed since January 1, 1970 UTC). CLI uses the current time for that field.
@@ -1116,7 +1116,7 @@ Adds a new Validator node.
     - pubkey: `string` - The validator's Protobuf JSON encoded public key
     - moniker: `string` - The validator's human-readable name
     - identity: `optional(string)` - identity signature (ex. UPort or Keybase)
-    - website: `optional(string)` - The validator's website link
+    - website: `optional(string)` - The validator's site link
     - details: `optional(string)` - The validator's details
     - ip: `optional(string)` - The node's public IP
     - node-id: `optional(string)` - The node's ID
@@ -1167,7 +1167,7 @@ Updates the Validator node by the owner.
     - address: `string` - Bench32 encoded validator address or owner account
     - moniker: `string` - The validator's human-readable name
     - identity: `optional(string)` - identity signature (ex. UPort or Keybase)
-    - website: `optional(string)` - The validator's website link
+    - website: `optional(string)` - The validator's site link
     - details: `optional(string)` - The validator's details
     - ip: `optional(string)` - The node's public IP
     - node-id: `optional(string)` - The node's ID
@@ -1240,7 +1240,7 @@ Sign transaction by the given key.
     - `from` -  name or address of private key to use to sign.
     - `account-number` - (optional) the account number of the signing account.
     - `sequence` - (optional) the sequence number of the signing account.
-    - `chain-id` - (optional) chain id.
+    - `chain-id` - (optional) chain ID.
 - CLI command: 
     -   `dcld tx sign [path-to-txn-file] --from [address]`
 Note: if `account_number` and `sequence`  are not specified they will be fetched from the ledger automatically.