diff --git a/cli/attaching-git-metadata.mdx b/cli/attaching-git-metadata.mdx
index f14def0d..ddc7cb89 100644
--- a/cli/attaching-git-metadata.mdx
+++ b/cli/attaching-git-metadata.mdx
@@ -37,4 +37,18 @@ Or, if you want to set repo URL you invoke:
 
 ```bash Terminal
 CHECKLY_REPO_URL="https://my.git.solution/project/" npx checkly test
-```
\ No newline at end of file
+```
+
+## Working with multiple repositories
+
+Each `checkly test --record` or `checkly deploy` invocation attaches metadata for a **single** `repoUrl`. If your monitors span multiple source repositories (for example, a backend repo and a frontend repo), run the CLI separately from each repository's CI pipeline and set `CHECKLY_REPO_URL` (and the other git variables) to point at the repo that owns the checks being tested or deployed in that pipeline.
+
+```bash Terminal
+# Backend CI pipeline
+CHECKLY_REPO_URL="https://github.com/acme/backend" npx checkly deploy
+
+# Frontend CI pipeline
+CHECKLY_REPO_URL="https://github.com/acme/frontend" npx checkly deploy
+```
+
+To keep checks from different repos isolated, scope each pipeline to its own set of resources — for example by placing each repo's checks in a separate [group](/platform/groups) or by using the [`--tags`](/cli/checkly-deploy) and check-file globs in `checkly.config` so that a deploy from one repo only touches its own checks.
\ No newline at end of file
diff --git a/integrations/observability/prometheus-v2.mdx b/integrations/observability/prometheus-v2.mdx
index b6c924c3..c90a53f1 100644
--- a/integrations/observability/prometheus-v2.mdx
+++ b/integrations/observability/prometheus-v2.mdx
@@ -88,6 +88,10 @@ checkly_check_status{name="Passing Browser Check",status="degraded"} 0
 
 `checkly_check_status` can be useful for viewing the current status of a check, whereas `checkly_check_result_total` can be useful for calculating overall statistics.
 
+<Note>
+`checkly_check_result_total` counts individual **check run results** over a 1-hour window and is intended for statistics and alerting, not for reconciling billing. Plan usage and billing are tracked separately in the Checkly app under [Billing](https://app.checklyhq.com/settings/account/billing) and via the CLI ([`checkly account plan`](/cli/checkly-account)), which report **active checks** and **check run volume** as measured by the billing system. A difference between this metric and your billing dashboard is expected — they measure different things.
+</Note>
+
 The metrics `checkly_browser_check_web_vitals_seconds`, `checkly_browser_check_errors`, `checkly_api_check_timing_seconds`, `checkly_tcp_monitor_timing_seconds`, `checkly_icmp_monitor_timing_seconds`, and `checkly_dns_monitor_timing_seconds` contain a `type` label.
 This label indicates the different Web Vitals, error types, and timing phases being measured.