fixup! Can I make a History Call to several Channels Simultaneously?

Author: franrob-projects

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

@@ -34,14 +34,14 @@ The Ably SDKs provide a straightforward API to retrieve paginated message event
 
 ### Multi-channel history limitations
 
-History is stored per channel, and you cannot make a single call to retrieve history from multiple channels simultaneously. Each history request must target a specific channel.
+History is stored per channel. You cannot retrieve history from multiple channels in a single call. Each history request must target a specific channel.
 
-To retrieve history from multiple channels, you must iterate over your list of channels and call the history method for each one. This can be done either synchronously (one after another) or asynchronously (in parallel), depending on your performance requirements:
+To retrieve history from multiple channels, iterate over your channels and call the history method for each one. You can do this synchronously (one after another) or asynchronously (in parallel):
 
-* Synchronous approach - Call history for each channel sequentially, which is simpler but slower
-* Asynchronous approach - Make parallel history calls for better performance, then combine and sort results by timestamp if needed
+* Synchronous: Call history for each channel sequentially. Simpler but slower.
+* Asynchronous: Make parallel history calls for better performance. Combine and sort results by timestamp if needed.
 
-This pattern is commonly used in applications that implement channel sharding, where related data is distributed across multiple channels.
+This pattern is commonly used when implementing channel sharding, where related data is distributed across multiple channels.
 
 This example retrieves the latest message sent on a channel: