fix warnings 2

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/durable-functions-overview.md

@@ -34,7 +34,7 @@ For language-specific requirements and package details, see [Durable Functions b
 
 ## How to get started
 
-1. Create a new Azure Functions app by using one of the language quickstarts in [Quickstarts and samples](#quickstarts-and-samples).
+1. Create a new Azure Functions app by using one of the language quickstarts in [Supported languages](#supported-languages).
 1. Add an orchestrator function and one or more activity functions.
 1. Choose and configure your backend in [Durable Functions storage providers](durable-functions-storage-providers.md). The recommended option is [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).
 1. Run and test locally with Azure Functions Core Tools.

includes/functions-timeout-duration.md

@@ -21,7 +21,7 @@ The following table shows the default and maximum values (in minutes) for specif
 | **[Container Apps](../articles/container-apps/functions-overview.md)** | 30 | Unbounded<sup>5</sup> | 
 | **[Consumption plan](../articles/azure-functions/consumption-plan.md)** | 5 | 10 |  
 
-1. Regardless of the function app timeout setting, 230 seconds is the maximum amount of time that an HTTP triggered function can take to respond to a request. This limit exists because of the [default idle timeout of Azure Load Balancer](../articles/app-service/faq-availability-performance-application-issues.yml#why-does-my-request-time-out-after-230-seconds). For longer processing times, consider using the [Durable Functions async pattern](../articles/azure-functions/durable/durable-functions-overview.md#async-http) or [defer the actual work and return an immediate response](../articles/azure-functions/performance-reliability.md#avoid-long-running-functions).
+1. Regardless of the function app timeout setting, 230 seconds is the maximum amount of time that an HTTP triggered function can take to respond to a request. This limit exists because of the [default idle timeout of Azure Load Balancer](../articles/app-service/faq-availability-performance-application-issues.yml#why-does-my-request-time-out-after-230-seconds). For longer processing times, consider using the [Durable Functions async pattern](../articles/azure-functions/durable/durable-functions-http-features.md#async-operation-tracking) or [defer the actual work and return an immediate response](../articles/azure-functions/performance-reliability.md#avoid-long-running-functions).
 2. There's no maximum execution timeout duration enforced. However, the grace period given to a function execution is 60 minutes [during scale in](../articles/azure-functions/event-driven-scaling.md#scale-in-behaviors) for the Flex Consumption and Premium plans, and a grace period of 10 minutes is given during platform updates.
 3. Requires the App Service plan be set to [Always On](/azure/azure-functions/dedicated-plan#always-on). A grace period of 10 minutes is given during platform updates.
 4. The default timeout for version 1.x of the Functions host runtime is _unbounded_.