Simplify KVEval example in ASH work_event docs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: alyshanjahani-crl

src/current/v26.3/active-session-history.md

@@ -95,7 +95,7 @@ Each sample is attributed to a workload via the `workload_type` and `workload_id
 
 The `work_event` column identifies the specific activity a goroutine was performing or waiting on when it was sampled, such as `LockWait`, `DistSenderRemote`, or `KVEval`. It is the most precise description of what a sample represents, and it is generally the column to group or filter by when analyzing ASH data.
 
-The `work_event_type` column is a coarse category associated with each `work_event`: `CPU`, `IO`, `LOCK`, `NETWORK`, `ADMISSION`, or `OTHER`. This category is a static, predefined mapping: every sample with a given `work_event` always has the same `work_event_type`, regardless of what the goroutine was actually doing at the time. As a result, `work_event_type` describes the resource that a `work_event` is generally concerned with, not the resource the sample was actually consuming. For example, a `KVEval` sample is categorized as `IO`, but the goroutine may have been using CPU to evaluate a request against data that was already cached in memory.
+The `work_event_type` column is a coarse category associated with each `work_event`: `CPU`, `IO`, `LOCK`, `NETWORK`, `ADMISSION`, or `OTHER`. This category is a static, predefined mapping: every sample with a given `work_event` always has the same `work_event_type`, regardless of what the goroutine was actually doing at the time. As a result, `work_event_type` describes the resource that a `work_event` is generally concerned with, not the resource the sample was actually consuming. For example, a `KVEval` sample is categorized as `IO`, but the goroutine may have been using CPU.
 
 {{site.data.alerts.callout_info}}
 Do not rely on `work_event_type` alone to determine whether a workload is CPU-bound, I/O-bound, or network-bound. Instead, look at the specific `work_event` values and the workloads they are attributed to, and correlate them with other signals such as [CPU profiles]({% link {{ page.version.version }}/automatic-cpu-profiler.md %}) and [hardware metrics]({% link {{ page.version.version }}/ui-hardware-dashboard.md %}).