try to fix the link

Author: Ankcorn

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

@@ -246,27 +246,27 @@ To review whether your application is experiencing any downtime or returning any
 
 The **Errors by invocation status** chart shows the number of errors broken down into the following categories:
 
-| Error                            | Meaning                                                                                    |
-| -------------------------------- | ------------------------------------------------------------------------------------------ |
-| `Uncaught Exception`           	 | Your Worker code threw a JavaScript exception during execution.                            |
-| `Exceeded CPU Time Limits`			 | Worker exceeded CPU time limit or other resource constraints.                              |
-| `Exceeded Memory`                | Worker exceeded the memory limit during execution.                                         |
-| `Internal`                  		 | An internal error occurred in the Workers runtime.                                         |
+| Error                      | Meaning                                                         |
+| -------------------------- | --------------------------------------------------------------- |
+| `Uncaught Exception`       | Your Worker code threw a JavaScript exception during execution. |
+| `Exceeded CPU Time Limits` | Worker exceeded CPU time limit or other resource constraints.   |
+| `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 broken down into the following categories:
 
-| Client Disconnects               | Meaning                                                                                    |
-| -------------------------------- | ------------------------------------------------------------------------------------------ |
-| `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.                          |
+| Client Disconnects             | Meaning                                                                                                                                                     |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `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.
+[Workers Logs](/workers/observability/logs/workers-logs) is a powerful tool for debugging your Workers. It shows all the historic 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.
+To find all your errors in Workers Logs, you can use the following filter: `$metadata.error EXISTS`. This will show 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.
+All the possible outcome values can be found in the [Workers Trace Event](/logs/reference/log-fields/account/workers_trace_events/#outcome) reference.
 
 ## Debug exceptions from `Wrangler`