Update context based on Adam's feedback

Author: Aviatorscode2

content/docs/platform/workflow/contexts.mdx

@@ -11,7 +11,7 @@ In simple terms, a context acts like an extended version of the payload. While t
 
 <Callout type='warn'>You can pass a maximum of five contexts per workflow trigger and the serialized `data` object for each context is limited to 64KB.</Callout>
 
-## How Context works
+## How context works
 
 Imagine you have a single subscriber entity, `[email protected]`, who uses two different applications you offer: "Notion Email" and "Notion Calendar". You want to send notifications specific to each application.
 
@@ -65,12 +65,12 @@ await novu.trigger('new-calendar-event', {
 
 Here are some ways context can be used:
 
-- **Multi-tenancy and App Routing**: Use a tenant or app context to dynamically alter notification content, branding, or logic for different customers or applications from a single workflow.
-- **Shared Chat Credentials**: For chat providers like Slack or MS Teams, store workspace-level credentials (for example, a bot token) in a context. This allows multiple subscribers within that workspace to receive notifications without each subscriber needing to store the shared token.
-- **A/B Testing**: Pass a campaign identifier in a context (for example, campaign: 'new-welcome-email-v2'). Use this in a condition step to split users into different notification paths and measure which performs better.
-- **Data Residency and Compliance**: Use a region context to tag notifications with their origin. This can help in applying data retention policies or filtering data for compliance audits.
+- **Multi-tenancy and app routing**: Use a tenant or app context to dynamically alter notification content, branding, or logic for different customers or applications from a single workflow.
+- **Shared chat credentials**: For chat providers like Slack or MS Teams, store workspace-level credentials (for example, a bot token) in a context. This allows multiple subscribers within that workspace to receive notifications without each subscriber needing to store the shared token.
+- **A/B testing**: Pass a campaign identifier in a context (for example, campaign: 'new-welcome-email-v2'). Use this in a condition step to split users into different notification paths and measure which performs better.
+- **Data residency and compliance**: Use a region context to tag notifications with their origin. This can help in applying data retention policies or filtering data for compliance audits.
 
-## How to use Contexts
+## How to use contexts
 
 Once a context is created, you can access its properties anywhere variables are supported, such as in template editors or condition steps.
 
@@ -103,20 +103,45 @@ Once a context is created, you can access its properties anywhere variables are
         Your account is on the {{context.tenant.data.plan}} plan.
         ```
 
-    * Using Context in Conditions
+    * Using context in step conditions
 
         You can use context variables in the **Step conditions** tab of a workflow step to add conditional logic to your notifications. For example, only send a "Feature X is now enabled" email if `context.tenant.data.plan` is `enterprise`.
         ![Context step conditions](/images/workflows/context-step-conditions.png)
 
-## Managing Context
+## Viewing and debugging contexts
+
+Once you start using contexts in your workflows, Novu provides full observability so you can monitor and debug your context usage after a workflow has been triggered.
+
+### Searching for workflow runs
+
+You can filter your workflow runs to find all executions associated with a specific context.
+
+1. Navigate to the **Activity Feed** in your Novu dashboard.
+2. Select the **Workflow Runs** tab.
+3. In the search bar, click **Context** and enter the context `type` and `id` using the format `type:id`.
+
+![Searching for workflow runs](/images/workflows/search-context-activityfeed.png)
+
+### Verifying the resolved context
+
+To confirm that Novu received and processed your context data correctly, you can inspect the API traces for a specific run.
+
+1. From the **Activity Feed**, select the relevant workflow run from the list in the **Requests** tab.
+2. In the workflow run details, go to the **API Traces** tab.
+
+Here, you will see the full context object that was resolved and attached to that specific workflow execution.
+
+![Verifying the resolved context](/images/workflows/resolved-context.png)
+
+## Manage context
 
 Novu provides two ways to manage contexts, either through the Novu dashboard or using the API.
 
-### Creating a Context
+### Create a Context
 
 You can create a new context via Novu dashboard or API, when you want to register reusable metadata. After creation, this context becomes available to all workflows and templates within your environment.
 
-#### Create a Context from the dashboard
+#### Create a context via dashboard
 
 Use the dashboard to manually define contexts that represent key business entities.
 
@@ -129,7 +154,7 @@ Use the dashboard to manually define contexts that represent key business entiti
     - **Custom data (JSON)**: An optional JSON object that contains metadata, such as branding, plan, or region details.
   5. Click **Create context** to save the context.
 
-#### Create a Context using the API
+#### Create a context via API
 
 Novu provides an API to create a context. If a context with the same `type:id` combination already exists, then the request will fail.
 
@@ -145,7 +170,7 @@ POST /v2/contexts
 }
 ```
 
-#### Create a Context using the API (Just-in-time)
+#### Create a context via API (Just-in-time)
 
 Contexts can also be created automatically when you trigger a workflow that includes a new context object. If the specified `type:id` doesn’t exist, then Novu automatically creates it before running the workflow.
 
@@ -160,19 +185,19 @@ await novu.trigger('welcome-email', {
 });
 ```
 
-### Updating a Context
+### Update a context
 
 You can update a context’s data payload at any time. The context `type` and `id` remain immutable.
 
-#### Update a Context from the dashboard
+#### Update a context via dashboard
 
 1. Log in to the Novu dashboard.
 2. Click **Contexts** on the sidebar.
 3. Click on the context you wish to edit from the context list on the Context page. 
 4. Modify its data object in the UI.
 5. Click **Save changes**.
 
-#### Update a Context using the API
+#### Update a context via API
 
 Novu provides an API to update an existing context. The `data` object is replaced entirely during updates (not merged). Include all fields you want to retain.
 
@@ -186,17 +211,17 @@ PATCH /v2/contexts/tenant/acme-corp
 }
 ```
 
-### Retrieving a single Context
+### Retrieve a single context
 
 You can retrieve a context to verify its data, confirm its creation, or inspect the metadata it holds.
 
-#### Retrieve a Context from the dashboard
+#### Retrieve a context via dashboard
 
 1. Log in to the Novu dashboard
 2. Click **Contexts** on the sidebar to view the list of all existing contexts.
 3. Click any context entry to see its details.
 
-#### Retrieve a Context using the API
+#### Retrieve a context via API
 
 Novu provides an API to retrieve a single, specific context by providing its `type` and `id` in the URL.
 
@@ -209,17 +234,17 @@ Here is an example:
 GET /v2/contexts/tenant/acme-corp
 ```
 
-### Listing or searching for Contexts
+### List or search for contexts
 
 You can list all contexts in your environment or search for specific ones by context type or ID.
 
-#### List or search Contexs from the dashboard
+#### List or search for contexs via dashboard
 
 1. Log in to the Novu dashboard
 2. Click **Contexts** on the sidebar to view all contexts.
 3. Use the search bar to filter by context type or ID.
 
-#### List or search Contexs using the API
+#### List or search for contexs via API
 
 Novu provides an API that lists or searches available contexts. Use pagination and search parameters to retrieve subsets efficiently.
 
@@ -228,21 +253,21 @@ GET /v2/contexts
 GET /v2/contexts?search=acme
 ```
 
-### Deleting a Context
+### Delete a context
 
 Delete a context if it’s no longer needed. This action permanently removes the context from your Novu environment. 
 
 <Callout type='warn'>This action cannot be undone, so ensure the context is no longer required by any active or historical workflows you might need to analyze.</Callout>
 
-#### Delete a Context from the dashboard
+#### Delete a context via dashboard
 
 1. Log in to the Novu dashboard.
 2. Click **Contexts** on the sidebar.
 3. Click on the **...** icon on the row of the context you want to remove.
 4. Click **Delete context**, a menu will appear.
 5. Click **Delete context**.
 
-#### Delete a Context using the API
+#### Delete a context via API
 
 Novu provides an API that you can use to delete a context. Once deleted, the context will no longer be available for use in new workflow executions.
 
@@ -254,4 +279,4 @@ Here is an example:
 
 ```
 DELETE /v2/contexts/tenant/acme-corp
-```
+```