docs: fix spelling issues (#390)

* Update event.md
* Update contract.md
* Update advanced-configuration.md

Author: nnsW3

docs/architecture/event.md

@@ -72,7 +72,7 @@ Contract Event and Contract Log Even support event filter function which include
 ```
 fromBlock: the start block number
 toBlock: the end block number
-contractAddress: contract adsresses list
+contractAddress: contract addresses list
 contractTopics: contract topics list
 ```
 
@@ -190,4 +190,4 @@ When the node has a new block, the subscriber will receive block event, the outp
 ```
 received a message related to: blockTrigger, containing message: {"timeStamp":1678343709000,"triggerName":"blockTrigger","blockNumber":1361,"blockHash":"00000000000005519b3995cd638753a862c812d1bda11de14bbfaa5ad3383280","transactionSize":0,"latestSolidifiedBlockNumber":1361,"transactionList":[]}
 received a message related to: blockTrigger, containing message: {"timeStamp":1678343712000,"triggerName":"blockTrigger","blockNumber":1362,"blockHash":"0000000000000552d53d1bdd9929e4533a983f14df8931ee9b3bf6d6c74a47b0","transactionSize":0,"latestSolidifiedBlockNumber":1362,"transactionList":[]}
-```
+```

docs/contracts/contract.md

@@ -62,12 +62,12 @@ message SmartContract {
 ```
 origin_address: smart contract creator address
 contract_address: smart contract address
-abi: the api information of the all the function of the smart contract
+abi: the api information of all the function of the smart contract
 bytecode: smart contract byte code
 call_value: TRX transferred into smart contract while call the contract
 consume_user_resource_percent: resource consumption percentage set by the developer
 name: smart contract name
-origin_energy_limit: energy consumption of the developer limit in one call, must greater than 0. For the old contracts, if this parameter is not set, it will be set 0, developer can use updateEnergyLimit api to update this parameter (must greater than 0)
+origin_energy_limit: energy consumption of the developer limit in one call, must be greater than 0. For the old contracts, if this parameter is not set, it will be set 0, developer can use updateEnergyLimit api to update this parameter (must greater than 0)
 
 Through other two grpc message types CreateSmartContract and TriggerSmartContract to create and use smart contract.
 

docs/developers/advanced-configuration.md

@@ -92,7 +92,7 @@ node.backup {
 ```
 policy: 
 1. the one which synchronized first will become master.
-2. if synchronization is completed at the same time, the one which with big priority will become master.
+2. if synchronization is completed at the same time, the one with big priority will become master.
 
 E.g. create backups for node A(192.168.0.100) and node B(192.168.0.100 ):
 node A's configuration: