@@ -24,7 +24,7 @@ Example: we could upload a generic "ERC20 mintable" contract, and many people co
24
24
independent instances based on the same bytecode, where the local data defines the token name, the
25
25
issuer, the max issuance, etc.
26
26
27
- 1 . First you ** create ** a _ contract_ ,
27
+ 1 . First you ** store ** a _ contract_ ,
28
28
2 . Then you ** instantiate** an _ instance_ ,
29
29
3 . Finally users ** invoke** the _ instance_ .
30
30
@@ -75,7 +75,7 @@ may either return a success (with data and events) or an error. In the case of a
75
75
will revert the entire transaction in the block.
76
76
77
77
In this document we focus on the ` execute ` entry-point implementation and call to show you the
78
- execution flow if the smart contracts. For more information on how to create contract and define
78
+ execution flow of the smart contracts. For more information on how to create contract and define
79
79
other basic entry-points, check [ the entrypoints section] ( entrypoints.mdx ) .
80
80
81
81
### Basic Execution
@@ -148,7 +148,7 @@ cache. If `gas_limit` is set, it is sandboxed to how much gas it can use until i
148
148
` OutOfGasError ` . This error is caught and returned to the caller like any other error returned from
149
149
contract execution (unless it burned the entire gas limit of the transaction).
150
150
151
- If it return success, the temporary state is committed (into the caller's cache), and the
151
+ If it returns success, the temporary state is committed (into the caller's cache), and the
152
152
[ ` Response ` ] ( https://docs.rs/cosmwasm-std/latest/cosmwasm_std/struct.Response.html ) is processed as
153
153
normal. Once the response is fully processed, this may then be intercepted by the calling contract
154
154
(for ` ReplyOn::Always ` and ` ReplyOn::Success ` ). On an error, the subcall will revert any partial
0 commit comments