docs: Fix typos (#5808)

* fix typo * fix typo * fix typos * fix typo * fix typo
solana-labs · Nov 13, 2023 · 6fe3c15 · 6fe3c15
1 parent b1ba649
commit 6fe3c15
Show file tree

Hide file tree

Showing 5 changed files with 9 additions and 9 deletions.
diff --git a/account-compression/sdk/README.md b/account-compression/sdk/README.md
@@ -137,7 +137,7 @@ await sendAndConfirmTransaction(connection, tx, [payer]);
 
 4. Replace a leaf in the tree, using a 3rd party indexer
 
-This example assumes that some 3rd party service is indexing the the tree at `cmtKeypair.publicKey` for you, and providing MerkleProofs via some REST endpoint.
+This example assumes that some 3rd party service is indexing the tree at `cmtKeypair.publicKey` for you, and providing MerkleProofs via some REST endpoint.
 The `getProofFromAnIndexer` function is a **placeholder** to exemplify this relationship.
 
 ```typescript
@@ -177,4 +177,4 @@ Here are some examples using account compression in the wild:
 
 2. Then build the SDK with `yarn build`.
 
-3. Run tests with `yarn test`. (Expect `jest` to detect an open handle that prevents it from exiting naturally)
+3. Run tests with `yarn test`. (Expect `jest` to detect an open handle that prevents it from exiting naturally)
diff --git a/docs/src/feature-proposal.md b/docs/src/feature-proposal.md
@@ -60,7 +60,7 @@ This section describes the life cycle of a feature proposal.
 The first step is to conceive of the new feature and realize it in the
 Solana code base, working with the core Solana developers at https://github.com/solana-labs/solana.
 
-During the implementation, a *feature id* will be required to identity the new
+During the implementation, a *feature id* will be required to identify the new
 feature in the code base to avoid the new functionality until its activation.
 The *feature id* for a feature proposal is derived by running the following
 commands.
@@ -140,8 +140,8 @@ acceptance, the votes are tallied by running:
 ```
 $ spl-feature-proposal tally 8CyUVvio2oYAP28ZkMBPHq88ikhRgWet6i4NYsCW5Cxa
 ```
-Anybody may tally the vote.  Once the required number of votes are tallied, the
+Anybody may tally the vote.  Once the required number of votes is tallied, the
 feature will be automatically activated at the start of the next epoch.
 
 Upon a successful activation the feature will now show as activated by
-`solana feature status` as well.
+`solana feature status` as well.
diff --git a/docs/src/single-pool.mdx b/docs/src/single-pool.mdx
@@ -94,7 +94,7 @@ $ solana config set --keypair usb://ledger/
 the wallet to draw funds from (for instance, to fund new stake accounts),
 and the signing authority on accounts that require one.
 When token accounts are required, it defaults to the default keypair's associated account.
-All of these roles can be overrided by command-line flags.
+All of these roles can be overriden by command-line flags.
 
   </TabItem>
   <TabItem value="jsc" label="WEB3.JS CLASSIC">

diff --git a/docs/src/stake-pool/overview.md b/docs/src/stake-pool/overview.md
@@ -66,7 +66,7 @@ using the `add-validator` instruction. In this command, the stake pool uses
 reserve funds to create a new stake account and delegate it to the desired validator.
 
 At this point, users can also deposit a stake account into the pool.  To do this,
-they must delegate a stake account to the one of the validators in the stake pool.
+they must delegate a stake account to one of the validators in the stake pool.
 If the stake pool has a preferred deposit validator, the user must delegate their
 stake to that validator's vote account.
 
@@ -172,7 +172,7 @@ In this way, a user's funds are never at risk, and always redeemable.
 ### Active stakes
 
 As mentioned earlier, the stake pool works with active stakes to
-maintains fungibility of stake pool tokens. Fully activated stakes
+maintain fungibility of stake pool tokens. Fully activated stakes
 are not equivalent to inactive, activating, or deactivating stakes due to the
 time cost of staking.
 

diff --git a/docs/src/stake-pool/quickstart.md b/docs/src/stake-pool/quickstart.md
@@ -207,7 +207,7 @@ through an automated system to collect information about the stake pool and the
 network, and decide how much stake to allocate to each validator.
 
 The Solana Foundation maintains an open-source bot for its delegation program,
-which can be adapated for your stake pool. The source code is part of the
+which can be adapted for your stake pool. The source code is part of the
 [stake-o-matic GitHub repo](https://github.com/solana-labs/stake-o-matic/tree/master/bot).
 
 Additionally, there is a work-in-progress Python stake pool bot, found at the