PR feedback

Author: mydea

docs/platforms/javascript/common/enriching-events/scopes/index.mdx

@@ -147,7 +147,9 @@ even call <PlatformIdentifier name="clear" /> to briefly remove all context info
 <PlatformCategorySection supported={['server']}>
 ## Using `withIsolationScope`
 
-`withIsolationScope` works fundamentally the same as `withScope`, but it will fork the isolation scope instead of the current scope. Generally, the isolation scope is meant to be forked less frequently than the current scope, and in most cases the SDK will handle this automatically for you. But in cases where you e.g. want to capture SDK events in a middleware (which happens before the request is processed and thus before the SDKs automatic handling), or if you want to isolate a non-request process (e.g. a background job), you can use `withIsolationScope` to create a new isolation scope that is only active for the duration of the callback:
+`withIsolationScope` works fundamentally the same as `withScope`, but it will fork the isolation scope instead of the current scope. Generally, the isolation scope is meant to be forked less frequently than the current scope, and in most cases the SDK will handle this automatically for you.
+
+But in cases where you e.g. want to isolate a non-request process (e.g. a background job), you can use `withIsolationScope` to create a new isolation scope that is only active for the duration of the callback:
 
 <PlatformContent includePath="enriching-events/scopes/with-isolation-scope" />
 </PlatformCategorySection>