diff --git a/docs/edge/en/concepts/crews.mdx b/docs/edge/en/concepts/crews.mdx
index 5bed8495b..2e4f21032 100644
--- a/docs/edge/en/concepts/crews.mdx
+++ b/docs/edge/en/concepts/crews.mdx
@@ -322,7 +322,7 @@ Caches can be employed to store the results of tools' execution, making the proc
 
 After the crew execution, you can access the `usage_metrics` attribute to view the language model (LLM) usage metrics for all tasks executed by the crew. This provides insights into operational efficiency and areas for improvement.
 
-`total_tokens` is the billed total (`prompt_tokens + completion_tokens`). Breakdown fields such as `cached_prompt_tokens` describe subsets already included in those totals — see [Flow Usage Metrics](/concepts/flows#flow-usage-metrics) for the full field semantics.
+`total_tokens` is the billed total (`prompt_tokens + completion_tokens`). Breakdown fields such as `cached_prompt_tokens` and `cache_creation_tokens` describe subsets already included in those totals and are not added on top of `total_tokens`. See the **UsageMetrics field semantics** section in the Flows concept documentation for the full contract.
 
 ```python Code
 # Access the crew's usage metrics
diff --git a/docs/edge/en/concepts/llms.mdx b/docs/edge/en/concepts/llms.mdx
index 6e8eb5e33..02fb97314 100644
--- a/docs/edge/en/concepts/llms.mdx
+++ b/docs/edge/en/concepts/llms.mdx
@@ -435,9 +435,9 @@ In this section, you'll find detailed examples that help you select, configure,
     # prompt_tokens includes cache read + cache write for Anthropic
     ```
 
-    See [UsageMetrics field semantics](/concepts/flows#usagemetrics-field-semantics)
-    for the provider-neutral contract used by `crew.usage_metrics` and
-    `flow.usage_metrics`.
+    See the **UsageMetrics field semantics** section in the Flows concept
+    documentation for the provider-neutral contract used by `crew.usage_metrics`
+    and `flow.usage_metrics`.
 
     **Important Notes:**
     - `max_tokens` is a **required** parameter for all Anthropic models