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 #1319

Merged
merged 2 commits into from
Oct 31, 2023
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 README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Additional information on how IBC works can be found [here](https://ibc.cosmos.n
- [Relayer Terminology](./docs/terminology.md)
- [New Chain Implementation](./docs/chain_implementation.md)
- [Recommended Pruning Settings](./docs/node_pruning.md)
- [Demo/Dev-Environmnet](./examples/README.md)
- [Demo/Dev-Environment](./examples/README.md)

---
## Basic Usage - Relaying Packets Across Chains
Expand Down
2 changes: 1 addition & 1 deletion docs/advanced_usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ By default, the Relayer will automatically update clients (`MsgUpdateClient`) if
> This auto-update functionality is specifically useful on low trafficked paths where messages aren't regularly being relayed.


Alternitavely, you can choose to update clients more frequently by using the `--time-threshold` flag when running the `rly start` command.
Alternatively, you can choose to update clients more frequently by using the `--time-threshold` flag when running the `rly start` command.

Example:

Expand Down
2 changes: 1 addition & 1 deletion docs/chain_implementation.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ After this, before the main poll loop or subscriber begins, two `ChainProcessor`

These caches are aliased types to `map[ConnectionKey]bool` and `map[ChannelKey]bool` respectively. The `PathProcessor` needs to know which connections are open and which channels are open. A value of `true` for the specific `ConnectionKey` or `ChannelKey` will inform the `PathProcessor` that the connection or channel is open later on once these caches are shared with the `PathProcessor`.

During the initalization of these caches, separate mappings should also be built for which connections belong to which clients and which channels belong to which connections. The example of these in the `CosmosChainProcessor` are:
During the initialization of these caches, separate mappings should also be built for which connections belong to which clients and which channels belong to which connections. The example of these in the `CosmosChainProcessor` are:

```go
// map of connection ID to client ID
Expand Down
2 changes: 1 addition & 1 deletion relayer/chains/cosmos/log.go
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ func (cc *CosmosProvider) LogSuccessTx(res *sdk.TxResponse, msgs []provider.Rela
zap.String("tx_hash", res.TxHash),
)

// Log the succesful transaction with fields
// Log the successful transaction with fields
cc.log.Info(
"Successful transaction",
fields...,
Expand Down
2 changes: 1 addition & 1 deletion relayer/chains/penumbra/log.go
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ func (cc *PenumbraProvider) LogSuccessTx(res *sdk.TxResponse, msgs []provider.Re
zap.String("tx_hash", res.TxHash),
)

// Log the succesful transaction with fields
// Log the successful transaction with fields
cc.log.Info(
"Successful transaction",
fields...,
Expand Down
Loading