Editorial mdlint and vale edits for HowTo/Deploy directory

docs/Concepts/Pruning.md

@@ -4,9 +4,11 @@ description: Pruning
 # Pruning
 
 !!! caution 
-    Do not use pruning in Hyperledger Besu v1.4.0. Pruning has a [known bug](https://github.com/hyperledger/besu/blob/master/CHANGELOG.md#known-issues).
-
-    If using fast sync in v1.4.0, explicitly disable pruning using [`--pruning-enabled=false`](../Reference/CLI/CLI-Syntax.md#pruning-enabled). 
+    Do not use pruning in Hyperledger Besu v1.4.0. Pruning has a
+    [known bug](https://github.com/hyperledger/besu/blob/master/CHANGELOG.md#known-issues).
+
+    If using fast sync in v1.4.0, explicitly disable pruning using
+    [`--pruning-enabled=false`](../Reference/CLI/CLI-Syntax.md#pruning-enabled). 
 
 Use pruning to reduce storage required for the world state. Pruning removes state trie nodes that
 are not required.

docs/HowTo/Deploy/Ansible.md

@@ -1,13 +1,17 @@
-title: Deploy Hyperledger Besu with Ansible 
-description: Deploying Hyperledger Besu with Ansible role on Galaxy 
-<!--- END of page meta data -->
+---
+title: Deploy Hyperledger Besu with Ansible
+description: Deploying Hyperledger Besu with Ansible role on Galaxy
+---
 
-Use the [Hyperledge Besu role](https://galaxy.ansible.com/pegasyseng/hyperledger_besu) published on Galaxy to deploy Besu using Ansible. 
+# Deploying Hyperledger Besu with Ansible
 
-Refer to the [Readme](https://galaxy.ansible.com/pegasyseng/hyperledger_besu) for details.  
+To deploy Hyperledger Besu using Ansible, use the
+[Hyperledge Besu role](https://galaxy.ansible.com/pegasyseng/hyperledger_besu) published on Galaxy.
+
+For more information, see the
+[Ansible readme](https://galaxy.ansible.com/pegasyseng/hyperledger_besu).
 
 !!! important
-    We strongly recommend automating network creation. Automating makes updates easy and ensures your
-    configuring is in sync across the network. 
-
-    Use the [Besu role](https://galaxy.ansible.com/pegasyseng/hyperledger_besu) for automation of network creation. 
+
+    We strongly recommend automating network creation. Automating makes updates easier and ensures
+    your configuration is synchronized across the network.

docs/HowTo/Deploy/Bootnodes.md

@@ -1,45 +1,57 @@
-description: Configuring bootnodes in production networks    
-<!--- END of page meta data -->
+---
+description: Configuring bootnodes in production networks
+---
 
-# Configuring Bootnodes in a Production Network 
+# Configuring bootnodes in a production network
 
-A network must have at least one operating bootnode. To allow for continuity in the event of failure, 
-configure two or more bootnodes. 
+A network must have at least one operating bootnode. To allow for continuity in the event of
+failure, configure two or more bootnodes.
 
-We do not recommend putting bootnodes behind a load balancer since the [enode](../../Concepts/Node-Keys.md#enode-url) is 
-tied to the node's public key, IP address, and discovery ports. Any changes to the enode of the bootnode prevents other nodes 
-from being able to establish a connection with the bootnode. This is why we recommend putting more bootnodes on the network itself.
+We do not recommend putting bootnodes behind a load balancer because the
+[enode](../../Concepts/Node-Keys.md#enode-url) relates to the node public key, IP address, and
+discovery ports. Any changes to a bootnode enode prevents other nodes from being able to establish
+a connection with the bootnode. This is why we recommend putting more bootnodes on the network
+itself.
 
-To ensure that the bootnode's enode does not change when recovering from a complete bootnode failure: 
+To ensure that a bootnode enode does not change when recovering from a complete bootnode failure:
 
-1. Create the [node key pair](../../Concepts/Node-Keys.md) (that is, the private and public key) before starting the bootnode.
-1. When creating bootnodes in the cloud (for example, AWS, Azure), attempt to assign a static IP to them. If your network is: 
-
-    * Publicly accessible, assign an elastic IP. 
-
-    * Internal only, specify a private IP address when you create the instance and record this IP address. 
+1. Create the [node key pair](../../Concepts/Node-Keys.md) (that is, the private and public key)
+   before starting the bootnode.
+1. When creating bootnodes in the cloud (for example, AWS and Azure), attempt to assign a static IP
+   address to them. If your network is:
 
-We recommend that the bootnode configuration be stored under source control. 
+    * Publicly accessible, assign an elastic IP.
+    * Internal only, specify a private IP address when you create the instance and record this IP
+      address.
 
-## Specifying Bootnodes 
+We recommend that you store the bootnode configuration under source control.
 
-To allow for failure, specify all bootnodes on the command line (even to the bootnodes themselves). 
+## Specifying bootnodes
 
-!!! example 
-    If your network has two bootnodes, pass the following parameter to all nodes, including the bootnodes. 
-
-    `--bootnodes=enode://<publicKeyBootnode1>@<ipBootnode1>:30303,<publicKeyBootnode2>@<ipBootnode2>:30303`
-
-!!! tip 
-    Having each bootnode list the other bootnodes increases the speed of discovery. Nodes ignore their own 
-    enode in the bootnodes list so it's not required to specify different bootnode lists to the bootnodes 
-    themselves.  
+To allow for failure, specify all bootnodes on the command line (even to the bootnodes themselves).
 
-## Adding and Removing Bootnodes 
+!!! example
 
-Adding new bootnodes is a similar process to creating bootnodes. Once the bootnodes have been created and added to the network,
-update the [`--bootnodes`](../../Reference/CLI/CLI-Syntax.md#bootnodes) command line option for each node to include the new bootnodes. 
+    If your network has two bootnodes, pass the following parameter to all nodes, including the
+    bootnodes.
 
-When bootnodes are added, running nodes don’t need to be restarted. Updating the [`--bootnodes`](../../Reference/CLI/CLI-Syntax.md#bootnodes)
-option means the next time they are restarted (for example, when [upgrading](../Upgrade/Upgrade-Node.md)), 
-the node connects to the new bootnodes.  
+    ```bash
+    --bootnodes=enode://<publicKeyBootnode1>@<ipBootnode1>:30303,<publicKeyBootnode2>@<ipBootnode2>:30303
+    ```
+
+!!! tip
+
+    Having each bootnode list the other bootnodes increases the speed of discovery. Nodes ignore
+    their own enode in the bootnodes list so it is not required to specify different bootnode lists
+    to the bootnodes themselves.
+
+## Adding and removing bootnodes
+
+Adding new bootnodes is a similar process to creating bootnodes. After creating the bootnodes and
+adding them to the network,update the [`--bootnodes`](../../Reference/CLI/CLI-Syntax.md#bootnodes)
+command line option for each node to include the new bootnodes.
+
+When adding bootnodes, you do not need to restart running nodes. By updating the
+[`--bootnodes`](../../Reference/CLI/CLI-Syntax.md#bootnodes) option, the next time you restart the
+nodes (for example, when [upgrading](../Upgrade/Upgrade-Node.md)), the nodes connect to the new
+bootnodes.

docs/HowTo/Deploy/Cloud.md

@@ -1,8 +1,12 @@
-description: Deploying Besu to cloud  
-<!--- END of page meta data -->
+---
+description: Deploying Besu to the cloud
+---
 
-When deploying to the cloud: 
+# Deploying Hyperledger Besu to the cloud
 
-* Ensure you have enough spread across Availability Zones (AZs) and Regions especially for bootnodes and validators.
-* If your network is a multi-region network, consider using VPC Peering  to reduce latency.
+When deploying Hyperledger Besu to the cloud:
+
+* Ensure you have enough spread across Availability Zones (AZs) and Regions, especially for
+  bootnodes and validators.
+* If your network is a multi-region network, consider using VPC Peering to reduce latency.
 * Where required, use VPNs to connect to your on premise systems, or single private chains.

docs/HowTo/Deploy/Kubernetes.md

@@ -1,11 +1,18 @@
-title: Deploy a Hyperledger Besu Private Network with Kubernetes 
-description: Deploying Hyperledger Besu with Kubernetes 
-<!--- END of page meta data -->
+---
+title: Deploy a Hyperledger Besu private network with Kubernetes
+description: Deploying Hyperledger Besu with Kubernetes
+---
 
-Use the [reference implementations](https://github.com/PegaSysEng/besu-kubernetes) to install private networks using Kubernetes(K8s). Reference implementations are available using:
+# Deploying Hyperledger Besu with Kubernetes
+
+Use the [reference implementations](https://github.com/PegaSysEng/besu-kubernetes) to install
+private networks using Kubernetes(K8s). Reference implementations are available using:
 
 * [Helm](https://github.com/PegaSysEng/besu-kubernetes/tree/master/helm)
-* [Helmfile](https://github.com/PegaSysEng/besu-kubernetes/tree/master/helmfile/private-network-ibft-automated)
-* [kubectl](https://github.com/PegaSysEng/besu-kubernetes/tree/master/kubectl)
+* [Helmfile]
+* [kubectl](https://github.com/PegaSysEng/besu-kubernetes/tree/master/kubectl).
+
+Familiarize yourself with the reference implementations and customize them for your requirements.
 
-Familiarize yourself with the reference implementations and customize them for your requirements.
+<!-- Links -->
+[Helmfile]: https://github.com/PegaSysEng/besu-kubernetes/tree/master/helmfile/private-network-ibft-automated

docs/HowTo/Deploy/Lite-Block-Explorer.md

@@ -1,101 +1,110 @@
+---
 description: Ethereum Lite Explorer
-<!--- END of page meta data -->
+---
 
-Use the [Alethio Ethereum Lite Explorer](https://lite-explorer.aleth.io/) to explore blockchain data 
-at the block, transaction, and account level.
-
-The Alethio Ethereum Lite Explorer is a web application that connects to any Ethereum 
-JSON-RPC enabled node. No online server, hosting, or trusting third parties to display the blockchain
-data is required. 
+# Alethio Ethereum Lite Explorer
+
+Use the [Alethio Ethereum Lite Explorer](https://lite-explorer.aleth.io/) to explore blockchain
+data at the block, transaction, and account level.
+
+The Alethio Ethereum Lite Explorer is a web application that connects to any Ethereum
+JSON-RPC-enabled node. The Explorer does not require an online server, hosting, or trusting third
+parties to display the blockchain data.
 
 ## Prerequisites
 
-[Docker](https://docs.docker.com/install/) or [Node.js](https://nodejs.org/)
+[Docker](https://docs.docker.com/install/) or [Node.js](https://nodejs.org/).
 
 !!! tip
-    Using Docker is the easiest way to get started using the Ethereum Lite Explorer with Hyperledger 
-    Besu if you do not have Node.js installed.
 
-## Run Using Docker
+    Using Docker is the easiest way to get started using the Ethereum Lite Explorer with
+    Hyperledger Besu if you do not have Node.js installed.
+
+## Run using Docker
 
-To run the Ethereum Lite Explorer using the Docker image: 
+To run the Ethereum Lite Explorer using the Docker image:
 
-1. Start Besu with the [`--rpc-http-enabled`](../../Reference/CLI/CLI-Syntax.md#rpc-http-enabled) option. 
+1. Start Besu with the [`--rpc-http-enabled`](../../Reference/CLI/CLI-Syntax.md#rpc-http-enabled)
+   option.
+
+    !!! example
 
-    !!! example 
-
         To run Besu in development mode:
-        
+
         ```bash
         besu --network=dev --miner-enabled --miner-coinbase=0xfe3b557e8fb62b89f4916b721be55ceb828dbd73 --rpc-http-cors-origins="all" --host-whitelist="*" --rpc-http-enabled --data-path=/tmp/tmpDatdir
         ```
 
-1. Run the `alethio/ethereum-lite-explorer` Docker image specifying the JSON-RPC HTTP URL (`http://localhost:8545` in this example): 
+1. Run the `alethio/ethereum-lite-explorer` Docker image specifying the JSON-RPC HTTP URL
+   (`http://localhost:8545` in this example):
 
     ```bash
     docker run --rm -p 8080:80 -e APP_NODE_URL=http://localhost:8545 alethio/ethereum-lite-explorer
     ```
 
-1. Open [http://localhost:8080](http://localhost:8080) in your browser to view the Lite Explorer. 
+1. Open [http://localhost:8080](http://localhost:8080) in your browser to view the Lite Explorer.
 
     ![Ethereum Lite Explorer](../../images/explorer.png)
 
     !!! note "Default HTTP port"
+
         We are using port 8080 to run the Ethereum Lite Explorer so
-        the [EthStats Lite](Lite-Network-Monitor.md) can use port 80. You can then run 
-        both at the same time. 
+        the [EthStats Lite](Lite-Network-Monitor.md) can use port 80, allowing you to run both at
+        the same time.
+
+## Install and run with Node.js
 
-## Install and Run with Node.js
+1. Clone the `ethereum-lite-explorer` repository:
 
-1. Clone the `ethereum-lite-explorer` repository: 
-
     ```bash
     git clone https://github.com/Alethio/ethereum-lite-explorer.git
     ```
 
-1. Change into the `ethereum-lite-explorer` directory: 
+1. Change into the `ethereum-lite-explorer` directory:
+
    ```bash
    cd ethereum-lite-explorer
    ```
 
-1. Install npm packages: 
+1. Install npm packages:
 
     ```bash
     npm install
     ```
 
-1. Copy the sample config: 
+1. Copy the sample configaration:
 
-    ```bash 
+    ```bash
     cp config.default.json config.dev.json
     ```
-
-1. Update the `config.dev.json` file: 
 
-    * Set `APP_NODE_URL` to the JSON-RPC HTTP URL of your node (`http://localhost:8545` in this example)
-
-    * Remove other environment variables. 
-
-1. In another terminal, start Besu with the [`--rpc-http-enabled`](../../Reference/CLI/CLI-Syntax.md#rpc-http-enabled) option. 
+1. Update the `config.dev.json` file:
+
+    * Set `APP_NODE_URL` to the JSON-RPC HTTP URL of your node (`http://localhost:8545` in this
+      example).
+    * Remove other environment variables.
+
+1. In another terminal, start Besu with the
+   [`--rpc-http-enabled`](../../Reference/CLI/CLI-Syntax.md#rpc-http-enabled) option.
+
+    !!! example
 
-    !!! example 
-
         To run Besu in development mode:
-        
+
         ```bash
         besu --network=dev --miner-enabled --miner-coinbase=0xfe3b557e8fb62b89f4916b721be55ceb828dbd73 --rpc-http-cors-origins="all" --host-whitelist="*" --rpc-http-enabled --data-path=/tmp/tmpDatdir
         ```
-        
-1. In the `ethereum-lite-explorer` directory, run the Lite Explorer in development mode: 
+
+1. In the `ethereum-lite-explorer` directory, run the Lite Explorer in development mode:
 
     ```bash
     npm run build
     npm run start
-    ```  
-   
-1. A browser window displays the Ethereum Lite Explorer (http://localhost:3000/).
-   
-## Lite Block Explorer Documentation 
-
-See the Ethereum Lite Explorer [GitHub repository](https://github.com/Alethio/ethereum-lite-explorer) 
-for more documentation, including details on deploying it. 
+    ```
+
+A browser window displays the Ethereum Lite Explorer (http://localhost:3000/).
+
+## Lite Block Explorer documentation
+
+For more information about Ethereum Lite Explorer, including details on how to deploy it, see the
+[GitHub repository](https://github.com/Alethio/ethereum-lite-explorer).