Update disaster-recovery.adoc

Author: NataliaIvakina

modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc

@@ -167,6 +167,8 @@ This causes downtime for all databases in the cluster until the processes are st
 . For every _lost_ server, add a new *unconstrained* one according to xref:clustering/servers.adoc#cluster-add-server[Add a server to the cluster].
 It is important that the new servers are unconstrained, or deallocating servers in the next step of this guide might be blocked, even though enough servers were added.
 +
+In the current example, the new unconstrained servers are added in this step.
++
 [NOTE]
 =====
 While recommended, it is not strictly necessary to add new servers in this step.
@@ -178,7 +180,7 @@ Be aware that not replacing servers can cause cluster overload when databases ar
 +
 . On each server, run `bin/neo4j-admin database load system --from-path=[path-to-dump] --overwrite-destination=true` to load the current `system` database dump.
 +
-image::system-db-restored.svg[width="400", title="The `system` database is restored and unconstrained servers are added", role=popup]
+image::system-db-restored.svg[width="400", title="The unconstrained servers are added and the `system` database is restored", role=popup]
 +
 . On each server, ensure that the discovery settings are correct.
 See xref:clustering/setup/discovery.adoc[Cluster server discovery] for more information.