Fixing line breaks for timeout

Author: nzthiago

includes/functions-timeout-duration.md

@@ -20,7 +20,7 @@ The following table shows the default and maximum values (in minutes) for specif
 | **[Premium plan](../articles/azure-functions/functions-premium-plan.md)** |  30<sup>3</sup> | Unlimited<sup>3</sup> |  
 | **[Dedicated plan](../articles/azure-functions/dedicated-plan.md)** |  30<sup>4</sup> | Unlimited<sup>3</sup> |  
 
-<sup>1</sup> 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 is 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).
-<sup>2</sup> In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees as the platform might need to terminate your instances during scale-in, deployments, or to apply updates.
-<sup>3</sup> The default timeout for version 1.x of the Functions runtime is _unlimited_.
+<sup>1</sup> 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 is 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).<br>
+<sup>2</sup> In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees as the platform might need to terminate your instances during scale-in, deployments, or to apply updates.<br>
+<sup>3</sup> The default timeout for version 1.x of the Functions runtime is _unlimited_.<br>
 <sup>4</sup> Guaranteed for up to 60 minutes. [OS and runtime patching](../articles/app-service/overview-patch-os-runtime.md), vulnerability patching, and [scale in behaviors](../articles/azure-functions/event-driven-scaling.md#scale-in-behaviors) can still cancel function executions so [ensure to write robust functions](../articles/azure-functions/functions-best-practices.md#write-robust-functions).