fix: multiple typos of different importance (#25068)
Co-authored-by: Alex | Interchain Labs <alex@interchainlabs.io>
This commit is contained in:
co-authored by
Alex | Interchain Labs
parent
86245cba91
commit
bc8ac8108f
@@ -253,7 +253,7 @@ message QuerySupplyResponse {
|
||||
uint64 amount = 1;
|
||||
}
|
||||
|
||||
// QueryNFTstRequest is the request type for the Query/NFTs RPC method
|
||||
// QueryNFTsRequest is the request type for the Query/NFTs RPC method
|
||||
message QueryNFTsRequest {
|
||||
string class_id = 1;
|
||||
string owner = 2;
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# ADR 048: Multi Tire Gas Price System
|
||||
# ADR 048: Multi Tier Gas Price System
|
||||
|
||||
## Changelog
|
||||
|
||||
@@ -26,7 +26,7 @@ We propose a multi-tier price system on consensus to provide maximum flexibility
|
||||
* Tier 2: a dynamic gas price which is adjusted according to previous block load.
|
||||
* Tier 3: a dynamic gas price which is adjusted according to previous block load at a higher speed.
|
||||
|
||||
The gas price of higher tier should bigger than the lower tier.
|
||||
The gas price of higher tier should be bigger than the lower tier.
|
||||
|
||||
The transaction fees are charged with the exact gas price calculated on consensus.
|
||||
|
||||
|
||||
@@ -644,7 +644,7 @@ type IntegrationTestConfig struct {
|
||||
}
|
||||
|
||||
// Run runs the test function for all combinations of dependency modules.
|
||||
func (cfg IntegationTestConfig) Run(t *testing.T, f func (t *testing.T, f IntegrationTestFixture)) {
|
||||
func (cfg IntegrationTestConfig) Run(t *testing.T, f func (t *testing.T, f IntegrationTestFixture)) {
|
||||
// ...
|
||||
}
|
||||
```
|
||||
|
||||
@@ -202,7 +202,7 @@ At this point, it is necessary to delete the `priv_validator_key.json` from the
|
||||
vim $HOME/tmkms/config/tmkms.toml
|
||||
```
|
||||
|
||||
This example shows a configuration that could be used for soft signing. The example has an IP of `123.456.12.345` with a port of `26659` a chain_id of `test-chain-waSDSe`. These are items that most be modified for the usecase of tmkms and the network.
|
||||
This example shows a configuration that could be used for soft signing. The example has an IP of `123.456.12.345` with a port of `26659` a chain_id of `test-chain-waSDSe`. These are items that must be modified for the usecase of tmkms and the network.
|
||||
|
||||
```toml
|
||||
# CometBFT KMS configuration file
|
||||
|
||||
@@ -16,7 +16,7 @@ With the separation of CometBFT and Cosmos-SDK, there is a lack of control of wh
|
||||
|
||||
The acceptance of this RFC would move validation within `ValidateBasic` to the message server in modules, update tutorials and docs to remove mention of using `ValidateBasic` in favour of handling all validation for a message where it is executed.
|
||||
|
||||
We can and will still support the `Validatebasic` function for users and provide an extension interface of the function once `sdk.Msg` is deprecated.
|
||||
We can and will still support the `ValidateBasic` function for users and provide an extension interface of the function once `sdk.Msg` is deprecated.
|
||||
|
||||
> Note: This is how messages are handled in VMs like Ethereum and CosmWasm.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user