Merge pull request #545 from wmjae/fix-typo

pyramation · web-flow · commit 485b6d3e092e · 2025-04-14T20:47:37.000-07:00
fix typos in documentation files
diff --git a/packages/docs/pages/advanced.md b/packages/docs/pages/advanced.md
@@ -13,11 +13,11 @@ There are four important classes.
 
 Before all, we need to clarify that there are two types of entities in CosmosKit as a wallet adapter: **Chain** and **Wallet**. Chain is identified by chain name i.e. `cosmoshub`, `osmosis` etc. And wallet is identified by wallet name i.e. `keplr-extension`, `keplr-mobile`, `cosmostation-extension` etc.
 
-> Note that we're taking a single wallet application as a wallet in CosmosKit rather than the wallet product name. Taking `Keplr` as an example, we diffientiate `extension` and `mobile` in our code because they are connected via totally different codes. So for product `Keplr`, we have two wallets `keplr-extension` and `keplr-mobile` in CosmosKit.
+> Note that we're taking a single wallet application as a wallet in CosmosKit rather than the wallet product name. Taking `Keplr` as an example, we differentiate `extension` and `mobile` in our code because they are connected via totally different codes. So for product `Keplr`, we have two wallets `keplr-extension` and `keplr-mobile` in CosmosKit.
 
 ### WalletManager
 
-`WalletManager` is the entrance of the whole code and it manages all `WalletRepo`, `MainWalletBase`, `ChainWalletBase` instances in it. It also corresponds to `ChainProvider` in `@cosmos-kit/react-lite` and `@cosmos-kit/react`. You can find that the properties of JSX element `ChainProvider` are almost the same with the constructor arguments of `WalletManager`. All necesssary chain information and wallet information from `ChainProvider` will be passed to corresponding wallet classes via `WalletManager`.
+`WalletManager` is the entrance of the whole code and it manages all `WalletRepo`, `MainWalletBase`, `ChainWalletBase` instances in it. It also corresponds to `ChainProvider` in `@cosmos-kit/react-lite` and `@cosmos-kit/react`. You can find that the properties of JSX element `ChainProvider` are almost the same with the constructor arguments of `WalletManager`. All necessary chain information and wallet information from `ChainProvider` will be passed to corresponding wallet classes via `WalletManager`.
 
 Three important properties/arguments in `ChainProvider`/`WalletManager` are `chains`, `assetLists` and `wallets`. `chains` and `assetLists` provide chain information, and `wallets` provides wallet information. Actually `wallets` is an array of `MainWalletBase` instances. Here leads to the second class `MainWalletBase`.
 
diff --git a/packages/docs/pages/cookbook/sign.mdx b/packages/docs/pages/cookbook/sign.mdx
@@ -18,7 +18,7 @@ const { getSigningStargateClient } = useChain('cosmoshub');
 const aminoSigningClient = await getSigningStargateClient();
 ```
 
-By default use `amino` signer. Or you need to set `return 'direct'` if `direct` signer required.
+By default use `amino` signer. Or you need to set `return 'direct'` if `direct` signer is required.
 
 ## Individual Settings
 
diff --git a/packages/docs/pages/get-started.mdx b/packages/docs/pages/get-started.mdx
@@ -28,7 +28,7 @@ Taking `Keplr` wallet as an example.
 yarn add @cosmos-kit/react @cosmos-kit/keplr chain-registry
 ```
 
-`@cosmos-kit/react` includes default modal made with `@interchain-ui/react`. If [customized modal](/provider/chain-provider/#customize-modal-with-walletmodal) is provided, you can use `@cosmos-kit/react-lite` instead to lighter your app.
+`@cosmos-kit/react` includes default modal made with `@interchain-ui/react`. If [customized modal](/provider/chain-provider/#customize-modal-with-walletmodal) is provided, you can use `@cosmos-kit/react-lite` instead to lighten your app.
 
 There are multiple wallets supported by CosmosKit. Details see [Integrating Wallets](/integrating-wallets)
 
diff --git a/packages/docs/pages/integrating-wallets/ledger.mdx b/packages/docs/pages/integrating-wallets/ledger.mdx
@@ -2,7 +2,7 @@
 
 ## Prerequisites
 
-1. Connect your Ledger device via an USB cable and unlock it.
+1. Connect your Ledger device via a USB cable and unlock it.
 2. Open the Cosmos app in Ledger, which shows `Cosmos Ready` in the screen.
 
 ## Browser Support
diff --git a/packages/docs/pages/provider/chain-provider.mdx b/packages/docs/pages/provider/chain-provider.mdx
@@ -195,7 +195,7 @@ function CosmosApp() {
 
 **Type:** `NameServiceName` = `string`;
 
-Currently two name services are registered: `'icns'` and `'stargaze'`. The default name service is `icns`. This property is only used in `getNameService` of `useManager` when prarameter `chainName` is undefined, and in `useNameService` when the prarameter `name` is not provided. Otherwise it will return the name service object corresponding to provided chain. Therefore it won't affect `getNameService` method returned by `useChain`, since `chainName` is always provide in `useChain`.
+Currently two name services are registered: `'icns'` and `'stargaze'`. The default name service is `icns`. This property is only used in `getNameService` of `useManager` when parameter `chainName` is undefined, and in `useNameService` when the parameter `name` is not provided. Otherwise it will return the name service object corresponding to provided chain. Therefore it won't affect `getNameService` method returned by `useChain`, since `chainName` is always provide in `useChain`.
 
 ### endpointOptions
 
@@ -261,7 +261,7 @@ There are four levels of `isLazy` setting.
 
 3. Endpoint `isLazy`: `isLazy` in `ExtendedHttpEndpoint` only controls the one in `ExtendedHttpEndpoint` object. For signing or broadcasting a transaction, this one is the lowerst level and with the highest priority.
 
-4. Parameter `isLazy`: `isLazy` in `getRpcEndpoint` and `getRestEndpoint` prarameters. It also globally controls all endpoints. (Note: this one only affects getting endpoint functions with the highest priority, but won't affect signing or broadcasting a transaction.)
+4. Parameter `isLazy`: `isLazy` in `getRpcEndpoint` and `getRestEndpoint` parameters. It also globally controls all endpoints. (Note: this one only affects getting endpoint functions with the highest priority, but won't affect signing or broadcasting a transaction.)
 
 The calculation of final `isLazy` can be seen [here](https://github.com/hyperweb-io/cosmos-kit/blob/main/packages/core/src/utils/endpoint.ts#L32-L59).
 
diff --git a/wallets/okxwallet-extension/README.md b/wallets/okxwallet-extension/README.md
@@ -12,7 +12,7 @@
    <a href="https://www.npmjs.com/package/@cosmos-kit/okxwallet-extension"><img height="20" src="https://img.shields.io/github/package-json/v/hyperweb-io/cosmos-kit?filename=wallets%2Fokxwallet-extension%2Fpackage.json"></a>
 </p>
 
-Cosmos Kit is a univeral wallet adapter for developers to build apps that quickly and easily interact with Cosmos blockchains and wallets.
+Cosmos Kit is a universal wallet adapter for developers to build apps that quickly and easily interact with Cosmos blockchains and wallets.
 
 @cosmos-kit/okxwallet is the okxWallet integration for Cosmos Kit.
 
