more typos

README.md

@@ -33,14 +33,15 @@ BlockBench comes with both [macro benchmark workloads](src/macro) for evaluating
 ### C++ libraries
 * [restclient-cpp](https://github.com/mrtazz/restclient-cpp)
 
-Note: we patched this library to include the "Expect: " header in POST requests, which considerably improves the speed for
-processing RPC request at Parity. 
-  + The patch file is include in [benchmark/parity](benchmark/parity) folder.
-  + To patch: go to top-level directory of restclient-cpp, then:
+  Note: we patched this library to include the "Expect: " header in POST requests, which considerably improves the speed for
+  processing RPC request at Parity. 
+
+    + The patch file is include in [benchmark/parity](benchmark/parity) folder.
+    + To patch: go to top-level directory of restclient-cpp, then:
 
         `patch -p4 < $BLOCK_BENCH_HOME/benchmark/parity/patch_restclient`
 
-  + The installation can then proceed as normal. 
+    + The installation can then proceed as normal. 
 
 * [libcurl](https://curl.haxx.se/libcurl/)
 

src/README.md

@@ -1,5 +1,5 @@
-This directory contains implementation of dirvers for both **Micro-** and **Macro-** benchmark workloads.
+This directory contains implementation of divers for both **Micro-** and **Macro-** benchmark workloads.
 
-* [Micro-benchmark](micro/README.md) contains workload of DoNothing, IOHeavy, CPUHeavy and Analytic.
+* [Micro-benchmark](micro/README.md) contains workload of DoNothing, IOHeavy, CPUHeavy and Analytics.
 
 * [Macro-benchmark](macro/README.md) contains workload of YCSB(KVStore) and SmallBank.

src/macro/README.md

@@ -3,7 +3,7 @@ This directory contains the drivers for macro benchmark workload - YCSB and Smal
 
 The DoNothing micro benchmark workload which is targeted to test the consensus layer is also integrated into the ycsbc-based driver.
 
-The driver in `kvstore` direcotry provides the following workloads:
+The driver in `kvstore` directory provides the following workloads:
 
 * KVStore: for Ethereum, Parity and Hyperledger
 
@@ -12,7 +12,7 @@ The driver in `kvstore` direcotry provides the following workloads:
   ./driver -db parity -threads 1 -P workloads/workloada.spec -txrate 5 -endpoint localhost:8545 -wl ycsb -wt 20
   ```
 
-* SmallBank: for Ethereum and Pairty
+* SmallBank: for Ethereum and Parity 
 
   Usage example:
   ```
@@ -26,4 +26,4 @@ The driver in `kvstore` direcotry provides the following workloads:
   ./driver -db hyperledger -threads 1 -P workloads/workloada.spec -txrate 5 -endpoint localhost:7050/chaincode -wl donothing
   ```
 
-The `smallbank` directory contains the driver of SmallBank workload for HyperLedger
+The `smallbank` directory contains the driver of SmallBank workload for Hyperledger

src/micro/README.md

@@ -16,7 +16,7 @@ We provide several workloads to stress the layers in order to understand their i
   ./driver -db parity -threads 1 -P workloads/workloada.spec -txrate 5 -endpoint localhost:8545 -wl donothing -wt 20
   ```
 
-* Data model layer - IOHeavy & Analytic
+* Data model layer - IOHeavy & Analytics
 
   * [IOHeavy](ioheavy/README.md) workload description.
   * [Analytic](analytic/README.md) workload description.

src/micro/analytic/README.md

@@ -9,9 +9,9 @@ extracting statistics from the blockchain data:
 
 * Q1: Compute the total transaction values committed between block i and block j.
 
-* Q2: Compute the largest transaction value involing a given account between block i and block j.
+* Q2: Compute the largest transaction value involving a given account between block i and block j.
 
-For Ethereum and Pairty the queries are implemented using JSON-RPC. Ethereum and Pairty share the same driver.
+For Ethereum and Parity the queries are implemented using JSON-RPC. Ethereum and Parity share the same driver.
 For Hyperledger we develop our own chaincode to implement the similar logic.
 To see more details, please refer to the README file in each individual directory for each system.
 

src/micro/analytic/hyperledger/README.md

@@ -1,7 +1,7 @@
 # Experiment Setup
 
-Need to deploy the analytic chaincode & populate the blockchain system using some pre-generated transactions before the analytical queries.
-The source code of analytic chaincode is in `blockbench/benchmark/contracts/hyperledger/go/analytic/` directory.
+Need to deploy the analytics chaincode & populate the blockchain system using some pre-generated transactions before the analytical queries.
+The source code of analytics chaincode is in `blockbench/benchmark/contracts/hyperledger/go/analytic/` directory.
 
 1. use `node deploy.js account_number` to initialize the chaincode into Hyperledger. `account_number` indicates how many initial accounts
 are created in the state of this chaincode.
@@ -13,4 +13,4 @@ using random accounts.
 
 * Q1: `node bench_q1.js start_block end_block` queries Q1 from block `start_block` to block `end_block`.
 
-* Q2: `node bench_q2.js account start_block end_block` queries Q2 for account `account` from block `start_block` to block `end_block`. `account` is an interger.
+* Q2: `node bench_q2.js account start_block end_block` queries Q2 for account `account` from block `start_block` to block `end_block`. `account` is an integer.

src/micro/cpuheavy/ethereum/README.md

@@ -1,3 +1,3 @@
 # Run
-* use `node deploy.js array_size` to deploy the sorting smart contract to blockchain, and also issue a sort request. It will report the latency into stdout. 
+* use `node deploy.js array_size` to deploy the sorting smart contract to blockchain, and also issue a sort request. It will report the latency into `stdout`. 
  `array_size` is the size of the array to sort.

src/micro/ioheavy/ethereum/README.md

@@ -4,7 +4,7 @@ Need to deploy the ioheavy smart contract first.
 The source code of ioheavy smart contract source code in Solidity is `blockbench/benchmark/contracts/ethereum/ioheavy.sol` as a reference.
 
 * use `node deploy.js` to deploy the smart contract into blockchain(ethereum/parity). It will output the deployed smart contract address
-into stdout.
+into `stdout`.
 
 # Run