🐛 typos in the docs (#255)

* fix typo ch00-00-introduction.md

* fix typo ch02-04-katana.md

* fix typo ch02-05-foundry-cast.md

* fix typo ch02-05-testnet-deployment.md

* fix typo ch02-07-01-01-erc20-ui.md

* fix typo ch03-01-01-transactions-lifecycle.md

* fix typo ch03-05-layer-3.md

* fix typo ch03-06-solidity-verifier.md

src/ch00-00-introduction.md

@@ -66,7 +66,7 @@ These are some key features of Starknet:
   (CVM), that allow us to innovate beyond the Ethereum Virtual Machine
   (EVM) and create a new paradigm for decentralized applications.
 
-Here some of them:
+Here are some of them:
 
 - Account Abstraction: Implemented at the protocol level, this
   facilitates diverse signing schemes while ensuring user security and

src/ch02-04-katana.md

@@ -27,7 +27,7 @@ RPC can be obtained from various sources: . To support the
 decentralization of the Network, you can use your own local Starknet
 node. For ease of access, consider using a provider such as
 [Infura](https://docs.infura.io/networks/starknet/how-to) or
-[Alchemy](https://www.alchemy.com/starknet) to get an RPC client. . For
+[Alchemy](https://www.alchemy.com/starknet) to get an RPC client. For
 development and testing, a temporary local node such as `katana` can be
 used.
 

src/ch02-05-foundry-cast.md

@@ -188,7 +188,7 @@ Points to remember:
 3. **`-private-key`** - Private key of the account.
 4. **`-add-profile`** - Though optional, it's pivotal. By enabling **`sncast`** to include the account in your **`Scarb.toml`** file, you can manage multiple accounts, facilitating transactions among them when working with your smart contract using sncast.
 
-Now that we have familiarized ourselves with using a predeployed account, let's proceed to adding a new account.
+Now that we have familiarized ourselves with using a predeployed account, let's proceed to add a new account.
 
 ### Creating and Deploying a New Account to Starknet Devnet
 

src/ch02-05-testnet-deployment.md

@@ -205,7 +205,7 @@ In case you face an error like this:
 
 It means you probably just created a new wallet and it has not been deployed yet. To accomplish this you have to fund your wallet with tokens and transfer tokens to a different wallet address. After this process, search your wallet address on the Starknet explorer. To see the details, go back to [Getting Started](ch01-00-getting-started.md) and find the `Smart Wallet Setup` section.
 
-After the acount descriptor file is generated, you can see the its detalis, run:
+After the acount descriptor file is generated, you can see its details, run:
 
 ```bash
     cat ~/.starkli-wallets/deployer/my_account_1.json

src/ch02-07-01-01-erc20-ui.md

@@ -455,7 +455,7 @@ npm i -g vercel
 
 ```bash
 vercel login
-Continue with Email (or select your preferent login method)
+Continue with Email (or select your preferred login method)
 ```
 
 After entering your email, check your inbox and click on the "Verify" button.

src/ch03-01-01-transactions-lifecycle.md

@@ -5,7 +5,7 @@ This chapter outlines the path of a Starknet transaction from its initiation to
 Starknet processes transactions in distinct steps:
 
 - A transaction starts by being sent to a gateway, a node, which acts as the Mempool.
-- The Sequencer, currently a single service, first validates and the executes the transactions in order.
+- The Sequencer, currently a single service, first validates and then executes the transactions in order.
   - If validated successfully, the status becomes RECEIVED.
   - If not, the status is REJECTED.
   - Successfully executed transactions are applied to the state and marked as ACCEPTED_ON_L2.

src/ch03-05-layer-3.md

@@ -85,7 +85,7 @@ a starting point for building Layer 3 Starknet appchains. This expands
 the possibilities for innovation within the Starknet ecosystem.
 
 Madara’s flexibility allows for the creation of Layer 3 appchains
-optimized for various needs, foe example:
+optimized for various needs, for example:
 
 - Cost-Efficiency: Create an appchain for running a decentralized
   exchange (DEX) with lower fees compared to the public Starknet.

src/ch03-06-solidity-verifier.md

@@ -26,7 +26,7 @@ To illustrate SHARP: Think of commuting by bus. The bus driver, the prover, tran
 
 A Solidity verifier is an L1 smart contract, crafted in Solidity, designed to validate STARK proofs from SHARP (Shared Prover).
 
-### Previous Architecture: Monolothic Verifier
+### Previous Architecture: Monolithic Verifier
 
 Historically, the Solidity Verifier was a monolithic contract, both initiated and executed by the same contract. For illustration, the operator would invoke the `update state` function on the main contract, providing the state to be modified and confirming its validity. Subsequently, the main contract would present the proof to both the verifier and the validium committee. Once they validated the proof, the state would be updated in the main contract.