Apply review edits to monitor conversations page (WBDOCS-1924)

Capitalize Calls to match Weave terminology, remove cross-reference
from monitors.mdx, and soften wording in timeout section.

Made-with: Cursor

Author: anastasiaguspan

weave/guides/evaluation/monitor-conversations.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Monitor conversations"
-description: "Score grouped calls after a conversation goes idle using debounced scoring"
+description: "Score grouped Calls after a conversation goes idle using debounced scoring"
 ---
 
-When your application handles multi-turn conversations, such as audio calls or chat threads, you might need to score the entire conversation rather than individual calls. Debounced scoring lets you group related calls and score them after the conversation goes idle, so your scorer has access to the full context.
+When your application handles multi-turn conversations, such as audio calls or chat threads, you might need to score the entire conversation rather than individual Calls. Debounced scoring in W&B Weave lets you group related Calls and score them after the conversation goes idle, so your scorer has access to the full context.
 
-For example, if your application uses OpenAI's Realtime APIs, each trace contains multiple `realtime.response` calls. Debounced scoring waits for the conversation to go idle, then scores the relevant calls as a group.
+For example, if your application uses OpenAI's Realtime APIs, each trace contains multiple `realtime.response` Calls. Debounced scoring waits for the conversation to go idle, then scores the relevant Calls as a group.
 
 For general monitor setup, see [Set up monitors](/weave/guides/evaluation/monitors).
 
@@ -15,35 +15,35 @@ To enable debounced scoring on a monitor:
 
 1. [Create a new monitor](/weave/guides/evaluation/monitors#how-to-create-a-monitor-in-weave) or edit an existing one.
 2. Toggle **Debounced Scoring** on. This reveals the following fields:
-   - **Aggregation field**: The field used to group calls. Select **Trace Id** to group calls within a single trace, or **Thread Id** to group calls across a broader conversation thread.
-   - **Aggregation method**: How calls in the group are scored. Select **Last message** to score only the most recent call in the group, or **All messages** to include all calls in the group.
-   - **Timeout (minutes)**: How long to wait after the last call completes before scoring. After the timeout elapses, Weave checks whether a newer call has arrived in the group. If not, Weave scores the group.
+   - **Aggregation field**: The field used to group Calls. Select **Trace Id** to group Calls within a single trace, or **Thread Id** to group Calls across a broader conversation thread.
+   - **Aggregation method**: How Calls in the group are scored. Select **Last message** to score only the most recent Call in the group, or **All messages** to include all Calls in the group.
+   - **Timeout (minutes)**: How long to wait after the last Call completes before scoring. After the timeout elapses, Weave checks whether a newer Call has arrived in the group. If not, Weave scores the group.
 3. Configure the **LLM-as-a-judge configuration** section as you would for any monitor. See [Set up monitors](/weave/guides/evaluation/monitors#how-to-create-a-monitor-in-weave) for details on these fields.
 4. Select **Create monitor** or **Update monitor**.
 
 ## Choose an aggregation method
 
-### Last message (recommended)
+### Last message (Recommended)
 
-Use the **Last message** method when each call in the conversation contains the full conversation history. This is the case when you use OpenAI's Realtime APIs, where every `realtime.response` call contains the complete audio conversation up to that point.
+Use the **Last message** method when each Call in the conversation contains the full conversation history. This is the case when you use OpenAI's Realtime APIs, where every `realtime.response` Call contains the complete audio conversation up to that point.
 
-Set the **Aggregation field** to **Trace Id** and the **Aggregation method** to **Last message**. After the timeout elapses, Weave scores only the most recent call in the trace, which already contains the full conversation.
+Set the **Aggregation field** to **Trace Id** and the **Aggregation method** to **Last message**. After the timeout elapses, Weave scores only the most recent Call in the trace, which already contains the full conversation.
 
-This method uses fewer resources because only one call per group is scored.
+This method uses fewer resources because only one Call per group is scored.
 
 ### All messages
 
-Use the **All messages** method when individual calls do not contain the full conversation history. In this case, Weave extracts content from every call in the aggregation group and passes it all to the scorer.
+Use the **All messages** method when individual Calls do not contain the full conversation history. In this case, Weave extracts content from every Call in the aggregation group and passes it all to the scorer.
 
-Set the **Aggregation field** to **Thread Id** for broader grouping flexibility, and the **Aggregation method** to **All messages**.
+You can set the **Aggregation field** to **Thread Id** for broader grouping flexibility, and the **Aggregation method** to **All messages**.
 
-This method uses more resources because the scorer processes every call in the group.
+This method uses more resources because the scorer processes every Call in the group.
 
 ## Timeout considerations
 
 The timeout value controls the trade-off between scoring latency and accuracy:
 
-- **Shorter timeouts** score conversations faster but risk scoring before the conversation is complete. Use shorter timeouts for debugging or when conversations have predictable end points.
-- **Longer timeouts** wait longer to confirm the conversation is idle, reducing the chance of premature scoring. Use longer timeouts in production, especially for conversations with variable pauses between calls. Longer timeouts increase server load.
+- Shorter timeouts score conversations faster but risk scoring before the conversation is complete. Use shorter timeouts for debugging or when conversations have predictable end points.
+- Longer timeouts wait longer to confirm the conversation is idle, reducing the chance of premature scoring. Use longer timeouts in production, especially for conversations with variable pauses between Calls. Longer timeouts increase server load.
 
-For example, a timeout of `0.25` minutes (15 seconds) is useful during development, while a timeout of several minutes is more appropriate for production workloads.
+For example, a timeout of `0.25` minutes (15 seconds) is useful during development, while a timeout of several minutes might be appropriate for production workloads.

weave/guides/evaluation/monitors.mdx

@@ -9,8 +9,6 @@ You can monitor text, images, and audio in your application's input and output.
 
 Monitors require no code changes to your application. Set them up using the W&B Weave UI.
 
-To score grouped calls in multi-turn conversations or audio threads after they go idle, see [Monitor conversations](/weave/guides/evaluation/monitor-conversations).
-
 If you need to actively intervene in your application's behavior based on scores, use [guardrails](/weave/guides/evaluation/guardrails) instead.
 
 ## How to create a monitor in Weave