fix(DT): Changed exception references to errors.

src/content/docs/distributed-tracing/ui-data/understand-use-distributed-tracing-ui.mdx

@@ -425,7 +425,7 @@ Here are some additional distributed tracing UI details, rules, and limits:
     id="error-tips"
     title="How to understand span errors"
   >
-    Span-level errors show you where errors originated in a process, how they bubbled up, and where they were handled. Every span that ends with an exception is shown with an error in the UI and contributes to the total error count for that trace.
+    Span-level errors show you where errors originated in a process, how they bubbled up, and where they were handled. Every span that ends with an error is shown with an error in the UI and contributes to the total error count for that trace.
 
     Here are some general tips about understanding span errors:
 
@@ -453,11 +453,11 @@ Here are some additional distributed tracing UI details, rules, and limits:
       <tbody>
         <tr>
           <td>
-            Spans ending in exceptions
+            Spans ending in errors
           </td>
 
           <td>
-            An exception that leaves the boundary of a span results in an error on that span and on any ancestor spans that also exit with an error, until the exception is caught or exits the transaction. You can see if an exception is caught in an ancestor span.
+            An error that leaves the boundary of a span results in an error on that span and on any ancestor spans that also exit with an error, until the error is caught or exits the transaction. You can see if an error is caught in an ancestor span.
           </td>
         </tr>