docs(guides): fix typos on operator, sdk & submitting proofs (#618)

Co-authored-by: Mariano A. Nicolini <mariano.nicolini.91@gmail.com>

Author: cliraa

docs/guides/0_submitting_proofs.md

@@ -21,13 +21,13 @@ The following proof systems are going to be added soon:
 
 ## 1. Import/Create Keystore file
 
-If you already have a keystore file, you can ignore this section and start sending proofs. We give two examples of how to generate one. The first one using Foundry, and the second one using EigenLayerCLI
+If you already have a keystore file, you can ignore this section and start sending proofs. We give two examples of how to generate one. The first one using Foundry, and the second one using EigenLayer CLI
 
 ### Alternative 1: With foundry
 
 You need to have installed [Foundry](https://book.getfoundry.sh/getting-started/installation).
 
-- If you are creating a new account. Create a private key with:
+- If you are creating a new account, create a private key with:
 
     ```bash
     cast wallet new-mnemonic --words 12
@@ -56,7 +56,7 @@ You need to have installed [Foundry](https://book.getfoundry.sh/getting-started/
 
 This will create the ECDSA keystore file in `~/.aligned_keystore/keystore0`
 
-### Alternative 2: With EigenlayerCLI
+### Alternative 2: With EigenLayer CLI
 
 - If you have the EigenLayer CLI installed, the keystore can be generated following [this](https://docs.eigenlayer.xyz/eigenlayer/operator-guides/operator-installation#import-keys) instructions. The key will be stored into `~/.eigenlayer/operator_keys`.
 
@@ -75,15 +75,16 @@ aligned deposit-to-batcher \
 --amount 0.1ether
 ```
 
-This commands allows the usage of the following flags:
+These commands allows the usage of the following flags:
+
 - `--batcher_addr` to specify the address of the Batcher Payment Service smart contract.
 - `--rpc` to specify the rpc url to be used.
 - `--chain` to specify the chain id to be used. Could be holesky or devnet.
 - `--keystore_path` the path to the keystore.
 - `--amount` the amount of ethers to transfer to the Batcher.
 - Note: `--amount` flag parameter must be with the shown format. The amount followed by the `ether` keyword to specify how many ethers you wish to deposit to the Batcher.
 
-After depositing funds, you can verify the Service has correctly received them, executing the following command:
+After depositing funds, you can verify the Service has correctly received them by executing the following command:
 
 ```bash
 aligned get-user-balance \
@@ -92,7 +93,8 @@ aligned get-user-balance \
 --user_addr <user_addr>
 ```
 
-This commands allows the usage of the following flags:
+These commands allows the usage of the following flags:
+
 - `--batcher_addr` to specify the address of the Batcher Payment Service smart contract.
 - `--rpc` to specify the rpc url to be used.
 - `--user_addr` the address of the user that funded the Batcher.

docs/guides/1_SDK.md

@@ -1,7 +1,7 @@
 # Aligned SDK
 
 The Aligned SDK aims to help developers interact with Aligned in a simple way.
-Some of its functionalities include submitting and verify proofs through the Aligned batcher, as well as checks the inclusion of the verified proofs on-chain. This guide provides an overview of the SDK, its installation, usage, and API details.
+Some of its functionalities include submitting and verifying proofs through the Aligned Batcher, as well as checking the inclusion of the verified proofs on-chain. This guide provides an overview of the SDK, its installation, usage, and API details.
 
 You can check the list of supported verifiers [here](../architecture/0_supported_verifiers.md).
 
@@ -46,7 +46,7 @@ pub async fn submit(
 
 ### submit_multiple
 
-Submits mulitple proofs to the batcher to be verified and returns an aligned verification data array.
+Submits multiple proofs to the batcher to be verified and returns an aligned verification data array.
 
 ```rust
 pub async fn submit_multiple(

docs/operator_guides/0_running_an_operator.md

@@ -115,7 +115,7 @@ EigenLayer's guide can be found [here](https://docs.eigenlayer.xyz/eigenlayer/re
 
 ### Option 2
 
-If you have ETH and need to convert it to WETH you can use the following command, that will convert 1 Eth to WETH.
+If you have ETH and need to convert it to WETH you can use the following command, that will convert 1 ETH to WETH.
 Make sure to have [foundry](https://book.getfoundry.sh/getting-started/installation) installed.
 Change the parameter in ```---value``` if you want to wrap a different amount:
 
@@ -126,7 +126,7 @@ cast send 0x94373a4919B3240D86eA41593D5eBa789FEF3848 --rpc-url https://ethereum-
 Here `<private_key>` is the placeholder for the ECDSA key specified in the output when generating your keys with the EigenLayer CLI.
 
 Finally, to end the staking process, you need to deposit into the WETH strategy,
-as shown in the Eigen guide.
+as shown in the EigenLayer guide.
 
 <details>
   <summary>An alternative using the CLI (only when running without docker)</summary>
@@ -139,7 +139,7 @@ as shown in the Eigen guide.
   </summary>
 </details>
 
-If you don't have Holesky Eth, these are some useful faucets:
+If you don't have Holesky ETH, these are some useful faucets:
 
 - [Google Cloud for Web3 Holesky Faucet](https://cloud.google.com/application/web3/faucet/ethereum/holesky)
 - [Holesky PoW Faucet](https://holesky-faucet.pk910.de/)