Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix spelling issues #390

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+5 −5
Open

docs: fix spelling issues #390

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0b7b47e
Update event.md
nnsW3 Oct 8, 2024
4b1fbcd
Update contract.md
nnsW3 Oct 8, 2024
eecdce7
Update advanced-configuration.md
nnsW3 Oct 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/architecture/event.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```

Expand Down Expand Up @@ -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":[]}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_

```
```
4 changes: 2 additions & 2 deletions docs/contracts/contract.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs/developers/advanced-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down