diff --git a/docs/platforms/javascript/common/enriching-events/process-isolation/index.mdx b/docs/platforms/javascript/common/enriching-events/process-isolation/index.mdx
index 09a8f9ddc566ff..7f64348e83c360 100644
--- a/docs/platforms/javascript/common/enriching-events/process-isolation/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/process-isolation/index.mdx
@@ -19,11 +19,11 @@ notSupported:
- javascript
---
-In server-side environments, the isolation scope is automatically forked around request boundaries. This means that each request will have its own isolation scope, and data set on the isolation scope will only apply to events captured during that request. This is done automatically by the SDK.
+In server-side environments, the isolation scope automatically forks around request boundaries. This is done automatically by the SDK. As a result, each request has its own isolation scope, and data set on the isolation scope only applies to events captured during that request.
-However, there are also other cases where you may want to have isolation, for example in background jobs or when you want to isolate a specific part of your code. In these cases, you can use `Sentry.withIsolationScope()` to create a new isolation scope that is valid inside of the callback you pass to it - see [Using withIsolationScope](../scopes/#using-withisolationscope).
+However, there are also other times when you may want to have isolation, for example, in background jobs or when you want to isolate a specific part of your code. In these cases, you can use `Sentry.withIsolationScope()` to create a new isolation scope that's valid inside of the callback you pass to it. Learn more about using [withIsolationScope](../scopes/#using-withisolationscope).
-The following example shows how you can use `withIsolationScope` to attach data for a specific job run:
+The following example shows how you can use `withIsolationScope` to attach data to a specific job run:
```javascript
async function job(jobId) {