fix

Author: sl0thentr0py

develop-docs/sdk/overview.mdx

@@ -338,9 +338,9 @@ sure we swallow them gracefully and emit an error level log describing the failu
 
 As a **design principle**, we never capture Sentry events for exceptions happening within our SDKs, including within user-defined callbacks and hooks such as `before_send` or `traces_sampler`.
 
-The main justification for this is that we are already in an event capturing flow where the scope has been applied
-and capturing another event at that point in the lifecycle would lead to undefined behavior. In the worst case,
-we could create a busy loop of creating and sending events repeatedly till the system crashes.
+The reason we avoid captuing internal SDK exceptions is that we are already in an event capturing flow
+where the scope has been applied and capturing another event at that point in the lifecycle
+would lead to undefined behavior. In the worst case, we could create a busy loop of creating and sending events repeatedly till the system crashes.
 
 ## Concurrency (Scope and Hubs)