Add example snippets

Author: ggailey777

articles/azure-functions/functions-infrastructure-as-code.md

@@ -3,7 +3,7 @@ title: Automate function app resource deployment to Azure
 description: Learn how to build, validate, and use a Bicep file or an Azure Resource Manager template to deploy your function app and related Azure resources.
 ms.assetid: d20743e3-aab6-442c-a836-9bcea09bfd32
 ms.topic: conceptual
-ms.date: 07/16/2024
+ms.date: 08/22/2024
 ms.custom: fasttrack-edit, devx-track-bicep, devx-track-arm-template, linux-related-content
 zone_pivot_groups: functions-hosting-plan
 ---
@@ -1834,7 +1834,33 @@ These application settings are required for container deployments:
 
 Keep these considerations in mind when working with site and application settings using Bicep files or ARM templates:
 ::: zone pivot="flex-consumption-plan"   
-+ The optional `alwaysReady` setting contains an array of one or more `{name,instanceCount}` objects, with one for each [per-function scale group](flex-consumption-plan.md#per-function-scaling). These are the scale groups being used to make always-ready scale decisions. The values assigned to `name` and `instanceCount` are the scale group name and always ready instance count, respectively.   
++ The optional `alwaysReady` setting contains an array of one or more `{name,instanceCount}` objects, with one for each [per-function scale group](flex-consumption-plan.md#per-function-scaling). These are the scale groups being used to make always-ready scale decisions. This example sets always-ready counts for both the `http` group and function named `helloworld`, which is of a non-gouped trigger type:
+	### [Bicep](#tab/bicep)
+	```bicep
+	alwaysReady: [
+	    {
+ 		name: 'http'
+ 		instanceCount: 2
+ 	    }
+	    {
+ 		name: 'function:helloworld'
+ 		instanceCount: 1
+ 	    }
+	]
+ 	```
+	### [ARM template](#tab/json)
+	```json
+	"alwaysReady": [
+	    {
+ 		"name": "http",
+ 		"instanceCount": 2
+ 	    },
+	    {
+ 		"name": "function:helloworld",
+ 		"instanceCount": 1
+ 	    }
+	]
+ 	```
 ::: zone-end
 ::: zone pivot="consumption-plan,premium-plan,dedicated-plan" 
 + There are important considerations for when you should set `WEBSITE_CONTENTSHARE` in an automated deployment. For detailed guidance, see the [`WEBSITE_CONTENTSHARE`](functions-app-settings.md#website_contentshare) reference.