Update flex-consumption-how-to.md

Author: nzthiago

articles/azure-functions/flex-consumption-how-to.md

@@ -445,7 +445,12 @@ You can't currently change the instance memory size setting for your app using V
 
 ## Set always ready instance counts
 
-When creating an app in a Flex Consumption plan, you can set the always ready instance count for specific groups (HTTP or Durable triggers) and triggers. For individual functions, use the format `function:<FUNCTION_NAME>=n`.
+You can set a number of always ready instances for the [Per-function scaling](flex-consumption-plan.md#per-function-scaling) groups or individual functions, to keep your functions loaded and ready to execute. There are three special groups, as in per-function scaling: 
++ `http` - all the HTTP triggered functions in the app are scaled together into their own instances.  
++ `durable` - all the Durable triggered functions (Orchestration, Activity, Entity) in the app are scaled together into their own instances. Use `durable` as the name for the name value pair setting.
++ `blob` - all the event grid blob storage triggered functions in the app are scaled together into their own instances. Use `blob` as the name for the name value pair setting.
+
+Use `http`, `durable` or `blob` as the name for the name value pair setting to configure Always Ready counts for these groups. For all othere trigger types you need to configure Always Ready for each individual function using the format `function:<FUNCTION_NAME>=n`.
 
 ### [Azure CLI](#tab/azure-cli)