Update src/content/docs/workers/platform/limits.mdx

Co-authored-by: Steve Faulkner <[email protected]>

Author: irvinebroque

src/content/docs/workers/platform/limits.mdx

@@ -150,7 +150,7 @@ Routes in fail closed mode will display a Cloudflare `1027` error page to visito
 
 Each [isolate](/workers/reference/how-workers-works/#isolates) your Worker's code runs in can consume up to 128 MB of memory. This includes both memory used by the JavaScript heap, and memory explicitly allocated in [WebAssembly](/workers/runtime-apis/webassembly/). Note that this limit is per-isolate, not per-invocation of your Worker. A single isolate can handle many concurrent requests.
 
-If at any point in time an isolate running your Worker uses more than 128 MB of memory, rather than immediately failing with an error, the Workers runtime will attempt to allow in-flight requests to that isolate to complete, and will create a new isolate for your Worker. In this process, the Workers runtime still may cancel one or more incoming requests, but ensures that if your Worker exceeds memory limits, it is automatically restarted as gracefully as possible.
+When an isolate running your Worker exceeds 128 MB of memory, the Workers runtime handles this gracefully instead of failing immediately. It allows in-flight requests to complete while simultaneously creating a new isolate for your Worker. While this approach typically preserves request handling, during periods of extremely high load, some incoming requests may be cancelled to maintain system stability.
 
 To view out-of-memory errors (OOM), as well as CPU limit overages: