fix(docs): Widget Library docs bug fixes (#4667)

Mis-named widget and updating the query condition.

Author: shruthilayaj

src/docs/product/dashboards/widget-library/index.mdx

@@ -14,7 +14,7 @@ The widget library contains a collection of prebuilt widgets you can add to your
 
 The library includes the following widgets:
 
-- **Distribution Duration**: A multi-y axis chart visualizing the distribution of transaction duration across various percentiles (p50, p75, and p95)
+- **Duration Distribution**: A multi-y axis chart visualizing the distribution of transaction duration across various percentiles (p50, p75, and p95)
 - **High Throughput Transactions**: The top five transactions with the largest number of events
 - **LCP by Country**: World map showing the p75 of page load times for each country
 - **Miserable Users**: The total number of unique users who have experienced slow transactions (transaction duration greater than 1200ms)
@@ -29,23 +29,23 @@ You can change the title, queries, fields, visualization types, and sort order o
 
 ### Performance across release versions
 
-To monitor how your app is performing on a certain release, you can modify the "Distribution Duration" widget by adding the release version to the search condition:
+To monitor how your app is performing on a certain release, you can modify the "Duration Distribution" widget by adding the release version to the search condition:
 
-- Search condition 1: `!event.type:error release.version:{version}`
+- Search condition 1: `event.type:transaction release.version:{version}`
 
 To compare performance with another release version, you can add another query by clicking the "Add Query" button and querying for a different release version:
 
-- Search condition 2: `!event.type:error release.version:{another_version}`
+- Search condition 2: `event.type:transaction release.version:{another_version}`
 
 You can also compare performance before/and after a certain version with the following conditions:
 
-- Search condition 1: `!event.type:error release.version:<{version}`
-- Search condition 2: `!event.type:error release.version:>={version}`
+- Search condition 1: `event.type:transaction release.version:<{version}`
+- Search condition 2: `event.type:transaction release.version:>={version}`
 
 
 ### Response thresholds
 
-The "Distribution Duration" widget shows the spread of transaction duration times. This visualization can be modified to show if transaction durations are within certain target thresholds and present them as "satisfactory", "tolerable", or "frustrating" transactions. To create this type of visualization, change the "Visualization Display" to "Area Chart". Area charts stack results and are more appropriate for results that are cumulative:
+The "Duration Distribution" widget shows the spread of transaction duration times. This visualization can be modified to show if transaction durations are within certain target thresholds and present them as "satisfactory", "tolerable", or "frustrating" transactions. To create this type of visualization, change the "Visualization Display" to "Area Chart". Area charts stack results and are more appropriate for results that are cumulative:
 
 - Visualization Display: `Area Chart`
 
@@ -55,15 +55,15 @@ Set one of the y-axis values to `count()` and remove the other two axes:
 
 To the first query, add the search condition for satisfactory transaction duration (this example uses 300ms as the satisfactory response threshold):
 
-- Search condition 1: `!event.type:error transaction.duration:<300`
+- Search condition 1: `event.type:transaction transaction.duration:<300`
 
 Add another query for the tolerable condition by clicking the "Add Query" button. In this example, we're using the [Apdex](/product/performance/metrics/#apdex) definition where tolerable response times are between the satisfactory threshold and four times the satisfactory threshold:
 
-- Search condition 2: `!event.type:error (transaction.duration:<1200 AND transaction.duration:>=300)`
+- Search condition 2: `event.type:transaction (transaction.duration:<1200 AND transaction.duration:>=300)`
 
 Finally, add a third query for for the frustrating transaction duration:
 
-- Search condition 3: `!event.type:error transaction.duration:>=1200`
+- Search condition 3: `event.type:transaction transaction.duration:>=1200`
 
 The chart now shows cumulative counts at different response time thresholds.