Future proof metric limit wording (#5080)

* Update api-reference.mdx

* Apply suggestion from @lennessyy

---------

Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com>

Author: dustin-temporal

docs/cloud/metrics/openmetrics/api-reference.mdx

@@ -117,8 +117,8 @@ Rate limit scopes are subject to change.
 | Account | 180 requests per hour |
 
 :::caution
-Practical enforcement of this limit may allow bursts of up to 2x this limit (up to 360 requests per hour) at various times.
-Do not rely on this headroom: design production clients against the documented limit of 180 requests per hour.
+Practical enforcement of this limit may allow bursts that exceed the limit at various times.
+Do not rely on this headroom: design production clients against the documented limit.
 
 :::
 
@@ -393,8 +393,8 @@ count({__name__=~"temporal_cloud_v1_.*"}) by (__name__)
 | 30k total datapoints per scrape | Response may be truncated | Use namespace/metric filtering |
 | 180 requests per account per hour (~3 requests per minute) | HTTP 429 returned | Set scrape interval to 30s |
 
-:::note
-Practical enforcement of this limit may allow bursts of up to 2x this limit (up to 360 requests per hour) at various times.
-Do not rely on this headroom: design production clients against the documented limit of 180 requests per hour.
+:::caution
+Practical enforcement of this limit may allow bursts that exceed the limit at various times.
+Do not rely on this headroom: design production clients against the documented limit.
 
 :::