Skip to content

Commit c92d87a

Browse files
authored
Merge pull request CosmWasm#1227 from rtviii/patch-1
Update README.md
2 parents 13a04e2 + ba88e25 commit c92d87a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -273,10 +273,10 @@ pub struct Region {
273273

274274
If you followed the [instructions above](#Creating), you should have a runable
275275
smart contract. You may notice that all of the Wasm exports are taken care of by
276-
`lib.rs`, which should shouldn't need to modify. What you need to do is simply
277-
look in `contract.rs` and implement `instantiate` and `execute` functions,
278-
defining your custom `InstantiateMsg` and `ExecuteMsg` structs for parsing your
279-
custom message types (as json):
276+
`lib.rs`, which you shouldn't need to modify. What you need to do is simply look
277+
in `contract.rs` and implement `instantiate` and `execute` functions, defining
278+
your custom `InstantiateMsg` and `ExecuteMsg` structs for parsing your custom
279+
message types (as json):
280280

281281
```rust
282282
#[entry_point]
@@ -305,8 +305,8 @@ pub fn migrate(deps: DepsMut, env: Env, msg: MigrateMsg) -> Result<Response, Con
305305
The low-level `db_read` and `db_write` imports are nicely wrapped for you by a
306306
`Storage` implementation (which can be swapped out between real Wasm code and
307307
test code). This gives you a simple way to read and write data to a custom
308-
sub-database that this contract can safely write as it wants. It's up to you to
309-
determine which data you want to store here:
308+
sub-database that this contract can safely write to as it wants. It's up to you
309+
to determine which data you want to store here:
310310

311311
```rust
312312
/// Storage provides read and write access to a persistent storage.

0 commit comments

Comments
 (0)