Clarifying CacheTtl max value and cached reads. (cloudflare#23501)

Author: Oxyjun

src/content/docs/kv/api/read-key-value-pairs.mdx

@@ -249,9 +249,11 @@ A hot read means that the data is cached on Cloudflare's edge network using the
 
 `cacheTtl` is not recommended if your data is updated often and you need to see updates shortly after they are written, because writes that happen from other global network locations will not be visible until the cached value expires.
 
-The `cacheTtl` parameter must be an integer greater than or equal to `60`, which is the default.
+The `cacheTtl` parameter must be an integer greater than or equal to `60`, which is the default. The maximum value for `cacheTtl` is [`Number.MAX_SAFE_INTEGER`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER).
 
-The effective `cacheTtl` of an already cached item can be reduced by getting it again with a lower `cacheTtl`. For example, if you did `NAMESPACE.get(key, {cacheTtl: 86400})` but later realized that caching for 24 hours was too long, you could `NAMESPACE.get(key, {cacheTtl: 300})` or even `NAMESPACE.get(key)` and it would check for newer data to respect the provided `cacheTtl`, which defaults to 60 seconds. This overwriting `cacheTtl` behavior will only take effect in regions where the key-value pair is read with the updated `cacheTtl`. In other words, reading a key-value pair in a given region will update the cache time-to-live in that region but not in other regions of Cloudflare's network (these will keep the time-to-live from the last read of the region). 
+The effective `cacheTtl` of an already cached item can be reduced by getting it again with a lower `cacheTtl`. For example, if you did `NAMESPACE.get(key, {cacheTtl: 86400})` but later realized that caching for 24 hours was too long, you could `NAMESPACE.get(key, {cacheTtl: 300})` or even `NAMESPACE.get(key)` and it would check for newer data to respect the provided `cacheTtl`, which defaults to 60 seconds. This overwriting `cacheTtl` behavior will only take effect in regions where the key-value pair is read with the updated `cacheTtl`. In other words, reading a key-value pair in a given region will update the cache time-to-live in that region but not in other regions of Cloudflare's network (these will keep the time-to-live from the last read of the region).
+
+Reading KV values while it is cached still incurs cost in line with Workers KV [limits](/kv/platform/limits/) and [pricing](/kv/platform/pricing/).
 
 ### Requesting more keys per Worker invocation with bulk requests
 

src/content/docs/kv/platform/limits.mdx

@@ -6,27 +6,27 @@ sidebar:
 
 ---
 
-
-
 import { Render } from "~/components"
 
-| Feature                           | Free                  | Paid         |
-| --------------------------------- | --------------------- | ------------ |
-| Reads                             | 100,000 reads per day | Unlimited    |
-| Writes to different keys          | 1,000 writes per day  | Unlimited    |
-| Writes to same key                | 1 per second          | 1 per second |
-| Operations/Worker invocation [^1] | 1000                  | 1000         |
-| Namespaces                        | 1000                  | 1000         |
-| Storage/account                   | 1 GB                  | Unlimited    |
-| Storage/namespace                 | 1 GB                  | Unlimited    |
-| Keys/namespace                    | Unlimited             | Unlimited    |
-| Key size                          | 512 bytes             | 512 bytes    |
-| Key metadata                      | 1024 bytes            | 1024 bytes   |
-| Value size                        | 25 MiB                | 25 MiB       |
-| Minimum [`cacheTtl`](/kv/api/read-key-value-pairs/#cachettl-parameter)         | 60 seconds            | 60 seconds   |
+| Feature                                                                        | Free                  | Paid         |
+| ------------------------------------------------------------------------------ | --------------------- | ------------ |
+| Reads                                                                          | 100,000 reads per day | Unlimited    |
+| Writes to different keys                                                       | 1,000 writes per day  | Unlimited    |
+| Writes to same key                                                             | 1 per second          | 1 per second |
+| Operations/Worker invocation [^1]                                              | 1000                  | 1000         |
+| Namespaces                                                                     | 1000                  | 1000         |
+| Storage/account                                                                | 1 GB                  | Unlimited    |
+| Storage/namespace                                                              | 1 GB                  | Unlimited    |
+| Keys/namespace                                                                 | Unlimited             | Unlimited    |
+| Key size                                                                       | 512 bytes             | 512 bytes    |
+| Key metadata                                                                   | 1024 bytes            | 1024 bytes   |
+| Value size                                                                     | 25 MiB                | 25 MiB       |
+| Minimum [`cacheTtl`](/kv/api/read-key-value-pairs/#cachettl-parameter) [^2]    | 60 seconds            | 60 seconds   |
 
 [^1]: Within a single invocation, a Worker can make up to 1,000 operations to external services (for example, 500 Workers KV reads and 500 R2 reads). A bulk request to Workers KV counts for 1 request to an external service.
 
+[^2]: The maximum value is [`Number.MAX_SAFE_INTEGER`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER).
+
 <Render file="limits_increase" product="workers" />
 
 :::note[Free versus Paid plan pricing]