fix some comments (#6318)

Signed-off-by: cui fliter <[email protected]>

Author: cuishuang

account-compression/sdk/tests/accountCompression.test.ts

@@ -196,7 +196,7 @@ describe('Account Compression', () => {
 
             assert(
                 splCMT.getAuthority().equals(randomSigner),
-                `Upon transfering authority, authority should be ${randomSigner.toString()}, but was instead updated to ${splCMT.getAuthority()}`
+                `Upon transferring authority, authority should be ${randomSigner.toString()}, but was instead updated to ${splCMT.getAuthority()}`
             );
 
             // Attempting to replace with new authority now works
@@ -342,7 +342,7 @@ describe('Account Compression', () => {
 
             try {
                 await execute(provider, [replaceIx], [payerKeypair]);
-                assert(false, 'Attacker was able to succesfully write fake existence of a leaf');
+                assert(false, 'Attacker was able to successfully write fake existence of a leaf');
             } catch (e) {}
 
             const splCMT = await ConcurrentMerkleTreeAccount.fromAccountAddress(connection, cmt);

docs/src/transfer-hook-interface/examples.md

@@ -136,7 +136,7 @@ instruction for some other program, which may not need them, if that program is
 going to CPI to your transfer hook program, it needs to have the proper
 accounts.
 
-Additionally, in order to perform a succesful dynamic account resolution, the
+Additionally, in order to perform a successful dynamic account resolution, the
 proper instruction needs to be provided to align with the instruction that was
 configured in the validation account - in this case the Transfer Hook
 interface's `ExecuteInstruction`. This is why we first create an

governance/program/src/state/legacy.rs

@@ -212,7 +212,7 @@ pub struct ProposalV1 {
     /// The number of instructions included in the proposal
     pub instructions_count: u16,
 
-    /// The index of the the next instruction to be added
+    /// The index of the next instruction to be added
     pub instructions_next_index: u16,
 
     /// When the Proposal was created and entered Draft state

governance/program/src/state/proposal.rs

@@ -65,7 +65,7 @@ pub struct ProposalOption {
     /// The number of transactions included in the option
     pub transactions_count: u16,
 
-    /// The index of the the next transaction to be added
+    /// The index of the next transaction to be added
     pub transactions_next_index: u16,
 }
 

libraries/math/src/precise_number.rs

@@ -29,7 +29,7 @@ fn zero() -> InnerUint {
 
 impl PreciseNumber {
     /// Correction to apply to avoid truncation errors on division.  Since
-    /// integer operations will always floor the result, we artifically bump it
+    /// integer operations will always floor the result, we artificially bump it
     /// up by one half to get the expect result.
     fn rounding_correction() -> InnerUint {
         InnerUint::from(ONE / 2)

libraries/merkle-tree-reference/src/lib.rs

@@ -31,7 +31,7 @@ pub fn recompute(mut leaf: Node, proof: &[Node], index: u32) -> Node {
     leaf
 }
 
-// Off-chain implentation to keep track of nodes
+// Off-chain implementation to keep track of nodes
 pub struct MerkleTree {
     pub leaf_nodes: Vec<Rc<RefCell<TreeNode>>>,
     pub root: Node,

libraries/tlv-account-resolution/src/account.rs

@@ -84,7 +84,7 @@ pub struct ExtraAccountMeta {
     /// Whether the account should be writable
     pub is_writable: PodBool,
 }
-/// Helper used to to know when the top bit is set, to interpret the
+/// Helper used to know when the top bit is set, to interpret the
 /// discriminator as an index rather than as a type
 const U8_TOP_BIT: u8 = 1 << 7;
 impl ExtraAccountMeta {

libraries/type-length-value/README.md

@@ -95,7 +95,7 @@ let value2 = state.get_value_with_repetition::<MyOtherPodValue>(2).unwrap();
 
 The Solana blockchain exposes slabs of bytes to on-chain programs, allowing program
 writers to interpret these bytes and change them however they wish. Currently,
-programs interpet account bytes as being only of one type. For example, an token
+programs interpret account bytes as being only of one type. For example, an token
 mint account is only ever a token mint, an AMM pool account is only ever an AMM pool,
 a token metadata account can only hold token metadata, etc.
 

name-service/program/src/processor.rs

@@ -85,7 +85,7 @@ impl Processor {
             // Issue the name registry account
             // The creation is done in three steps: transfer, allocate and assign, because
             // one cannot `system_instruction::create` an account to which lamports have
-            // been transfered before.
+            // been transferred before.
             invoke(
                 &system_instruction::transfer(payer_account.key, &name_account_key, lamports),
                 &[

stake-pool/cli/scripts/withdraw.sh

@@ -68,7 +68,7 @@ create_keypair $authority
 echo "Withdrawing stakes from stake pool"
 withdraw_stakes "$stake_pool_pubkey" "$validator_list" "$withdraw_sol_amount"
 
-echo "Withdrawing stakes from stake pool to recieve it in stake receiver account"
+echo "Withdrawing stakes from stake pool to receive it in stake receiver account"
 withdraw_stakes_to_stake_receiver "$stake_pool_pubkey" "$validator_list" "$withdraw_sol_amount"
 
 echo "Withdrawing SOL from stake pool to authority"