Update docs: corrections errors

docs/docs/learn/builder-guides/bridged-btc-gas-fee/account-abstraction/index.md

@@ -53,9 +53,9 @@ Given that ERC-4337 is still relatively new, there is not a lot of support for t
 
 ## Opportunities
 
-There are a interesting use cases that account abstraction enables being pushed by several team. Some places to look for inspiration:
+There are interesting use cases that account abstraction enables being pushed by several team. Some places to look for inspiration:
 
-- [Privy](https://docs.privy.io/): Privy allows users to chose from traditional crypto wallets and social logins to create accounts.
+- [Privy](https://docs.privy.io/): Privy allows users to choose from traditional crypto wallets and social logins to create accounts.
 - [Safe](https://docs.safe.global/getting-started/readme): Safe allows complex multi-sig setups, simple authentication, and onramping.
 - [Pimlico](https://pimlico.notion.site/Product-Directory-5d92fe60243b4c5aac6650de390e7cb3): Pimlico tracks several products around account abstraction and it is worthwhile checking out the rapid and new developments in this space.
 

docs/docs/learn/builder-guides/hello-bitcoin/index.mdx

@@ -531,7 +531,7 @@ contract TestLightRelay is LightRelay {
 <Tabs groupId="dev-env">
   <TabItem value="foundry" label="Foundry">
 
-To compile the contract run the followling command:
+To compile the contract run the following command:
 
 ```shell
 forge build
@@ -684,7 +684,7 @@ At this point, your smart contract is ready to be used, but we can go a step fur
 
 5. Click on the "Code" tab and click on "Verify & Publish" button.
 
-6. Now you should be presented we a set of possilities for verifying you published contract, but we will proceed with "Via flattened source code".
+6. Now you should be presented we a set of possibilities for verifying you published contract, but we will proceed with "Via flattened source code".
 
 7. Fill the form with the specific information about the contract and how it was deployed. Make sure every field is correctly populated before submitting. Any incorrect field will lead to a failed verification. After submitting, the verification might take a couple of minutes.
 

docs/docs/learn/reference/research.md

@@ -83,7 +83,7 @@ We provide the first systematic exposition of cross-chain communication protocol
 </details>
 
 - **Zamyatin A**, Al-Bassam M, Zindros D, Kokoris-Kogias E, Moreno-Sanchez P, Kiayias A, Knottenbelt WJ
-- Financial Cyprography and Data Security 2021
+- Financial Cryptography and Data Security 2021
 - In collaboration with Imperial College London, UCL, IOHK, EPFL, TU Vienna, University of Athens, University of Edinburgh
 
 ### [TxChain: Efficient Cryptocurrency Light Clients via Contingent Transaction Aggregation](https://eprint.iacr.org/2020/580.pdf)
@@ -95,7 +95,7 @@ Cryptocurrency light- or simplified payment verification (SPV) clients allow nod
 
 Recently, two improved sublinear light clients were proposed: to validate the blockchain, NIPoPoWs and FlyClient only download a polylogarithmic number of block headers, sampled at random. The actual verification of payments, however, remains costly: for each verified transaction, the corresponding block must too be downloaded. This yields NIPoPoWs and FlyClient only effective under low transaction volumes.
 
-We present TxChain, a novel mechanism to maintain efficiency of light clients even under high transaction volumes. Specifically, we introduce the concept of contingent transaction aggregation, where proving inclusion of a single contingent transaction implicitly proves that n other transactions exist in the blockchain. To verify n payments, TxChain requires a only single transaction in the best (n≤c), and n/c+logc(n) transactions in the worst case (n>c). We deploy TxChain on Bitcoin without consensus changes and implement a soft fork for Ethereum. To demonstrate effectiveness in the cross-chain setting, we implement TxChain as a smart contract on Ethereum to efficiently verify Bitcoin payments.
+We present TxChain, a novel mechanism to maintain efficiency of light clients even under high transaction volumes. Specifically, we introduce the concept of contingent transaction aggregation, where proving inclusion of a single contingent transaction implicitly proves that n other transactions exist in the blockchain. To verify n payments, TxChain requires only a single transaction in the best (n≤c), and n/c+logc(n) transactions in the worst case (n>c). We deploy TxChain on Bitcoin without consensus changes and implement a soft fork for Ethereum. To demonstrate effectiveness in the cross-chain setting, we implement TxChain as a smart contract on Ethereum to efficiently verify Bitcoin payments.
 
 </details>
 

docs/docs/learn/user-guides/bob-stake/index.md

@@ -15,7 +15,7 @@ All you need is a Bitcoin wallet with some BTC to send and an EVM-compatible wal
 
 ## Bonus Spice Points with Intract
 
-You can harvest extra Spice by competing any of these [Intract Campaign](https://www.intract.io/explore?query=BOB&hideCompleted=true&hideExpired=true&sortBy=rankingB&entity_type=CAMPAIGN) tasks with BOB Stake.
+You can harvest extra Spice by completing any of these [Intract Campaign](https://www.intract.io/explore?query=BOB&hideCompleted=true&hideExpired=true&sortBy=rankingB&entity_type=CAMPAIGN) tasks with BOB Stake.
 
 | Task Name          | Description                                                         | Reward                        |
 | ------------------ | ------------------------------------------------------------------- | ----------------------------- |