typos fixing

pages/automation/create-compatible-contracts.mdx

@@ -232,7 +232,7 @@ For example, if you have a contract where you create a timer in checkTask() that
 ### Perform only when data is verified
 Some actions must be performed using data you intend to use. Revalidate that the performData is allowed before execution.
 
-For example, if you have a performTask() that funds a wallet and the address of the wallet is received via the performData parameter, ensure you have a list of permissable addresses to compare against to prevent third-party calling your function to send money to their address.
+For example, if you have a performTask() that funds a wallet and the address of the wallet is received via the performData parameter, ensure you have a list of permissible addresses to compare against to prevent third-party calling your function to send money to their address.
 
 ### When performing is not harmful
 Sometimes actions must be performed when conditions are met, but performing actions when conditions are not met is still acceptable. 

pages/delegated-staking/gnosis/unstake.mdx

@@ -18,7 +18,7 @@ It means that the release time for your GNO tokens may vary, but on average it t
 1. Open [Ankr Staking Dashboard](https://www.ankr.com/staking/dashboard/).
 2. Locate the GNO box and click **Manage**.
    <img src="/docs/staking/delegated-staking/gnosis/click-manage.jpg" alt="Click Manage" class="responsive-pic" width="600" />
-3. Choose a Node Provide (currently, only Ankr; more providers come later) and click the the **-** icon.
+3. Choose a Node Provide (currently, only Ankr; more providers come later) and click the **-** icon.
    <img src="/docs/staking/delegated-staking/gnosis/click-minus-icon.jpg" alt="Click Manage" class="responsive-pic" width="600" />
 4. Enter the desired amount to unstake, but no less than 0.5 ETH, and click **Unstake**.
    <img src="/docs/staking/delegated-staking/gnosis/enter-amount-click-unstake.jpg" alt="Click Unstake" class="responsive-pic" width="400" />

pages/rpc-service/chains/chains-api/solana.mdx

@@ -3813,7 +3813,7 @@ curl -X POST https://rpc.ankr.com/solana \
 
     * `<string>` (required): the Pubkey of the account to receive lamports, as base-58 encoded string.
     * `integer` (required): lamports, as a u64.
-    * `object` (optional): the configuration object containing the follwing field:
+    * `object` (optional): the configuration object containing the following field:
       * `commitment` (string): used for retrieving blockhash and verifying airdrop success; the commitment describes how finalized a block is at that point in time. When querying the ledger state, it's recommended to use lower levels of commitment to report progress and higher levels to ensure the state will not be rolled back. For processing many dependent transactions in series, it's recommended to use "confirmed" commitment, which balances speed with rollback safety. For total safety, it's recommended to use "finalized" commitment:
         * `finalized`: the node will query the most recent block confirmed by supermajority of the cluster as having reached maximum lockout, meaning the cluster has recognized this block as finalized.
         * `confirmed`: the node will query the most recent block that has been voted on by supermajority of the cluster.

pages/rpc-service/chains/chains-api/tron.mdx

@@ -5487,7 +5487,7 @@ curl -X POST 'https://rpc.ankr.com/http/tron/wallet/getdelegatedresourceaccounti
 }'
 ```
 
-#### Response exmple ???
+#### Response example ???
 
 ```json
 {