Skip to content

Commit 161b9b9

Browse files
committed
fixes
1 parent 10c72d1 commit 161b9b9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/governance/governance-interaction.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The starting & ending epochs should be an even-length hex string containing the
3939
After issuing the proposal, there is a log event generated having the `proposal` identifier that will contain the following encoded topics:
4040

4141
- `nonce` as encoded integer which uniquely identifies the proposals
42-
- `identifier` the provided 40 hex characters long identifier
42+
- `identifier` is the provided 40 hex characters long identifier
4343
- `start epoch` as encoded integer for the starting epoch
4444
- `end epoch` as encoded integer for the ending epoch
4545

@@ -105,7 +105,7 @@ This is very useful whenever implementing liquid-staking-like smart contracts. T
105105
The maximum value for the staked value & the voting power for the liquid-staking contract is known by the governance contract, so it can not counterfeit the voting. If, due to a bug the liquid-staking contract allows, for example, for a user to vote with a larger quota, the liquid-staking contract will deplete its maximum allowance making other voting transactions (on his behalf) to fail.
106106
:::
107107

108-
The user that delegated through a liquid-staking-like contract in order to vote on a proposal, sends a transaction to the liquid-staking-like contract. The smart contract then creates the GovernanceVoteThroughDelegationTransaction based on the users transaction inputs to forward the vote and the computed voting power to the governance contract.
108+
The user that delegated through a liquid-staking-like contract in order to vote on a proposal, sends a transaction to the liquid-staking-like contract. The smart contract then creates the GovernanceVoteThroughDelegationTransaction based on the user’s transaction inputs, forwarding the vote and the computed voting power to the governance contract.
109109

110110
```rust
111111
GovernanceVoteThroughDelegationTransaction {
@@ -363,7 +363,7 @@ The response will contain the following json definition where all fields are bas
363363
"<lost_proposal_fee>", (the amount of EGLD that the issuer loses if the proposal fails)
364364
"<min_quorum>", (the minimum percentage of total voting power required for a proposal to be considered valid)
365365
"<min_veto_threshold>", (the minimum percentage of veto votes needed to reject a proposal and slash its fee)
366-
"<min_pass_threshold>", (the minimum percentage of YES votes required for a proposal to
366+
"<min_pass_threshold>", (the minimum percentage of YES votes required for a proposal to pass)
367367
"<last_proposal_nonce>" (the nonce of the last created proposal)
368368
]
369369
}

0 commit comments

Comments
 (0)