ref(develop): Clarify synthetic flag in exception mechanism

Author: Lms24

develop-docs/sdk/data-model/event-payloads/exception.mdx

@@ -79,14 +79,17 @@ from the operating system or runtime APIs, as well as mechanism-specific values.
 
 `synthetic`
 
-: An optional flag indicating that this error is synthetic. Synthetic errors
-are errors that carry little meaning by themselves. This may be because they
-are created at a central place (like a crash handler), and are all
-called the same: `Error`, `Segfault` etc. When the flag is set, Sentry will then
-try to use other information (top in-app frame function) rather than exception
-type and value in the UI for the primary event display. This flag should be set
-for all "segfaults" for instance as every single error group would look very
-similar otherwise.
+: An optional flag indicating that this error is synthetic. Synthetic errors are errors that
+carry little meaning by themselves. This may be because they are created at a central
+place (like a crash handler), and are all called the same: `Error`, `Segfault` etc.
+When the flag is set, Sentry will then try to use other information (top in-app frame
+function) rather than the exception type and value in the UI for the primary event display.
+Furthermore, if this flag is set, Sentry will ignore the exception `type` when grouping the
+exception into issues.
+: This flag should be set for all "segfaults" for instance as every single error group would
+look very similar otherwise. Also, errors the SDK creates to add a stack trace to events
+that don't have one themselves should be marked as `synthetic`. For example, when users
+set `attachStackTrace: true` and capture a string message via `captureException` or `captureMessage`.
 
 `exception_id`
 
@@ -118,9 +121,10 @@ mechanism (see [meta information](#meta-information)).
 this mechanism.
 
 <Alert title="Note" level="warning">
-The <code>type</code> attribute is required to send any exception mechanism attribute, even
-if the SDK cannot determine the specific mechanism. In this case, set the <code>type</code>
-to <code>generic</code>. See below for an example.
+  The <code>type</code> attribute is required to send any exception mechanism
+  attribute, even if the SDK cannot determine the specific mechanism. In this
+  case, set the <code>type</code>
+  to <code>generic</code>. See below for an example.
 </Alert>
 
 ### Meta information
@@ -371,4 +375,5 @@ Exception group:
   ]
 }
 ```
+
 `;