Update planning.adoc

Author: NataliaIvakina

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

@@ -187,22 +187,23 @@ However, _restoring_ a database in a cluster is different since it is not known
 This method relies on the seed already existing on one of the servers.
 The recommended way to restore a database in a cluster is to xref::database-administration/standard-databases/seed-from-uri.adoc[seed from URI].
 
+[NOTE]
+====
+For backing up a clustered database, it is recommended to use the `--include-metadata=all` option.
+This option includes metadata in the backup file, retaining not only `users` and `roles` but also the cluster topology.
+The cluster topology in the `system` database details which servers exist and their modes.
+====
 
 [[backup-planning-databases]]
-== Databases to backup
+== Databases to back up
 
 A Neo4j DBMS can host multiple databases.
-Both Neo4j Community and Enterprise Editions have a default user database, called `neo4j`, and a `system` database, which contains configurations, e.g., operational states of databases, security configuration, schema definitions, login credentials, and roles.
+Both Neo4j Community and Enterprise Editions have a default user database named `neo4j` and a `system` database.
+The `system` database contains configurations, e.g., operational states of databases, security configuration, schema definitions, login credentials, and roles.
 
 In the Enterprise Edition, you can also create multiple user databases.
 Each of these databases is backed up independently of one another.
 
-[NOTE]
-====
-Backing up the `system` database, it is recommended to use the `--include-metadata=all` option.
-This restores the user databases to the new `system` database retaining not only `users` and `roles` but also the cluster topology.
-====
-
 It is very important to store a recent backup of your databases, including the `system` database, in a safe location.
 
 
@@ -224,4 +225,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.