Merge pull request #125766 from RoyVoetman/patch-2

Update durable-functions-perf-and-scale.md

Author: ShannonLeavitt

articles/azure-functions/durable/durable-functions-perf-and-scale.md

@@ -31,7 +31,7 @@ On a premium plan, automatic scaling can help to keep the number of workers (and
 
 ### CPU usage
 
-**Orchestrator functions** are executed on a single thread to ensure that execution can be deterministic across many replays. Because of this single-threaded execution, it's important that orchestrator function threads do not perform CPU-intensive tasks, do I/O, or block for any reason. Any work that may require I/O, blocking, or multiple threads should be moved into activity functions.
+**Orchestrator functions** run their logic multiple times due to their replaying behavior. It's therefore important that orchestrator function threads do not perform CPU-intensive tasks, do I/O, or block for any reason. Any work that may require I/O, blocking, or multiple threads should be moved into activity functions.
 
 **Activity functions** have all the same behaviors as regular queue-triggered functions. They can safely do I/O, execute CPU intensive operations, and use multiple threads. Because activity triggers are stateless, they can freely scale out to an unbounded number of VMs.