Formatting update to spend limit error example

This documentation page describes how the service monitors and enforces rate limits and spending restrictions across programmatic accounts. The recent revision adjusts the visual presentation of an example error payload returned when an organization exceeds its permitted monthly spend threshold. Specifically, the JSON code block was reformatted with slightly altered punctuation spacing, and a product badge or tag element was inserted above the code sample. The underlying content of the error message, including the specified error classification, the reason code indicating that a spending cap was triggered, the illustrative future access resumption timestamp, and the sample identifier string, remain identical to what was shown previously. In practical terms, this modification does not change operational quotas, tier levels, billing calculations, or how the programmatic interface responds to requests. Developers integrating with the system will experience no shifts in API behavior or payload schemas. What remains uncertain from the documentation extract alone is whether the newly added tag denotes a broader redesign across the developer portal or designates a specific platform scope for that response example.