diff --git a/contracts/cw20-ics20/README.md b/contracts/cw20-ics20/README.md index 3feae9a19..9be95ff95 100644 --- a/contracts/cw20-ics20/README.md +++ b/contracts/cw20-ics20/README.md @@ -1,7 +1,7 @@ # CW20 ICS20 This is an *IBC Enabled* contract that allows us to send CW20 tokens from one chain over the standard ICS20 -protocol to the bank module of another chain. In short, it let's us send our custom CW20 tokens with IBC and use +protocol to the bank module of another chain. In short, it lets us send our custom CW20 tokens with IBC and use them just like native tokens on other chains. It is only designed to send tokens and redeem previously sent tokens. It will not mint tokens belonging diff --git a/contracts/cw20-ics20/src/lib.rs b/contracts/cw20-ics20/src/lib.rs index 6260eef54..a9dba517d 100644 --- a/contracts/cw20-ics20/src/lib.rs +++ b/contracts/cw20-ics20/src/lib.rs @@ -1,6 +1,6 @@ /*! This is an *IBC Enabled* contract that allows us to send CW20 tokens from one chain over the standard ICS20 -protocol to the bank module of another chain. In short, it let's us send our custom CW20 tokens with IBC and use +protocol to the bank module of another chain. In short, it lets us send our custom CW20 tokens with IBC and use them just like native tokens on other chains. It is only designed to send tokens and redeem previously sent tokens. It will not mint tokens belonging diff --git a/packages/cw1/README.md b/packages/cw1/README.md index 78df4593c..72a95915a 100644 --- a/packages/cw1/README.md +++ b/packages/cw1/README.md @@ -6,7 +6,7 @@ where one contract is meant to hold assets (or rights) on behalf of other contracts. The simplest example is a contract that will accept messages from -the creator and resend them from it's address. Simply by making this +the creator and resend them from its address. Simply by making this transferable, you can then begin to transfer non-transferable assets (eg. staked tokens, voting power, etc). diff --git a/packages/cw1/src/lib.rs b/packages/cw1/src/lib.rs index b5a8571f6..a73529538 100644 --- a/packages/cw1/src/lib.rs +++ b/packages/cw1/src/lib.rs @@ -5,7 +5,7 @@ where one contract is meant to hold assets (or rights) on behalf of other contracts. The simplest example is a contract that will accept messages from -the creator and resend them from it's address. Simply by making this +the creator and resend them from its address. Simply by making this transferable, you can then begin to transfer non-transferable assets (eg. staked tokens, voting power, etc). diff --git a/packages/cw2/README.md b/packages/cw2/README.md index 3d1e31781..b80c599a2 100644 --- a/packages/cw2/README.md +++ b/packages/cw2/README.md @@ -5,10 +5,10 @@ of the contract. The APIs used for `ExecuteMsg` or `QueryMsg`. However, when we wish to migrate or inspect smart contract info, we need some form of smart contract information embedded on state. -This is where CW2 comes in. It specifies on special Item to +This is where CW2 comes in. It specifies a special Item to be stored on disk by all contracts on `instantiate`. -`ContractInfo` is must be stored under `"contract_info"` key which translates +`ContractInfo` must be stored under the `"contract_info"` key which translates to `"636F6E74726163745F696E666F"` in hex format. Since the state is well defined, we do not need to support any "smart queries". We do provide a helper to construct a "raw query" to read the ContractInfo diff --git a/packages/cw2/src/lib.rs b/packages/cw2/src/lib.rs index 4866d54b1..12cb7b594 100644 --- a/packages/cw2/src/lib.rs +++ b/packages/cw2/src/lib.rs @@ -4,10 +4,10 @@ of the contract. The APIs used for `ExecuteMsg` or `QueryMsg`. However, when we wish to migrate or inspect smart contract info, we need some form of smart contract information embedded on state. -This is where CW2 comes in. It specifies on special Item to +This is where CW2 comes in. It specifies a special Item to be stored on disk by all contracts on `instantiate`. -`ContractInfo` is must be stored under `"contract_info"` key which translates +`ContractInfo` must be stored under the `"contract_info"` key which translates to `"636F6E74726163745F696E666F"` in hex format. Since the state is well defined, we do not need to support any "smart queries". We do provide a helper to construct a "raw query" to read the ContractInfo diff --git a/packages/cw4/README.md b/packages/cw4/README.md index 3cf96ae9e..d2203088d 100644 --- a/packages/cw4/README.md +++ b/packages/cw4/README.md @@ -12,9 +12,9 @@ the ones laid out here should be under the specified keys and in the same format. In this case, a cw3 contract could *read* an external group contract with -no significant cost more than reading local storage. However, updating +no significant cost besides reading local storage. However, updating that group contract (if allowed), would be an external message and -charged the instantiation overhead for each contract. +will be charged as part of the overhead for each contract. ## Messages diff --git a/packages/cw4/src/lib.rs b/packages/cw4/src/lib.rs index 9aa21c717..71c6f2e0d 100644 --- a/packages/cw4/src/lib.rs +++ b/packages/cw4/src/lib.rs @@ -11,9 +11,9 @@ the ones laid out here should be under the specified keys and in the same format. In this case, a cw3 contract could *read* an external group contract with -no significant cost more than reading local storage. However, updating +no significant cost besides reading local storage. However, updating that group contract (if allowed), would be an external message and -charged the instantiation overhead for each contract. +will be charged as part of the overhead for each contract. For more information on this specification, please check out the [README](https://github.com/CosmWasm/cw-plus/blob/main/packages/cw4/README.md).