typo edits

Author: varnarmat

lib/ethereum/README.md

@@ -125,7 +125,7 @@ Don’t see a client or client combination you would like supported? Open a GitH
     - Navigate to [CloudWatch service](https://console.aws.amazon.com/cloudwatch/) (make sure you are in the region you have specified for `AWS_REGION`)
     - Open `Dashboards` and select `eth-sync-node-<your-eth-client-combination>` from the list of dashboards.
 
-4. Once the initial synchronization is done, you should be able to access the RPC API of that node from within the same VPC. The RPC port is not exposed to the Internet. Tun the following query against the private IP of the single RPC node you deployed:
+4. Once the initial synchronization is done, you should be able to access the RPC API of that node from within the same VPC. The RPC port is not exposed to the Internet. Turn the following query against the private IP of the single RPC node you deployed:
 
 ```bash
    INSTANCE_ID=$(cat single-node-deploy.json | jq -r '..|.node-instance-id? | select(. != null)')
@@ -160,7 +160,7 @@ The result should be like this (the actual balance might change):
 
 Once synchronization process is over, the script will automatically stop both clients and copy all the contents of the `/data` directory to your snapshot S3 bucket. That may take from 30 minutes to about 2 hours. During the process on the dashboard you will see lower CPU and RAM utilization but high data disc throughput and outbound network traffic. The script will automatically start the clients after the process is done.
 
-Note: the snapshot backup process will automatically run ever day at midnight time of the time zone were the sync node runs. To change the schedule, modify `crontab` of the root user on the node's EC2 instance.
+Note: the snapshot backup process will automatically run ever day at midnight of the time zone were the sync node runs. To change the schedule, modify `crontab` of the root user on the node's EC2 instance.
 
 3. Configure and deploy 2 RPC Nodes
 
@@ -201,7 +201,7 @@ The result should be like this (the actual balance might change):
 
 ### Clearing up and undeploying everything
 
-1. Undeploy RPC Nodes, Sync Nodes and Comon components
+1. Undeploy RPC Nodes, Sync Nodes and Common components
 
 ```bash
    # Setting the AWS account id and region in case local .env file is lost