Fix typos

content/build/smart-contract-environments/hardhat.md

@@ -1,6 +1,6 @@
 ---
 title: Solidity & Vyper – Hardhat
-menuTitle: Solidty & Vyper – Hardhat
+menuTitle: Solidity & Vyper – Hardhat
 aliases:
   - /apps/smart-contract-environments/hardhat
 description: Hardhat is a highly extensible and modular TypeScript-based Ethereum development environment, with a mature Solidity debugging experience.
@@ -30,7 +30,7 @@ require("@nomicfoundation/hardhat-toolbox");
 
 const PORTAL_ID = "<PORTAL-ID>";
 
-// Replace these privates key with your respective account private key
+// Replace these private keys with your respective account private key
 // To export your private key from Metamask, open Metamask and
 // go to Account Details > Export Private Key
 // Beware: NEVER put real Ether into testing accounts

content/learn/protocol-parameters.md

@@ -137,7 +137,7 @@ The DAO may manually adjust an application's `MaxRelays` at the time of staking
 
 ## PoS (Node) Module
 
-These parameters relate to [staked nodes](/learn/economics/nodes) on the networ, including [how rewards are calculated](/learn/economics/monetary-policy).
+These parameters relate to [staked nodes](/learn/economics/nodes) on the network, including [how rewards are calculated](/learn/economics/monetary-policy).
 
 ### BlocksPerSession
 

content/learn/vision.md

@@ -51,7 +51,7 @@ We posit that application-specific blockchains like Pocket Network have the abil
 Pocket achieves this through an incentive design that rewards Service Nodes for collectively achieving economies of scale:
 
 1. Load balancing at the protocol level incentivizes decentralization and minimizes the need for buffers
-2. Staking and inflation enables more efficient resource allocation
+2. Staking and inflation enable more efficient resource allocation
 3. Low marginal costs reduce barriers to entry, allowing anyone to participate at any scale
 
 ### Load balancing at the protocol level
@@ -72,7 +72,7 @@ Pocket's staking and inflation mechanisms enable a more efficient resource alloc
 
 ### Low marginal costs and participation
 
-The marginal cost of running an individual Service Node is only as high as your electricity and bandwidth costs, ensuring a low barrier to entry for new Service Node operators. Because work is load balanced evenly across the protocol, the stake, size, or capabilities of the Service Node does not increase the probability of receiving work, which enables hobbyists and small providers to participate and contribute alongside major infrastructure providers. As smaller Service Node operators scale up, they can then choose to bear the costs of hardware, equipment, and salaries needed to add more Service Nodes to their operation.
+The marginal cost of running an individual Service Node is only as high as your electricity and bandwidth costs, ensuring a low barrier to entry for new Service Node operators. Because work is load balanced evenly across the protocol, the stake, size, or capabilities of the Service Node do not increase the probability of receiving work, which enables hobbyists and small providers to participate and contribute alongside major infrastructure providers. As smaller Service Node operators scale up, they can then choose to bear the costs of hardware, equipment, and salaries needed to add more Service Nodes to their operation.
 
 While the bulk of work will most likely be serviced by professional infrastructure providers, Pocket also enables a long tail of individuals to participate and increase the resilience of the protocol, with potential for upward mobility for those who choose to purchase more Service Nodes.
 

content/node/environment.md

@@ -110,7 +110,7 @@ AppVersion: {{< pocket-version >}}
 {{< /tabs >}}
 
 {{% notice style="info" %}}
-You can find the latest release on the [Pocket Core GitHub pagee](https://github.com/pokt-network/pocket-core/releases).
+You can find the latest release on the [Pocket Core GitHub page](https://github.com/pokt-network/pocket-core/releases).
 {{% /notice %}}
 
 ### Homebrew

content/node/faq.md

@@ -370,7 +370,7 @@ curl -H "Content-Type: application/json" -d '{"height": 4407, "address": "85efd0
 You can verify that there are no transactions associated with that address in block 4406.
 
 {{% notice style="note" %}}
-There isn't a straighforward way to do this natively within Pocket at the moment. You would have to [query all of the transactions for a given block](https://docs.pokt.network/api-docs/pokt/#/api-docs/pokt/operations/block_txs_v1_query_blocktxs_post) and then search through them for the address in question. We plan to make this easier in the future.
+There isn't a straightforward way to do this natively within Pocket at the moment. You would have to [query all of the transactions for a given block](https://docs.pokt.network/api-docs/pokt/#/api-docs/pokt/operations/block_txs_v1_query_blocktxs_post) and then search through them for the address in question. We plan to make this easier in the future.
 {{% /notice %}}
 
 Finally, you can see that this address was the proposer for block 4406:

content/node/setup.md

@@ -67,7 +67,7 @@ Learn more about [securely managing your POKT accounts](/pokt/).
 To stake a node in Pocket Network, the account must have a balance above the minimum stake, which is 15,000 POKT (or 15,000,000,000 uPOKT).
 
 {{% notice style="warning" %}}
-We recommend staking more than the absolute minimum node stake of 15,000 POKT (such as 15,100) as a reasonable buffer against operational slashes which can occur on even properly configured nodes as well as misconfigured and misbehaving ones. If slashes cause your node stake to drop below 15,000, you node will be forcibly unstaked.
+We recommend staking more than the absolute minimum node stake of 15,000 POKT (such as 15,100) as a reasonable buffer against operational slashes which can occur on even properly configured nodes as well as misconfigured and misbehaving ones. If slashes cause your node stake to drop below 15,000, your node will be forcibly unstaked.
 {{% /notice %}}
 
 Send POKT with the following command:

content/node/trustlessStaking.md

@@ -27,7 +27,7 @@ Created by the Node Operator, this address is used to manage and run your node.
 for editing the Domain and Chains with the Output Address. However, the Operator Address cannot control the funds; only the Output Address has this capability.
 
 
-The very first stake initiated from the output address establishes a link between the operator address and the output address.The Node Operator can then start running your node using the operator address. Any node rewards will be sent to the output address. Additionally, if unstaked, the unstaked funds will also go to the output address. An output address can be linked to multiple operator addresses.
+The very first stake initiated from the output address establishes a link between the operator address and the output address. The Node Operator can then start running your node using the operator address. Any node rewards will be sent to the output address. Additionally, if unstaked, the unstaked funds will also go to the output address. An output address can be linked to multiple operator addresses.
 
 ## Introduction
 
@@ -68,7 +68,7 @@ Notice there is a balance of 36.57 present. The node requires some POKT to pay f
 ## Preparing the Output Address
 
 1. Login to your  output address using the pocket official wallet below. Note down the password used to create the wallet. https://wallet.pokt.network/
-2. **IMPORTANT:** Backup the keyfile.json using “export keyfile” and the password. Lose this and you will lose your funds. Then send 15011 tokens to this address. 15010 will be staked, leaving one for transaction fees.(Each transaction costs 0.01 POKT at the time this doc is written)
+2. **IMPORTANT:** Backup the keyfile.json using “export keyfile” and the password. Lose this and you will lose your funds. Then send 15011 tokens to this address. 15010 will be staked, leaving one for transaction fees. (Each transaction costs 0.01 POKT at the time this doc is written)
 
 ![](/images/wallet.png)
 
@@ -122,4 +122,4 @@ Yes, the operator can change chains or the service URL; consult your node operat
 Yes, you can reuse the output address for another operator address; rewards and unstaked funds from both operators will be sent to the output address.
 
 **If all rewards end up in the output account, how does the node operator get their reward share?**
-Node operators can't access your rewards; you must send their share manually.
+Node operators can't access your rewards; you must send their share manually.