Update disaster-recovery.adoc

Author: NataliaIvakina

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

@@ -26,17 +26,17 @@ The consequence of this is that all servers may be different in which databases
 Losing a server in a cluster may cause some databases to lose a member while others are unaffected.
 Therefore, in a disaster where one or more servers go down, some databases may keep running with little to no impact, while others may lose all their allocated resources.
 
-Figure 2 shows the cluster in a state of panic when three servers are lost, demonstrating that this situation impacts databases in different ways.
+Figure 2 shows the disaster when three servers are lost, demonstrating that this situation impacts databases in different ways.
 
 image::disaster.svg[width="400", title="Example of a cluster disaster", role=popup]
 
-* For database A -- all primary copies are lost.
-* For database B -- the primary copy is lost, the secondary copy is available.
-* For database C -- two primary copies and a secondary one are lost.
-* For database D -- one primary and two secondaries are lost.
+* For database A -- all allocations are lost.
+* For database B -- the primary allocation is lost, and the secondary allocation is available.
+* For database C -- two primary allocations and a secondary one are lost.
+* For database D -- one primary allocation and two secondary allocations are lost.
 * Database E is unaffected.
 
-Although databases C and D share the same topology, their primaries and secondaries are allocated differently, requiring distinct recovery strategies in the event of a disaster.
+Although databases C and D share the same topology, their primaries and secondaries are allocated differently, requiring distinct recovery strategies in this disaster example.
 
 == Guide overview
 [NOTE]