diff --git a/apps/web/src/content/pages/docs/reference/page-components.mdx b/apps/web/src/content/pages/docs/reference/page-components.mdx
index e8a59269..9ad99ecb 100644
--- a/apps/web/src/content/pages/docs/reference/page-components.mdx
+++ b/apps/web/src/content/pages/docs/reference/page-components.mdx
@@ -51,7 +51,7 @@ The component reflects the current operational state of your monitor. If the mon
 **Historical data visualization:**
 Monitor components display historical uptime data through status trackers. Depending on your [tracker configuration](/docs/guides/how-to-configure-status-page#1-components-configuration), you can show:
 - **Monitor checks with Time per status**: Shows the time spent in each status (success, error, degraded, maintenance).
-- **Monitor checks with Number of checks**: Shows the number of successful vs. failed checks.
+- **Monitor checks with Number of checks**: Shows the number of successful, degraded, and failed checks.
 - **Reports only**: Shows only the most significant status of each day, based on your status reports and maintenances.
 
 **Uptime calculations:**
diff --git a/apps/web/src/content/pages/docs/reference/status-report.mdx b/apps/web/src/content/pages/docs/reference/status-report.mdx
index 44d8315c..789792a5 100644
--- a/apps/web/src/content/pages/docs/reference/status-report.mdx
+++ b/apps/web/src/content/pages/docs/reference/status-report.mdx
@@ -72,7 +72,7 @@ All attached components must belong to the same status page. Adding a component
 
 ## Component impacts
 
-Beyond marking a component as affected, each update of a status report can declare **how badly** each component is affected. This per-component impact drives the component's live status, the report's overall indicator, and — for status pages using the Reports only status source — the uptime percentage.
+Beyond marking a component as affected, each update of a status report can declare **how badly** each component is affected. This per-component impact drives the component's live status, the report's overall indicator, and the uptime percentage. Reports only uses these impacts as its uptime source, while Monitor checks with **Time per status** also includes report intervals alongside monitor downtime.
 
 ### Impact levels