Navigation updated for expenditure and token limit sections

The reference documentation outlines throughput boundaries, token constraints, and budgetary thresholds enforced across developer accounts using the API. The recent modification rearranges index markers and navigation pointers within the documentation guide. Previously listed as discrete standalone labels, subtopics covering total budget ceilings and token volumes that factor in prompt caching now appear grouped directly under broader parent designations. Specifically, markers for reaching financial boundaries and tracking cache-sensitive input token consumption were merged into compound labels alongside their corresponding top-level thematic sections. For developers managing active API integrations, this adjustment does not alter numeric allowances, billing rates, usage tier thresholds, or runtime enforcement behavior. System requests continue to encounter the exact same financial boundaries and concurrency restrictions as before; only the documentation layout organizing these concepts was refreshed. Because the update reflects solely structural navigation revisions, it remains unclear from the provided excerpt alone whether any explanatory guidance on cache optimization was revised, or whether broader adjustments to account quotas will follow.