improve the workers observability errors documentation

Author: Ankcorn

src/content/docs/workers/observability/errors.mdx

@@ -242,11 +242,9 @@ To review whether your application is experiencing any downtime or returning any
 2. In **Account Home**, select **Workers & Pages**.
 3. In **Overview**, select your Worker and review your Worker's metrics.
 
-A `responseStreamDisconnected` event `outcome` occurs when one end of the connection hangs up during the deferred proxying stage of a Worker request flow. This is regarded as an error for request metrics, and presents in logs as a non-error log entry. It commonly appears for longer lived connections such as WebSockets.
-
 ### Worker Errors
 
-The `Errors by invocation status` chart shows the number of errors that occurred. This graph is chart down into the following categories:
+The **Errors by invocation status** chart shows the number of errors broken down into the following categories:
 
 | Error                            | Meaning                                                                                    |
 | -------------------------------- | ------------------------------------------------------------------------------------------ |
@@ -255,18 +253,20 @@ The `Errors by invocation status` chart shows the number of errors that occurred
 | `Exceeded Memory`                | Worker exceeded the memory limit during execution.                                         |
 | `Internal`                  		 | An internal error occurred in the Workers runtime.                                         |
 
-The `Client disconnected by type` chart shows the number of client disconnect errors that occurred. This graph is chart down into the following categories:
+The **Client disconnected by type** chart shows the number of client disconnect errors broken down into the following categories:
 
 | Client Disconnects               | Meaning                                                                                    |
 | -------------------------------- | ------------------------------------------------------------------------------------------ |
-| `Response Stream Disconnected`   | Connection was terminated while streaming the response (common with WebSockets).           |
+| `Response Stream Disconnected`   | Connection was terminated during the deferred proxying stage of a Worker request flow. It commonly appears for longer lived connections such as WebSockets.           |
 | `Cancelled`                      | The Client disconnected before the Worker completed its response.                          |
 
 ## Debug exceptions with Workers Logs
 
 [Workers Logs](/workers/observability/logs/workers-logs) is a powerful tool for debugging your Workers. It allows you to see the logs generated by your Worker, including any uncaught exceptions that occur during execution.
 
-To find all your errors in Workers Logs, you can use the following filter: `$metadata.error EXISTS`. This will show you all the logs that have an error associated with them. You can also filter by `$workers.outcome` to find the requests that resulted in an error. For example, you can filter by `$workers.outcome = "exception"` to find all the requests that resulted in an uncaught exception. All the possible outcome values can be found in the [Workers Trace Events](logs/reference/log-fields/account/workers_trace_events/#outcome) Reference.
+To find all your errors in Workers Logs, you can use the following filter: `$metadata.error EXISTS`. This will show you all the logs that have an error associated with them. You can also filter by `$workers.outcome` to find the requests that resulted in an error. For example, you can filter by `$workers.outcome = "exception"` to find all the requests that resulted in an uncaught exception.
+
+All the possible outcome values can be found in the [Workers Trace Events](logs/reference/log-fields/account/workers_trace_events/#outcome) reference.
 
 ## Debug exceptions from `Wrangler`