docs: fix typos (#1319)

* fix typos in comments * docs: fix typos
cosmos · Oct 31, 2023 · e4e9f27 · e4e9f27
1 parent d0deac5
commit e4e9f27
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -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

diff --git a/docs/advanced_usage.md b/docs/advanced_usage.md
@@ -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:
 

diff --git a/docs/chain_implementation.md b/docs/chain_implementation.md
@@ -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

diff --git a/relayer/chains/cosmos/log.go b/relayer/chains/cosmos/log.go
@@ -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...,

diff --git a/relayer/chains/penumbra/log.go b/relayer/chains/penumbra/log.go
@@ -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...,