diff --git a/docs/cloud/ai-agents/context-engine.mdx b/docs/cloud/ai-agents/context-engine.mdx
index 3fb98b6fe..258a673c4 100644
--- a/docs/cloud/ai-agents/context-engine.mdx
+++ b/docs/cloud/ai-agents/context-engine.mdx
@@ -20,7 +20,7 @@ It connects lineage across your entire stack — from your data warehouse and db
 **From Elementary's own monitoring:**
 - **Test results** — pass/fail history across dbt, Python, and Cloud tests, coverage gaps
 - **Test performance** — execution times and cost per test run
-- **Model performance** — execution times, cost, trends over time
+- **Task performance** — execution times, cost, trends over time
 - **Health scores** — data quality dimensions across all assets
 
 Lineage connects these layers. A table in your warehouse maps to a dbt model, which feeds a dashboard, which is owned by a team. When something breaks, the Context Engine already knows the blast radius.
diff --git a/docs/cloud/best-practices/triage-and-response.mdx b/docs/cloud/best-practices/triage-and-response.mdx
index 2de803fab..bacce06dd 100644
--- a/docs/cloud/best-practices/triage-and-response.mdx
+++ b/docs/cloud/best-practices/triage-and-response.mdx
@@ -124,9 +124,9 @@ These are the questions that should be asked, and product tips on how to answer
   - Is the failure is a model failure, or a freshness issue?
   - Do we run `dbt build` and this failure stopped the pipeline?
 
-    - Check the **Model runs** section of the dashboard to see if there are skipped models, as failures in build cause the downstream models to be skipped.
+    - Check the **Task runs** section of the dashboard to see if there are skipped models, as failures in build cause the downstream models to be skipped.
 
-    ![Model runs portion of the dashboard](https://res.cloudinary.com/diuctyblm/image/upload/v1738149955/Docs/dashboard-model-runs_zzgnd2.png)
+    ![Task runs portion of the dashboard](https://res.cloudinary.com/diuctyblm/image/upload/v1738149955/Docs/dashboard-model-runs_zzgnd2.png)
 
 
 - How important is the data asset?
diff --git a/docs/cloud/cloud-vs-oss.mdx b/docs/cloud/cloud-vs-oss.mdx
index 42b0b0f79..3ba6620a3 100644
--- a/docs/cloud/cloud-vs-oss.mdx
+++ b/docs/cloud/cloud-vs-oss.mdx
@@ -37,7 +37,7 @@ Below is a detailed comparison between the OSS and Cloud features:
 | **Detection**          | <ul><li>dbt tests and anomaly detection tests (freshness, volume)</li></ul> | <ul><li>[ML-powered anomaly detection](/cloud/features/anomaly-detection/monitors-overview)</li><li>[No-code cloud tests](/cloud/features/data-tests/cloud-tests-overview)</li><li>[Schema validation](/cloud/features/data-tests/schema-validation-test) and [data contracts](/cloud/features/data-tests/data-contract-test)</li><li>Bulk add/edit for tests</li></ul> |
 | **Test coverage**      | <ul><li>Test results in the self-hosted report</li></ul> | <ul><li>[Test coverage screen](/cloud/features/data-tests/test-coverage-screen)</li><li>Automated coverage recommendations</li></ul> |
 | **Triage & Response**  | <ul><li>Basic Slack and Teams alerts</li></ul> | <ul><li>[Interactive alerts](/cloud/features/alerts-and-incidents/alerts-and-incidents-overview) and [alert rules](/cloud/features/alerts-and-incidents/alert-rules)</li><li>[Incident management](/cloud/features/alerts-and-incidents/incident-management)</li><li>[BI integrations](/cloud/integrations/bi/connect-bi-tool)</li><li>Test results history</li></ul> |
-| **Performance & cost** | <ul><li>Model and test performance</li></ul>            | <ul><li>[Model and test performance](/cloud/features/performance-monitoring/performance-monitoring)</li><li>[Performance alerts](/cloud/features/performance-monitoring/performance-alerts)</li><li>Continuous cost and performance monitoring</li></ul> |
+| **Performance & cost** | <ul><li>Model and test performance</li></ul>            | <ul><li>[Task and test performance](/cloud/features/performance-monitoring/performance-monitoring)</li><li>[Performance alerts](/cloud/features/performance-monitoring/performance-alerts)</li><li>Continuous cost and performance monitoring</li></ul> |
 | **Governance**         | X                                      | <ul><li>[Catalog](/cloud/features/collaboration-and-communication/catalog)</li><li>[Metadata in code and UI](/cloud/features/data-governance/manage-metadata)</li><li>[AI-generated descriptions](/cloud/features/data-governance/ai-descriptions)</li><li>[Critical assets](/cloud/features/data-governance/critical_assets)</li></ul> |
 | **Enabling non-technical users** | X                                      | <ul><li>[No-code test editor](/cloud/features/data-tests/cloud-tests-overview)</li><li>[Data health scores](/cloud/features/collaboration-and-communication/data-health)</li><li>[External catalog integrations](/cloud/integrations/governance/atlan)</li><li>Ticketing integrations ([Jira](/cloud/integrations/alerts/jira), [Linear](/cloud/integrations/alerts/linear), [ServiceNow](/cloud/integrations/alerts/servicenow))</li></ul> |
 | **Security & privacy** | <ul><li>Fully self-hosted, your data and metadata stay in your environment</li></ul> | <ul><li>[RBAC](/cloud/features/roles-and-permissions) at account, environment, and asset level</li><li>SSO ([Okta](/cloud/integrations/security-and-connectivity/okta), [Microsoft Entra](/cloud/integrations/security-and-connectivity/ms-entra))</li><li>[Audit logs](/cloud/features/collaboration-and-communication/audit_logs/overview) and [PrivateLink](/cloud/integrations/security-and-connectivity/aws-privatelink-integration)</li><li>[SOC 2 Type II and HIPAA](/cloud/general/security-and-privacy), metadata only and no raw data access</li></ul> |
diff --git a/docs/cloud/features/performance-monitoring/performance-monitoring.mdx b/docs/cloud/features/performance-monitoring/performance-monitoring.mdx
index e0b951007..d4a74cdd4 100644
--- a/docs/cloud/features/performance-monitoring/performance-monitoring.mdx
+++ b/docs/cloud/features/performance-monitoring/performance-monitoring.mdx
@@ -16,9 +16,9 @@ Use the pages to monitor and spot outliers. Use the agent to investigate and get
 
 Elementary monitors and logs the execution times of your dbt models and tests.
 
-## Models performance
+## Task Performance
 
-Navigate to the `Model Duration` tab.
+Navigate to **Task Performance** in the sidebar.
 
 The table displays the latest execution time, median execution time, and execution time trend for each model. You can sort the table by these metrics and explore the execution times over time for the models with the longest durations
 
@@ -31,7 +31,7 @@ src="https://res.cloudinary.com/diuctyblm/video/upload/v1719746949/9_-_Performan
 frameborder="0"
 allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
 allowfullscreen
-alt="Elementary Models Duration tab"
+alt="Elementary Task Performance page"
 >
 </iframe>