Update deployment methods for multi-container groups

Author: staleycyn

learn-pr/wwl-azure/configure-azure-container-instances/includes/4-implement-container-groups.md

@@ -10,11 +10,13 @@ Let's review some of details about container groups for Azure Container Instance
 
 - Azure Container Instances allocates resources to a multi-container group by adding together the resource requests of all containers in the group. Resources can include items such as CPUs, memory, and GPUs.
 
-- There are two common ways to deploy a multi-container group: Azure Resource Manager (ARM) templates and YAML files.
+- There are three common ways to deploy a multi-container group.
 
-  - **ARM template**. An ARM template is recommended for deploying other Azure service resources when you deploy your container instances, such as an Azure Files file share.
+  - **Azure Resource Manager template**. JSON-based infrastructure as code, ideal when deploying alongside other Azure resources.
+
+  - **Bicep**. Microsoft's recommended infrastructure as code language, more concise than Azure Resource Manager templates. Bicep includes full IntelliSense support.
 
-  - **YAML file**. Due to the concise nature of the YAML format, a YAML file is recommended when your deployment includes only container instances.
+  - **YAML files**. Container-focused format, ideal for deployments that include only container instances.
 
 - Container groups can share an external-facing IP address, one or more ports on the IP address, and a DNS label with an FQDN.
 
@@ -49,4 +51,4 @@ Consider the following scenarios for working with multi-container groups. Think
 
 - **Consider app monitoring**. Enable monitoring for your app with a multi-container group. A monitoring container periodically makes a request to your application container to ensure your app is running and responding correctly. The monitoring container raises an alert if it identifies possible issues with your app.
 
-- **Consider front-end and back-end support**. Create a multi-container group to hold your front-end container and back-end container. The front-end container can serve a web app. The back-end container can run a service to retrieve data.
+- **Consider front-end and back-end support**. Create a multi-container group to hold your front-end container and back-end container. The front-end container can serve a web app. The back-end container can run a service to retrieve data.