Docs fix spelling issues (#1719)

docs/private-networks/concepts/permissioning/index.md

@@ -14,7 +14,7 @@ A permissioned network enables node permissioning and account permissioning, all
 
 In peer-to-peer networks, node permissioning enforces rules on nodes you control.
 
-Permissioning requires a distributed network of trust across the network where participants agree to follow the rules. One bad actor can decide not to follow the rules. Nodes can take action to prevent the bad actor adding to the chain but they cannot prevent the bad actor from allowing access to the chain.
+Permissioning requires a distributed network of trust across the network where participants agree to follow the rules. One bad actor can decide not to follow the rules. Nodes can take action to prevent the bad actor from adding to the chain but they cannot prevent the bad actor from allowing access to the chain.
 
 Besu also implements [privacy](../privacy/index.md).
 
@@ -44,15 +44,15 @@ You can specify permissioning [locally](#local) or [onchain](#onchain).
 
 [Local permissioning](../../how-to/use-permissioning/local.md) works at the node level. Each node in the network has a [permissions configuration file].
 
-Local permissioning affects your node but not the rest of the network. Use local permissioning to restrict use of your node (that is, the resources under your control). For example, customers able to access your node.
+Local permissioning affects your node but not the rest of the network. Use local permissioning to restrict use of your node (that is, the resources under your control). For example, customers are able to access your node.
 
 Local permissioning does not require coordination with the rest of the network and you can act immediately to protect your node. Your rules are not enforced in blocks produced by other nodes.
 
 ### Onchain
 
 [Onchain permissioning](onchain.md) works through a smart contract on the network. Specifying permissioning onchain enables all nodes to read and update permissioning configuration from one location.
 
-Onchain permissioning requires coordination to update the rules. The network might not be able to act immediately (for example, the smart contract might enforce a minimum of number of votes before changing permissioning rules).
+Onchain permissioning requires coordination to update the rules. The network might not be able to act immediately (for example, the smart contract might enforce a minimum number of votes before changing permissioning rules).
 
 When you update onchain permissioning, the update applies across the network and new blocks abide by the updated rules. For example, blocked accounts can no longer add transactions to the chain.
 

docs/private-networks/concepts/privacy/flexible-privacy.md

@@ -20,7 +20,7 @@ Flexible privacy groups are an early access feature. Don't use in production net
 
 The flexible privacy group interfaces might change between releases. There might not be an upgrade path from flexible privacy groups created using v1.5 or earlier to enable use of flexible privacy group functionality in future versions.
 
-We don't recommended creating flexible privacy groups in a chain with existing [offchain privacy groups](privacy-groups.md).
+We don't recommend creating flexible privacy groups in a chain with existing [offchain privacy groups](privacy-groups.md).
 
 :::
 

docs/private-networks/how-to/configure/free-gas.md

@@ -116,7 +116,7 @@ If zero base fee is enabled, you cannot specify a value for [`--tx-pool-price-bu
 
 ## Configure free gas in Hardhat
 
-If using Hardhat to develop on your free gas network, you also need to configure free gas in Hardhat.
+If using Hardhat to develop your free gas network, you also need to configure free gas in Hardhat.
 
 Like setting block and contract size limits to their maximum values for Besu, set the transaction gas limit in Hardhat to the maximum possible.
 
@@ -154,4 +154,4 @@ Update the `hardhat.config.js` file:
         optimizer: {...},
       },
     },
-   ```
+   ```