Merge pull request #106504 from jeffhollan/premium-timeout

functions: clarifying timeout

Author: PRMerger9

articles/azure-functions/functions-premium-plan.md

@@ -61,7 +61,7 @@ Additional compute instances are automatically added for your app using the same
 
 ### Longer run duration
 
-Azure Functions in a Consumption plan are limited to 10 minutes for a single execution.  In the Premium plan, the run duration defaults to 30 minutes to prevent runaway executions. However, you can [modify the host.json configuration](./functions-host-json.md#functiontimeout) to make this 60 minutes for Premium plan apps.
+Azure Functions in a Consumption plan are limited to 10 minutes for a single execution.  In the Premium plan, the run duration defaults to 30 minutes to prevent runaway executions. However, you can [modify the host.json configuration](./functions-host-json.md#functiontimeout) to make this unbounded for Premium plan apps (guaranteed 60 minutes).
 
 ## Plan and SKU settings
 

articles/azure-functions/functions-scale.md

@@ -59,7 +59,7 @@ When you're using the Premium plan, instances of the Azure Functions host are ad
 
 * Perpetually warm instances to avoid any cold start
 * VNet connectivity
-* Unlimited execution duration
+* Unlimited execution duration (60 minutes guaranteed)
 * Premium instance sizes (one core, two core, and four core instances)
 * More predictable pricing
 * High-density app allocation for plans with multiple function apps