Further wording refinements

docs/modules/storage/pages/persistence.adoc

@@ -1,5 +1,5 @@
 = Persisting Data on Disk
-:description: Persistence allows individual members and whole clusters to recover data by persisting map entries, JCache data, and streaming job snapshots on disk. Members can use persisted data to recover from planned cluster-wide shutdowns, unplanned cluster-wide failures and speed up individual member restarts by reducing the volume of data sent over the network.
+:description: Persistence allows individual members and whole clusters to recover data by persisting map entries, JCache data, and streaming job snapshots on disk. Members can use persisted data to recover from planned cluster-wide shutdowns, unplanned cluster-wide failures, and to accelerate individual member restarts by reducing the volume of data sent over the network.
 :toc-levels: 3
 :page-enterprise: true
 
@@ -11,7 +11,7 @@ Data in Hazelcast is usually stored in-memory (RAM) so that it's faster to acces
 
 Clusters can use persisted data for the following scenarios:
 
-- **Persisting data across cluster-wide shutdowns**:
+- **Cluster-wide shutdowns**:
 
 ** **Planned**: A whole cluster is shut down and restarted with the same configuration, state, and data as before the restart. 
 +
@@ -21,10 +21,10 @@ In order for persistence to function correctly for planned cluster shutdowns you
 ====
 ** **Unplanned**: A cluster is restarted after all its members crash at the same time due an event such as a power outage. Note that some data loss is expected unless `fsync` is set to `true`. For more information, see xref:storage:configuring-persistence.adoc#data-structures[Data structure options].
 
-- **Speeding up single member restarts**: 
+- **Accelerating single member restarts**: 
 
 ** **Planned**: During a rolling restart each cluster member is restarted one by one for scenarios such as installing an operating system patch or new hardware. xref:maintain-cluster:rolling-upgrades.adoc[Rolling upgrades] are an example of a rolling restart.
-** **Unplanned**: A member may crash or terminate unexpectedly at any time, using persistence allows faster recovery.
+** **Unplanned**: A single member may crash or terminate unexpectedly at any time, using persistence allows faster recovery by using the data on disk where possible. In some cases a member can recover entirely using the data on disk removing the need to transfer data over the network.
 
 
 == Supported Features