Skip to content

Commit efa32ca

Browse files
committed
Update README.md
1 parent 600d217 commit efa32ca

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

steps/10/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -226,10 +226,10 @@ impl<T: Config> Pallet<T> {
226226
If, for example, you wanted to call the `mint` function in the pallet you are working on and ensure the mint succeeded, you would simply write:
227227

228228
```rust
229-
assert_oK!(PalletKitties::mint(some_account));
229+
assert_ok!(PalletKitties::mint(some_account));
230230
```
231231

232-
This is not any kind of Polkadot SDK specific magic, this is just regular Rust.
232+
This is not any kind of Polkadot SDK specific magic. This is just regular Rust.
233233

234234
### Checking Events
235235

@@ -240,9 +240,9 @@ For this, you can use `System::assert_last_event(...)`, which checks in storage
240240
You can see an example of this added to our `tests.rs` file in this step.
241241

242242
One really important thing to remember is that you need to set the block number to a value greater than zero for events to work!
243-
This is because on the genesis block, we don't want to emit events, because there will be so many of them, it would bloat and lag our blockchain on that zeroth block.
243+
This is because, on the genesis block, we don't want to emit events since there will be so many of them it would bloat and lag our blockchain on that zeroth block.
244244

245-
If you write a test, and you expect some event, but don't see it, just double check that you have set the block number.
245+
If you write a test and expect some event, but don't see it, just double-check that you have set the block number.
246246

247247
## Your Turn!
248248

0 commit comments

Comments
 (0)