4.1 cherry pick 932 (neo4j#965)

Cherry-picked from neo4j#932

Author: lidiazuin

modules/ROOT/pages/backup-restore/online-backup.adoc

@@ -160,6 +160,7 @@ Therefore, it is highly recommended to perform the backup and consistency check
 +
 Alternatively, you can decouple the backup operation from the consistency check (using the `neo4j-admin backup` option `--check-consistency=false`) and schedule that part of the workflow to happen at a later point in time, on a dedicated machine.
 Consistency checking a backup is vital for safeguarding and ensuring the quality of the data, and should not be underestimated.
+For more information, see xref:tools/consistency-checker.adoc[Consistency checker].
 +
 [TIP]
 ====

modules/ROOT/pages/backup-restore/planning.adoc

@@ -216,4 +216,4 @@ If you have a cluster, you should back up these files for each cluster member.
 
 For any backup, it is important that you store your data separately from the production system, where there are no common dependencies, and preferably off-site.
 If you are running Neo4j in the cloud, you may use a different availability zone or even a separate cloud provider.
-Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.
+Since backups are kept for a long time, the longevity of archival storage should be considered as part of backup planning.