Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix typos and grammar in multiple files #216

Merged
merged 1 commit into from
Dec 20, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/pages/sylvia/basics/ibc.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ pub fn ibc_channel_open(
}
```

You can also define a trait for the IBC methods and implement it for on the contract.
You can also define a trait for the IBC methods and implement it on the contract.

```rust {7, 10, 12-13, 21-22}, template="sylvia-empty"
#[cfg_attr(not(feature = "library"), entry_point)]
Expand Down
2 changes: 1 addition & 1 deletion src/pages/tutorial/cw-contract/execution.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The idea of the contract will be easy - every contract admin would be eligible t
messages:

- `AddMembers` message would allow the admin to add another address to the admin's list
- `Leave` would allow and admin to remove himself from the list
- `Leave` would allow an admin to remove himself from the list

Not too complicated. Let's get coding. Start with defining messages:

Expand Down
6 changes: 3 additions & 3 deletions src/pages/tutorial/cw-contract/funds.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,9 @@ special meaning, like being used for paying
[staking](https://en.wikipedia.org/wiki/Proof_of_stake) for consensus algorithm, but can be just
arbitrary assets.

Native tokens are assigned to their owners but can be transferred. Everything have an address in the
blockchain is eligible to have its native tokens. As a consequence - tokens can be assigned to smart
contracts! Every message sent to the smart contract can have some funds sent with it. In this
Native tokens are assigned to their owners but can be transferred. Everything that has an address in
the blockchain is eligible to have its native tokens. As a consequence - tokens can be assigned to
smart contracts! Every message sent to the smart contract can have some funds sent with it. In this
chapter, we will take advantage of that and create a way to reward hard work performed by admins. We
will create a new message - `Donate`, which will be used by anyone to donate some funds to admins,
divided equally.
Expand Down
2 changes: 1 addition & 1 deletion src/pages/wasmd/getting-started/cli.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,7 @@ ALICE_ADDR=$(wasmd keys show alice -a --keyring-backend=test)
# Retrieve the address of Bob's account
BOB_ADDR=$(wasmd keys show bob -a --keyring-backend=test)

# Define init parameters fo the contract
# Define init parameters for the contract
INIT="{\"verifier\":\"$ALICE_ADDR\", \"beneficiary\":\"$BOB_ADDR\"}"
```

Expand Down