fixup! How synchronized / up to date is channel history betweendatacenters / regions?

Author: franrob-projects

src/pages/docs/storage-history/history.mdx

@@ -800,6 +800,8 @@ Channel history is synchronized across all datacenters within approximately 100
 
 ### Synchronization process
 
+When a message is published, it moves through a multi-stage synchronization process.
+
 When a message is published:
 
 1. The message is immediately available in ephemeral storage (Redis) at the publishing datacenter.
@@ -808,20 +810,25 @@ When a message is published:
 
 ### Storage consistency
 
-Storage consistency levels:
+Different storage types have different consistency guarantees.
+
+The following table explains storage consistency levels:
 
 | Storage type | Synchronization time | Consistency level |
 |-------------|---------------------|------------------|
-| Ephemeral storage. | Immediate at publishing datacenter. | Eventually consistent globally. |
-| Persistent storage. | ~100ms across all datacenters. | Strong consistency via quorum. |
-| Message survivability. | 99.999999% after acknowledgment. | Replicated to 3+ regions. |
+| Ephemeral storage | Immediate at publishing datacenter | Eventually consistent globally |
+| Persistent storage | ~100ms across all datacenters | Strong consistency via quorum |
+| Message survivability | 99.999999% after acknowledgment | Replicated to 3+ regions |
 
 ### Implications for applications
 
-- History requests may show slight delays (up to 100ms) for messages published in remote datacenters.
-- Connection recovery works reliably regardless of datacenter failover.
-- Message continuity is preserved even during regional failures.
-- Applications should not depend on instant global history consistency for real-time features.
+Understanding these synchronization characteristics helps you design robust applications.
+
+* History requests may show slight delays (up to 100ms) for messages published in remote datacenters.
+* Connection recovery works reliably regardless of datacenter failover.
+* Message continuity is preserved even during regional failures.
+* Applications should not depend on instant global history consistency for real-time features.
+
 
 ## Ordering of historical messages <a id="historical-order"/>