diff --git a/docs/HowTo/Backup/Backup.md b/docs/HowTo/Backup/Backup.md
index bdc6a7c4510..bdaa2477282 100644
--- a/docs/HowTo/Backup/Backup.md
+++ b/docs/HowTo/Backup/Backup.md
@@ -1,57 +1,55 @@
-description: Backing up and restoring Besu   
-<!--- END of page meta data -->
+---
+description: Backing up and restoring Besu
+---
 
-# Backups 
+# Backups
 
-In a decentralized blockchain, data is replicated on other nodes so it cannot be lost. However, backing up 
-configuration and data ensures a smoother recovery.  
+In a decentralized blockchain, data replicates between nodes so it is not lost. However,backing up
+configuration and data ensures a smoother recovery from corrupted data or other failures.
 
-## Genesis File 
+## Genesis file
 
-The genesis file for a network must be accessible on every node. We recommend the genesis file is 
-stored under source control. 
+The genesis file for a network must be accessible on every node. We recommend the genesis file is
+stored under source control.
 
-## Data Backups
+## Data backups
 
-If installed locally, the default data location is the directory in which Besu is installed.
+If installed locally, the default data location is the Besu installation directory.
 
-We recommend mounting a [separate volume to store data](../Get-Started/Run-Docker-Image.md#starting-besu). 
-Use the [`--data-path`](../../Reference/CLI/CLI-Syntax.md#data-path) command line option to pass the path to Besu. 
+We recommend mounting a
+[separate volume to store data](../Get-Started/Run-Docker-Image.md#starting-besu). Use the
+[`--data-path`](../../Reference/CLI/CLI-Syntax.md#data-path) command line option to pass the path
+to Besu.
 
-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 Besu installation directory, 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. You can perform periodic backups of
+the data directory and send the data to your preferred backup mechanism. For example, cron job and
+rsync, archives to the cloud such as s3, or `tar.gz` archives.
 
-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).
+## Data restores
 
-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).
+To restore data:
 
-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. 
+1. If the node is running, stop the node.
+1. If required, move the data directory to another location for analysis.
+1. Restore the data from your last known good backup to the same directory.
+1. Ensure user permissions are valid so the data directory can be read from and written to.
+1. Restart the node.
 
-## Data Restores 
+## Corrupted data
 
-To restore data: 
+If log messages signify a corrupt database, the cleanest way to recover is:
 
-1. If the node is running, stop the node. 
-1. If required, move the data directory to another location for analysis. 
-1. Restore the data from your last known good backup to the same directory. 
-1. Ensure user permissions are valid so the data directory can be read from and written to. 
-1. Restart the node. 
+1. Stop the node.
+1. Restore the data from a [previous backup](#data-backups).
+1. Restart the node.
 
-## Corrupted Data 
+## Finding peers after restarting
 
-If log messages indicate a corrupt database, the cleanest way to recover is: 
+The process for finding peers after restarting is the same as for
+[finding peers after upgrading and restarting].
 
-1. Stop the node. 
-1. Restore the data from a [previous backup](#data-backups). 
-1. Restart the node. 
-
-## 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). 
+<!-- Links -->
+[finding peers after upgrading and restarting]: ../Upgrade/Upgrade-Node.md#finding-peers-on-restarting
\ No newline at end of file