Update connect-node.md (#525)

Correcting typos (header and instructions)

docs/subquery_network/node_operators/rpc_providers/connect-node.md

@@ -1,18 +1,18 @@
-# Connect your an RPC Endpoint
+# Connect your RPC Endpoint
 
 Node Operators can run either data indexing projects or RPC endpoints for the network (or both). If you instead want to sync a data indexing project, please follow the instructions [here](../indexers/index-project.md).
 
 :::info Connect any RPC
-The SubQuery Network does not control how your run the underlying RPC endpoint to the Network, only that you connect and announce a standard EVM endpoint that is able to consume public queries.
+The SubQuery Network does not control how you run the underlying RPC endpoint to the Network, only that you connect and announce a standard EVM endpoint that is able to consume public queries.
 
-This means you can run existing RPC endpoint used for other purposes (includng other decentralised RPC networks) to the SubQuery Network.
+This means you can run existing RPC endpoint used for other purposes (including other decentralised RPC networks) to the SubQuery Network.
 :::
 
 ## Prerequisites
 
-This guide assumes you are already a running an RPC node that is publicly available on a known IP address/port.
+This guide assumes you are already running an RPC node that is publicly available on a known IP address/port.
 
-For example with Etheruem, it can any client (geth or erigon etc), and it is listening on a known address and port (in the examples below our node is listening on `192.168.1.100:8545`).
+For example with Etheruem, it can be any client (geth or erigon etc), and it is listening on a known address and port (in the examples below our node is listening on `192.168.1.100:8545`).
 
 Please consult the relevant guides for how to run an RPC node on each network, for example this is the guide for [Geth on Ethereum](https://geth.ethereum.org/docs/getting-started), and [Base](https://docs.base.org/tutorials/run-a-base-node/).
 
@@ -28,15 +28,15 @@ Enter the project deployment ID when adding the new project, in our case, it is
 
 ## 2. Connect your local RPC node
 
-Input the public endpoint of your local node, then backend will run some verification on the endpoint to check whether it matches the manifest of the project, e.g chainId, node type, localness.
+Input the public endpoint of your local node, then the backend will run some verification on the endpoint to check whether it matches the manifest of the project, e.g chainId, node type, localness.
 
-Be aware that coordinator service runs in docker, so localhost doesn't work like it runs outside of docker. You should use the internal ip address to connect to the node, or `host.docker.internal` which points to the host localhost.
+Be aware that the coordinator service runs in docker, so localhost doesn't work like it runs outside of docker. You should use the internal ip address to connect to the node, or `host.docker.internal` which points to the host localhost.
 
 ![Connect local node](/assets/img/network/rpc_connect_node.png)
 
 ## 3. Go Online
 
-Click `Go Online`, which will then trigger your wallet to sign a transaction, then your RPC is announced online and is available to query.
+Click `Go Online`, which will then trigger your wallet to sign a transaction. Then your RPC is announced online and is available to query.
 
 ## 4. Allocate SQT to the Project and Monitor
 
@@ -48,5 +48,5 @@ Monitor your eligibility for rewards from the Admin Portal, if your node is out
 
 Congratulations! You have successfully synced your SubQuery RPC Endpoint.
 
-- If you encounter any trouble while running the the Node Operator service, please visit [Troubleshooting](../setup/troubleshooting.md)) and find all your solutions in one place.
+- If you encounter any trouble while running the Node Operator service, please visit [Troubleshooting](../setup/troubleshooting.md)) and find all your solutions in one place.
 - Find the list of [FAQs](../setup/faq.md), and resolve your query.