chore: fix some typos in comments (#2543)

Signed-off-by: alaningtrump <alaningtrump@outlook.com>

Author: alaningtrump

docs/build/guides/dapps/react.mdx

@@ -55,7 +55,7 @@ function MintButton({
 }
 ```
 
-This functional component takes three properties as arguments: `account`, `decimals`, and `symbol`. It demonstrates the concept of prop passing, a way to pass data from parent to child components in React. The `onComplete` prop even allows you to pass functions to your copmonents as props. We also see React's `useState` hook for local state management, a method to preserve values between function calls.
+This functional component takes three properties as arguments: `account`, `decimals`, and `symbol`. It demonstrates the concept of prop passing, a way to pass data from parent to child components in React. The `onComplete` prop even allows you to pass functions to your components as props. We also see React's `useState` hook for local state management, a method to preserve values between function calls.
 
 ## State Management and Hooks
 

docs/learn/fundamentals/transactions/list-of-operations.mdx

@@ -582,7 +582,7 @@ Learn more about claimable balances: [Claimable Balances Guide](../../../build/g
 
 | Parameters | Type | Description |
 | --- | --- | --- |
-| BalanceID | claimableBalanceID | The BalanceID on the ClaimableBalanceEntry that the source account is claiming, which can be retrieved from a succesful `CreateClaimableBalanceResult` |
+| BalanceID | claimableBalanceID | The BalanceID on the ClaimableBalanceEntry that the source account is claiming, which can be retrieved from a successful `CreateClaimableBalanceResult` |
 
 **Possible errors**:
 

docs/learn/migrate/evm/smart-contract-deployment.mdx

@@ -998,7 +998,7 @@ stellar contract invoke \
 
 </TabItem>
 
-<TabItem value="insatll wasm" label="install.sh">
+<TabItem value="install wasm" label="install.sh">
 
 ```bash
 stellar contract install \
@@ -1185,7 +1185,7 @@ stellar contract invoke \
     --token <TOKEN_CONTRACT_ADDRESS>
 ```
 
-After recieving the transaction has been submitted, we will mint some tokens to **both** our User Account and Vault Contract addresses. We can do this by running the `mint.sh` script.
+After receiving the transaction has been submitted, we will mint some tokens to **both** our User Account and Vault Contract addresses. We can do this by running the `mint.sh` script.
 
 ```bash
 stellar contract invoke \

docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx

@@ -106,7 +106,7 @@ In this example, the `GDJ...X47` public key identifies the sending organization,
 
 </CodeExample>
 
-Your business server can use any identifer for customers as long as it is a string.
+Your business server can use any identifier for customers as long as it is a string.
 
 Following the registration of a customer, the sending organization can use either approach when checking the customer's status. For example, you may get a `GET /customer` request like the following:
 
@@ -118,7 +118,7 @@ Following the registration of a customer, the sending organization can use eithe
 
 </CodeExample>
 
-Or, the sending organziation could use the identifier you returned when they originally registered the customer.
+Or, the sending organization could use the identifier you returned when they originally registered the customer.
 
 <CodeExample>
 
@@ -147,7 +147,7 @@ You can test your implementation with the [Stellar Demo Wallet][demo-wallet] fol
 5. Fund your account with a balance of the asset
 6. Select "SEP-31 Send" in the dropdown menu
 
-You should see the demo wallet find your service URLs, authenticate, and check which KYC fields it needs to collect. It should then present a form for you to enter the KYC details for the sender and reciever.
+You should see the demo wallet find your service URLs, authenticate, and check which KYC fields it needs to collect. It should then present a form for you to enter the KYC details for the sender and receiver.
 
 [![demo wallet after initiating a transaction](/assets/ap/anchor-platform-sep31-demo-wallet-widget.png)](/assets/ap/anchor-platform-sep31-demo-wallet-widget.png)
 

docs/tools/openzeppelin-contracts.mdx

@@ -75,7 +75,7 @@ OpenZeppelin Stellar Contracts is a collection of audited contracts and utilitie
   - **Pausable Operations**: Emergency pause functionality for the entire token
   - **Role-Based Access Control (RBAC)**: Flexible privilege management for administrative functions
 
-**Token Vault** The Fungible Token Vault extends the Fungible Token and implents [SEP-56 Tokenized Vault Standard](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md), enabling fungible tokens to represent shares in an underlying asset pool. The tokenized vault standard is the formalized interface for yield-bearing vaults that hold underlying assets. Vault shares enable hyperfungible collaterals in DeFi and remain fully compatible with standard fungible token operations.
+**Token Vault** The Fungible Token Vault extends the Fungible Token and implements [SEP-56 Tokenized Vault Standard](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md), enabling fungible tokens to represent shares in an underlying asset pool. The tokenized vault standard is the formalized interface for yield-bearing vaults that hold underlying assets. Vault shares enable hyperfungible collaterals in DeFi and remain fully compatible with standard fungible token operations.
 
 **Smart Accounts**
 
@@ -118,7 +118,7 @@ Repository Structure
 │   ├── tokens/                # Various token types (fungible, non-fungible, RWA, vault, etc.)
 ```
 
-To provide feedback on these contracts and utilties, please open issues at: [https://github.com/OpenZeppelin/stellar-contracts/issues](https://github.com/OpenZeppelin/stellar-contracts/issues)
+To provide feedback on these contracts and utilities, please open issues at: [https://github.com/OpenZeppelin/stellar-contracts/issues](https://github.com/OpenZeppelin/stellar-contracts/issues)
 
 ## OpenZeppelin Open Source Tools