update commit

Author: nytian

articles/azure-functions/durable/durable-functions-troubleshooting-guide.md

@@ -69,10 +69,10 @@ Heavy data processing, internal errors, and insufficient compute resources can c
 1. Check the Durable Task Framework traces for warnings or errors for the impacted orchestration instance ID. A sample query can be found in the [Trace Errors/Warnings section](#trace-errorswarnings).
 
 2. If your app utilizes the .NET in-process model, consider enabling [extended sessions](./durable-functions-azure-storage-provider.md#extended-sessions). 
-   Excessive history load can result in slow orchestrator processing.
+   This minimizes history loads, which can slow down processing.
 
 3. Check for performance and scalability bottlenecks. 
-   Application performance depends on many factors. For example, high CPU usage or large memory consumption can result in delays. Read [Performance and scale in Durable Functions](./durable-functions-perf-and-scale.md) for detailed guidance.
+   Application performance depends on many factors. For example, high CPU usage, or large memory consumption can result in delays. Please read [Performance and scale in Durable Functions](./durable-functions-perf-and-scale.md) for detailed guidance.
 
 ## Sample Queries