Run edits

docs/cloud/features/observability/run.md

@@ -1,14 +1,20 @@
 # Runs
 
-Run pages, like [plan pages](./plan.md), serve as comprehensive control centres that provide detailed insights into individual runs executed across your various environments. They were created with the same philosophy as the plan pages, providing a consistent user experience and navigation pattern - users navigate to these pages directly from the activity table, just as they would with plan pages, ensuring familiarity and ease of use across the platform. 
+Run pages, like [plan pages](./plan.md), serve as centralized information sources that provide detailed insights into individual runs executed across your various environments.
 
-These pages act as a central hub where team members can monitor and understand all aspects of a run’s execution, from start to finish. And the runs page can serve as an essential jumping off point for issue investigation and triaging processes whenever runs experience errors or unexpected behavior.
+They were created with the same philosophy as the plan pages, providing a consistent user experience and navigation pattern.
+
+These pages act as a central hub where team members can monitor and understand all aspects of a run’s execution, from start to finish. Additionally, they can serve as a jumping off point for investigating run-related errors or unexpected behavior.
+
+![tcloud run](./run/tcloud_run.png)
 
 ## When you might use this
 
-Data engineers often want to examine the most recent run to verify its status. The run page provides a quick way to check whether a run has succeeded or failed and when exactly it was executed. So you can get a comprehensive view of all model executions and audits that were included in the run.
+If you're monitoring data pipelines, a common activity is verifying the status of the most recent run.
+
+The run page provides a quick way to check whether a run has succeeded or failed and when exactly it was executed. The page includes a comprehensive view of all model executions and audits that were included in the run.
 
-For those who need deeper insights, the [Debugger View](../debugger_view.md) offers advanced analysis capabilities. This powerful tool allows teams to investigate which models are taking the longest time to update, helping identify potential performance bottlenecks in their data pipelines.
+If you need deeper insights, the [Debugger View](../debugger_view.md) offers advanced analysis capabilities. This powerful tool allows teams to investigate which models are taking the longest time to update, helping identify potential performance bottlenecks in their data pipelines.
 
 ## Navigating to a Run page
 
@@ -26,9 +32,9 @@ Clicking the link opens the detailed run overview page:
 
 The top of the overview page summarizes the `run`, including:
 
-  - `Status`: completion status (completed, in progress, or failed)
-  - `When`: start and end times
-  - `Changes since previous run`: list of project changes that occurred since the previous `run`
+  1. `Status`: completion status (completed, in progress, or failed)
+  2. `When`: start and end times
+  3. `Changes since previous run`: list of project changes that occurred since the previous `run`
 
 ![tcloud run](./run/tcloud_run_summary.png)
 
@@ -44,6 +50,6 @@ The lower portion of the page contains a table with three tabs.
 
 ![tcloud run model executions](./run/run_audits.png)
 
-`Explore Executions`: interactive view of executed models, including a lineage graph of model dependencies, and detailed information about impact analysis, model definitions, time intervals processed, and links to associated logs (for more see the [Debugger View page](../debugger_view.md))
+`Explore Executions`: interactive view of executed models, including a lineage graph of model dependencies, and detailed information about impact analysis, model definitions, time intervals processed, and links to associated logs (learn more on the [Debugger View page](../debugger_view.md))
 
 ![tcloud run model executions](./run/run_explore_executions.png)