diff --git a/docs/HowTo/Backup/Backup.md b/docs/HowTo/Backup/Backup.md
index c688a96eb73..bdc6a7c4510 100644
--- a/docs/HowTo/Backup/Backup.md
+++ b/docs/HowTo/Backup/Backup.md
@@ -27,6 +27,9 @@ or `/opt/besu/database` if using the [Besu Docker image](../../HowTo/Get-Started
 The default data location is the directory in which Besu is installed
 or `/opt/besu/database` if using the [Besu Docker image](../../HowTo/Get-Started/Run-Docker-Image.md).
 
+The default data location is the directory in which Besu is installed
+or `/opt/besu/database` if using the [Besu Docker image](../../HowTo/Get-Started/Run-Docker-Image.md).
+
 Having some data reduces the time to synchronise a new node. Periodic backups can be performed of 
 the data directory and the data sent to your preferred backup mechanism. For example, cron job and 
 rsync, archives to cloud such as s3, or `tar.gz` archives. 
@@ -51,4 +54,4 @@ If log messages indicate a corrupt database, the cleanest way to recover is:
 
 ## Finding Peers on Restarting 
 
-The process for finding peers on restarting is the same as [finding peers after upgrading and restarting](../Upgrade/Upgrade-Network.md#finding-peers-on-restarting). 
+The process for finding peers on restarting is the same as [finding peers after upgrading and restarting](../Upgrade/Upgrade-Node.md#finding-peers-on-restarting). 
diff --git a/docs/HowTo/Deploy/Bootnodes.md b/docs/HowTo/Deploy/Bootnodes.md
index 9b10d1f74cb..857ea0bf396 100644
--- a/docs/HowTo/Deploy/Bootnodes.md
+++ b/docs/HowTo/Deploy/Bootnodes.md
@@ -41,5 +41,5 @@ Adding new bootnodes is a similar process to creating bootnodes. Once the bootno
 update the [`--bootnodes`](../../Reference/CLI/CLI-Syntax.md#bootnodes) command line option for each node to include the new 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-Network.md)), 
+option means the next time they are restarted (for example, when [upgrading](../Upgrade/Upgrade-Node.md)), 
 the node connects to the new bootnodes.  
diff --git a/docs/HowTo/Upgrade/Upgrade-Network.md b/docs/HowTo/Upgrade/Upgrade-Node.md
similarity index 83%
rename from docs/HowTo/Upgrade/Upgrade-Network.md
rename to docs/HowTo/Upgrade/Upgrade-Node.md
index 0830fc9945f..33a1a303f84 100644
--- a/docs/HowTo/Upgrade/Upgrade-Network.md
+++ b/docs/HowTo/Upgrade/Upgrade-Node.md
@@ -1,7 +1,7 @@
 description: Upgrade Besu     
 <!--- END of page meta data -->
 
-# Upgrading your Network 
+# Upgrading your Besu node  
 
 We recommend: 
 
@@ -10,11 +10,11 @@ We recommend:
 
 ## Ansible 
 
-The [Ansible role on Galaxy](https://galaxy.ansible.com/pegasyseng/pantheon) can be used directly
-or customised to suit your needs. Upgrade by running the play. The play: 
+The [Ansible role on Galaxy](https://galaxy.ansible.com/pegasyseng/hyperledger_besu) can be used directly
+or customised to suit your needs. 
 
-Upgrade the Besu version on nodes by running the play with the new version. For details, see the [Readme on Galaxy](https://galaxy.ansible.com/pegasyseng/pantheon). 
-The play: 
+Upgrade the Besu version on nodes by running the play with the new version. For details, see 
+the [Readme on Galaxy](https://galaxy.ansible.com/pegasyseng/hyperledger_besu). The play: 
 
 1. Stops Besu.
 1. Downloads the updated version.
diff --git a/docs/HowTo/Upgrade/Upgrade-Protocol.md b/docs/HowTo/Upgrade/Upgrade-Protocol.md
index 413d55bf08a..df276c012e0 100644
--- a/docs/HowTo/Upgrade/Upgrade-Protocol.md
+++ b/docs/HowTo/Upgrade/Upgrade-Protocol.md
@@ -3,11 +3,11 @@ description: Upgrading protocol versions
 
 ## Upgrading your protocol in a private network 
 
-To [upgrade the protocol](../../Concepts/Protocol-Upgrades.md) (also known as a hardfork) in a private network: 
+To [upgrade the protocol](../../Concepts/Protocol-Upgrades.md) in a private network: 
 
 1. Review included EIPs for breaking changes. A [meta EIP](https://eips.ethereum.org/meta) 
-for each hardfork lists included EIPs. For example, [Istanbul](https://eips.ethereum.org/EIPS/eip-1679). 
-1. Network participants agree on block number at which to [hardfork](../../Concepts/Protocol-Upgrades.md). 
+for each protocol upgrade lists included EIPs. For example, [Istanbul](https://eips.ethereum.org/EIPS/eip-1679). 
+1. Network participants agree on block number at which to [upgrade](../../Concepts/Protocol-Upgrades.md). 
 1. For each node in the network: 
     
      a. Add the [milestone block number](../../Reference/Config-Items.md#milestone-blocks) to the genesis file.     
diff --git a/mkdocs.yml b/mkdocs.yml
index 1f7d1edb07c..0d81a030604 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -120,7 +120,7 @@ nav:
           - Use Alethio EthStats Lite Network Monitor: HowTo/Deploy/Lite-Network-Monitor.md
         - Backup and Restore: HowTo/Backup/Backup.md
         - Upgrade:
-          - Upgrade Network: HowTo/Upgrade/Upgrade-Network.md
+          - Upgrade Node: HowTo/Upgrade/Upgrade-Node.md
           - Upgrade Protocol: HowTo/Upgrade/Upgrade-Protocol.md
         - Develop Dapps on Besu:
           - Use Truffle with Besu: HowTo/Develop-Dapps/Truffle.md