Update how-kv-works.mdx

Author: thomasgauvin

src/content/docs/kv/concepts/how-kv-works.mdx

@@ -48,7 +48,7 @@ KV does not perform like an in-memory datastore, such as [Redis](https://redis.i
 
 ## Consistency
 
-KV achieves high performance by being eventually-consistent. At the Cloudflare global network location at which changes are made, these changes are usually immediately visible. However, this is not guaranteed and therefore it is not advised to rely on this behaviour. In other global network locations changes may take up to 60 seconds or more to be visible as their cached versions of the data time-out.
+KV achieves high performance by being eventually-consistent. Writes to KV are eventually propagated and visible at all locations up to 60 seconds or more after the write as their cached versions of the data time-out.
 
 Visibility of changes takes longer in locations which have recently read a previous version of a given key (including reads that indicated the key did not exist, which are also cached locally).