Fix typos (#423)

* Fix: typo

* Fix: typo

* Fix: typo

* Fix: typo

* Fix: typo

* Fix: typo

---------

Co-authored-by: acolytec3 <17355484+acolytec3@users.noreply.github.com>

DEVNET.md

@@ -18,7 +18,7 @@ Notes:  The nodes started by the script have a JSON-RPC server enabled.  The por
 ```sh
 npx ts-node scripts/seeder.ts --rpcPort=8546 --numBlocks=[number of blocks to seed into network] --sourceFile="[path/to/json/file/with/block/data.json]" --numNodes=[number of nodes in devnet (same as above)]
 ```
-This will load the first `numBlocks` blocks from your `sourceFile` to the the node with the `rpcPort` specified.
+This will load the first `numBlocks` blocks from your `sourceFile` to the node with the `rpcPort` specified.
 
 3. If all goes well, you should see the nodes start to connect with one another
 
@@ -48,4 +48,4 @@ scrape_configs:
 
     static_configs:
       - targets: ["localhost:5051"]
-```
+```

README.md

@@ -2,7 +2,7 @@
 
 This monorepo comprises a suite of tools **currently in development** to allow dapps, wallet providers, and really any Javascript based Ethereum application to connect into the Portal Network once development is complete and the Portal Network is live. 
 
-## Prequisites
+## Prerequisites
 
 Node v16+, NPM v7+
 

packages/browser-client/docs/mobile.md

@@ -23,7 +23,7 @@ The nice part of this for our purposes is that the React web app is the same cod
 ## Debugging the mobile app
 
 There are a couple of ways to debug Android apps but far and away the easiest is:
- - Run `npx cap open android` from `[directory root]/packages/browser-client` and then select the "Run" tab on the very bottom left of the Android Studio UI and it wll show you all of the debug logs from the app.
+ - Run `npx cap open android` from `[directory root]/packages/browser-client` and then select the "Run" tab on the very bottom left of the Android Studio UI and it will show you all of the debug logs from the app.
 
  ## Local development notes
 

packages/portalnetwork/README.md

@@ -9,7 +9,7 @@ See [Architecture](./ARCHITECTURE.md) for architectural concepts
 
 ## Routing Table Management
 
-The Portal Network module currently supports two overlay routing tables for use with tbe below two subnetworks:
+The Portal Network module currently supports two overlay routing tables for use with the below two subnetworks:
 - State Network
 - History Network
 
@@ -34,4 +34,4 @@ Content for the history network is stored in the DB as key/value pairs consistin
 - `value` -- hex string encoded representation of the RLP serialized content (block header, block body, receipt)
 # Acknowledgements
 
-[Chainsafe's `discv5` implementation](https://github.com/ChainSafe/discv5) without which none of this would be possible
+[Chainsafe's `discv5` implementation](https://github.com/ChainSafe/discv5) without which none of this would be possible

packages/portalnetwork/docs/README.md

@@ -11,7 +11,7 @@ See [Architecture](./ARCHITECTURE.md) for architectural concepts
 
 ## Routing Table Management
 
-The Portal Network module currently supports two overlay routing tables for use with tbe below two subnetworks:
+The Portal Network module currently supports two overlay routing tables for use with the below two subnetworks:
 - State Network
 - History Network
 

packages/proxy/README.md

@@ -20,7 +20,7 @@ The proxy strips this prefix from the message payload and forwards the remaining
 
 #### UDP -> Websocket forwarding
 
-Any message received at a UDP port are forwarded to the corresponding websocket client unmodified.
+Any message received at a UDP port is forwarded to the corresponding websocket client unmodified.
 ## Usage
 
 To run a proxy on a local network, run `npm run start`.