update

Author: nytian

articles/azure-functions/durable/TOC.yml

@@ -174,7 +174,7 @@
     items:
     - name: Upgrade Durable Functions extension version
       href: durable-functions-extension-upgrade.md
-    - name: Durable Function Troubleshooting Guide
+    - name: Durable Functions Troubleshooting Guide
       href: durable-functions-troubleshooting-guide.md
 - name: Resources
   items:

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

@@ -68,7 +68,7 @@ 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 is .NET in-process, consider enabling [extended sessions](./durable-functions-azure-storage-provider.md#extended-sessions).  
+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.
 
 3. Check for performance and scalability bottlenecks. 
@@ -171,6 +171,8 @@ traces
 | project timestamp, appName, severityLevel, pid, taskName, eventType, message, details, messageId, partitionId, instanceId, executionId, age, latencyMs, dequeueCount, eventCount, newEvents, taskHub, account, extendedSession, sdkVersion
 ```
 
+Below is a list of the columns projected by the queries above and their respective descriptions.
+
 |Column |Description |
 |-------|------------|
 |pid|Process ID of the function app instance. This is useful for determining if the process was recycled while an orchestration was executing.|