Merge pull request #2278 from BorisNaum/typos

Fixed typos

README.md

@@ -59,7 +59,7 @@ The project comes with several executables found in the `build/bin` directory.
 
 ### Generate the keys
 
-Each node requires two pairs of public&private keys, the one is called node's keypair, it's generated based on the secp256k1 curve for marking the node identity and signning the block, and the other is called node's blskeypair, it's based on the BLS_12_381 curve and is used for consensus verifing. These two pairs of public-private key need to be generated by the platonkey tool.
+Each node requires two pairs of public&private keys, the one is called node's keypair, it's generated based on the secp256k1 curve for marking the node identity and signning the block, and the other is called node's blskeypair, it's based on the BLS_12_381 curve and is used for consensus verifying. These two pairs of public-private key need to be generated by the platonkey tool.
 
 Switch to the directory where contains 'platonkey.exe'(Windows) or 'platonkey'(Ubuntu).
 Node's keypair(Ubuntu for example):

cmd/ctool/core/contractcmd.go

@@ -94,7 +94,7 @@ func DeployContract(abiFilePath string, codeFilePath string) error {
 
 	resp := parseResponse(r)
 
-	fmt.Printf("\ntrasaction hash: %s\n", resp.Result)
+	fmt.Printf("\ntransaction hash: %s\n", resp.Result)
 
 	// Get transaction receipt according to result
 	ch := make(chan string, 1)
@@ -238,7 +238,7 @@ func InvokeContract(contractAddr string, abiPath string, funcParams string, txTy
 		}
 		fmt.Printf("\n result: []\n")
 	} else {
-		fmt.Printf("\n trasaction hash: %s\n", resp.Result)
+		fmt.Printf("\n transaction hash: %s\n", resp.Result)
 	}
 	return nil
 }
@@ -266,7 +266,7 @@ func getContractByAddress(addr string) bool {
 		fmt.Printf("platon_getCode error ,error:%v", resp.Error.Message)
 		return false
 	}
-	//fmt.Printf("trasaction hash: %s\n", resp.Result)
+	//fmt.Printf("transaction hash: %s\n", resp.Result)
 
 	if resp.Result != "" && len(resp.Result) > 2 {
 		return true

cmd/ctool/core/utils_test.go

@@ -112,7 +112,7 @@ func TestHttpPostDeploy(t *testing.T) {
 	//if resp.Error.Code != 0 {
 	//	t.Fatalf("send transaction error ,error:%v", resp.Error.Message)
 	//}
-	//fmt.Printf("trasaction hash: %s\n", resp.Result)
+	//fmt.Printf("transaction hash: %s\n", resp.Result)
 	//
 	//// Get transaction receipt according to result
 	//ch := make(chan string, 1)

cmd/ctool/readme.md

@@ -17,7 +17,7 @@ eg： ./ctool deploy -abi "D:\\resource\\temp\\contractc.cpp.abi.json" -code "D:
 ```
 ./ctool invoke
 -addr     contract address (must)
--func     functon name and param (must)
+-func     function name and param (must)
 -abi      abi json file path (must)
 -type     transaction type ,default 2 (optional)
 
@@ -50,7 +50,7 @@ eg: ./ctool invoke -addr "lat1l3p70ayph8flwhx0ljxj86k9yt5kmetsusy5z0" -func "tra
 ##### 6.Prepare transaction stability test account
 ```
 ./ctool prepare
--pkfile      account private key file path,defalut "./test/privatekeys.txt" (optional)
+-pkfile      account private key file path,default "./test/privatekeys.txt" (optional)
 -size        the number of accounts,default 10 (optional)
 -value       transfer value (must)
 -config      config path (optional)
@@ -69,7 +69,7 @@ eg: ./ctool.exe pre -size 10 -pkfile "./test/privateKeys.txt" -value 0xDE0B6B3A7
 eg:  ./ctool.exe stab -pkfile "./test/privateKeys.txt" -times 10000 -interval 10
 ```
 
-note: If the command exits normally,the next time you can continue to run with the generated accounts and the command exits abnormally, you need to re-use the pre command to generate the test accounts.
+note: If the command exits normally,the next time you can continue to run with the generated accounts and the command exits abnormally, you need to reuse the pre command to generate the test accounts.
 
 ##### Config Description： The config parameter is not passed in the command, and the `config.json` file in the current directory is read by default.
 

tests/fuzzers/README.md

@@ -11,17 +11,17 @@ That command should generate a `rlp-fuzz.zip` in the `rlp/` directory. If you ar
 
 ```
 [user@work rlp]$ go-fuzz
-2019/11/26 13:36:54 workers: 6, corpus: 3 (3s ago), crashers: 0, restarts: 1/0, execs: 0 (0/sec), cover: 0, uptime: 3s
-2019/11/26 13:36:57 workers: 6, corpus: 3 (6s ago), crashers: 0, restarts: 1/0, execs: 0 (0/sec), cover: 1054, uptime: 6s
-2019/11/26 13:37:00 workers: 6, corpus: 3 (9s ago), crashers: 0, restarts: 1/8358, execs: 25074 (2786/sec), cover: 1054, uptime: 9s
-2019/11/26 13:37:03 workers: 6, corpus: 3 (12s ago), crashers: 0, restarts: 1/8497, execs: 50986 (4249/sec), cover: 1054, uptime: 12s
-2019/11/26 13:37:06 workers: 6, corpus: 3 (15s ago), crashers: 0, restarts: 1/9330, execs: 74640 (4976/sec), cover: 1054, uptime: 15s
-2019/11/26 13:37:09 workers: 6, corpus: 3 (18s ago), crashers: 0, restarts: 1/9948, execs: 99482 (5527/sec), cover: 1054, uptime: 18s
-2019/11/26 13:37:12 workers: 6, corpus: 3 (21s ago), crashers: 0, restarts: 1/9428, execs: 122568 (5836/sec), cover: 1054, uptime: 21s
-2019/11/26 13:37:15 workers: 6, corpus: 3 (24s ago), crashers: 0, restarts: 1/9676, execs: 145152 (6048/sec), cover: 1054, uptime: 24s
-2019/11/26 13:37:18 workers: 6, corpus: 3 (27s ago), crashers: 0, restarts: 1/9855, execs: 167538 (6205/sec), cover: 1054, uptime: 27s
-2019/11/26 13:37:21 workers: 6, corpus: 3 (30s ago), crashers: 0, restarts: 1/9645, execs: 192901 (6430/sec), cover: 1054, uptime: 30s
-2019/11/26 13:37:24 workers: 6, corpus: 3 (33s ago), crashers: 0, restarts: 1/9967, execs: 219294 (6645/sec), cover: 1054, uptime: 33s
+2019/11/26 13:36:54 workers: 6, corpus: 3 (3s ago), crashes: 0, restarts: 1/0, execs: 0 (0/sec), cover: 0, uptime: 3s
+2019/11/26 13:36:57 workers: 6, corpus: 3 (6s ago), crashes: 0, restarts: 1/0, execs: 0 (0/sec), cover: 1054, uptime: 6s
+2019/11/26 13:37:00 workers: 6, corpus: 3 (9s ago), crashes: 0, restarts: 1/8358, execs: 25074 (2786/sec), cover: 1054, uptime: 9s
+2019/11/26 13:37:03 workers: 6, corpus: 3 (12s ago), crashes: 0, restarts: 1/8497, execs: 50986 (4249/sec), cover: 1054, uptime: 12s
+2019/11/26 13:37:06 workers: 6, corpus: 3 (15s ago), crashes: 0, restarts: 1/9330, execs: 74640 (4976/sec), cover: 1054, uptime: 15s
+2019/11/26 13:37:09 workers: 6, corpus: 3 (18s ago), crashes: 0, restarts: 1/9948, execs: 99482 (5527/sec), cover: 1054, uptime: 18s
+2019/11/26 13:37:12 workers: 6, corpus: 3 (21s ago), crashes: 0, restarts: 1/9428, execs: 122568 (5836/sec), cover: 1054, uptime: 21s
+2019/11/26 13:37:15 workers: 6, corpus: 3 (24s ago), crashes: 0, restarts: 1/9676, execs: 145152 (6048/sec), cover: 1054, uptime: 24s
+2019/11/26 13:37:18 workers: 6, corpus: 3 (27s ago), crashes: 0, restarts: 1/9855, execs: 167538 (6205/sec), cover: 1054, uptime: 27s
+2019/11/26 13:37:21 workers: 6, corpus: 3 (30s ago), crashes: 0, restarts: 1/9645, execs: 192901 (6430/sec), cover: 1054, uptime: 30s
+2019/11/26 13:37:24 workers: 6, corpus: 3 (33s ago), crashes: 0, restarts: 1/9967, execs: 219294 (6645/sec), cover: 1054, uptime: 33s
 
 ```
 Otherwise:
@@ -34,7 +34,7 @@ go-fuzz -bin ./rlp/rlp-fuzz.zip
 Once a 'crasher' is found, the fuzzer tries to avoid reporting the same vector twice, so stores the fault in the `suppressions` folder. Thus, if you
 e.g. make changes to fix a bug, you should _remove_ all data from the `suppressions`-folder, to verify that the issue is indeed resolved.
 
-Also, if you have only one and the same exit-point for multiple different types of test, the suppression can make the fuzzer hide differnent types of errors. So make
+Also, if you have only one and the same exit-point for multiple different types of test, the suppression can make the fuzzer hide different types of errors. So make
 sure that each type of failure is unique (for an example, see the rlp fuzzer, where a counter `i` is used to differentiate between failures:
 
 ```golang