updates3

Author: LiSeda

learn-pr/achievements/learn.azure.build-reusable-bicep-templates-parameters.badge.yml renamed to learn-pr/achievements/learn.azure.build-reusable-bicep-files-parameters.badge.yml

@@ -1,6 +1,6 @@
 The Azure Developer CLI (`azd`) can provision resources in Azure using infrastructure as code (IaC) files written in either Bicep or Terraform. Infrastructure as code allows you to define infrastructure resources and configurations in declarative definition files that reliably generate the same environments every time they're deployed. `azd` executes these files to create the Azure resources required to host your app. You can learn more about infrastructure as code in the [What is infrastructure as code?](/devops/deliver/what-is-infrastructure-as-code) documentation. 
 
-In this unit, you'll add Bicep code to your template to provision the necessary resources for your app. Previous knowledge of Bicep isn't required to complete this module. However, if you plan to work with `azd` templates extensively, it's a good idea to become familiar with at least the basics of Bicep or Terraform. Learn more about Bicep on the [Fundamentals of Bicep](/training/paths/fundamentals-bicep/) training path.
+In this unit, you'll add Bicep code to your template to provision the necessary resources for your app. Previous knowledge of Bicep isn't required to complete this module. However, if you plan to work with `azd` templates extensively, it's a good idea to become familiar with at least the basics of Bicep or Terraform. Learn more about Bicep in the [Fundamentals of Bicep](/training/paths/fundamentals-bicep/) training path.
 
 The Bicep or Terraform files for your template live in the `infra` folder. The `infra` folder of the Bicep starter template you selected contains the following components as a starting point:
 
@@ -9,7 +9,7 @@ The Bicep or Terraform files for your template live in the `infra` folder. The `
 * `main.parameters.json` - A JSON file that defines default values for important template parameters, such as the default Azure location or the environment name.
 * `core` - A subfolder that includes a variety of reusable Bicep files you can use to generate common Azure resources by simply passing in configuration parameters.
 
-You can define and provision the required Azure resources for your app by updating the `main.bicep` file and creating custom Bicep files, or leveraging the templates in the `core` folder. `Main.bicep` generally orchestrates the execution of other Bicep modules by passing parameters between them. For this example, you'll create an additional minimal Bicep module to define the Azure App Service that will host your application.
+You can define and provision the required Azure resources for your app by updating the `main.bicep` file and creating custom Bicep files or bys leveraging the templates in the `core` folder. `Main.bicep` generally orchestrates the execution of other Bicep modules by passing parameters between them. For this example, you'll create an additional minimal Bicep module to define the Azure App Service that will host your application.
 
 1. Inside of the `infra` folder of your template, create a new file called `app.bicep`.
 

learn-pr/azure/build-first-azd-template/includes/4-create-infrastructure.md

@@ -20,7 +20,7 @@ In this module, you'll extend a Bicep file by using conditions and loops. You'll
 
 ## What is the main goal?
 
-By the end of this module, you'll be able to create Bicep files by using conditions and loops, and write Bicep code that configures how loops are executed. You'll also be able to create variable loops and output loops to make your templates even more flexible.
+By the end of this module, you'll be able to create Bicep files by using conditions and loops, and write Bicep code that configures how loops are executed. You'll also be able to create variable loops and output loops to make your files even more flexible.
 
 ## Prerequisites
 

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/1-introduction.md

@@ -1,10 +1,10 @@
 Your toy company wants to launch a new teddy bear toy in multiple countries/regions. For compliance reasons, the infrastructure must be spread across all the Azure regions where the toy will be launched.
 
-You needed to deploy the same resources in multiple locations and a variety of environments. You wanted to create flexible Bicep files that you can reuse, and to control resource deployments by changing the deployment parameters.
+You needed to deploy the same resources in multiple locations and a variety of environments. You wanted to create flexible Bicep files that you can reuse and to control resource deployments by changing the deployment parameters.
 
-To deploy some resources only to certain environments, you added conditions to your template. You then used copy loops to deploy resources into various Azure regions. You used variable loops to define the properties of the resources to be deployed. Finally, you used output loops to retrieve the properties of those deployed resources.
+To deploy some resources only to certain environments, you added conditions to your Bicep file. You then used copy loops to deploy resources into various Azure regions. You used variable loops to define the properties of the resources to be deployed. Finally, you used output loops to retrieve the properties of those deployed resources.
 
-Without the conditions and copy loops features, you'd have to maintain and use multiple versions of Bicep files. You'd have to apply every change in your environment in multiple templates. Maintaining all these templates would entail a great deal of effort and overhead. By using conditions and loops, you were able to create a single template that works for all your regions and environments and ensure that all your resources are configured identically.
+Without the conditions and copy loops features, you'd have to maintain and use multiple versions of Bicep files. You'd have to apply every change in your environment to multiple files. Maintaining all these files would entail a great deal of effort and overhead. By using conditions and loops, you were able to create a single file that works for all your regions and environments, ensuring that all your resources are configured identically.
 
 ## Learn more
 

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/10-summary.md

@@ -1,6 +1,6 @@
 You can use conditions in your Bicep code to deploy resources only when specific constraints are in place.
 
-For example, at your toy company, you need to deploy resources to various environments. When you deploy them to a production environment, you need to ensure that auditing is enabled for your Azure SQL logical servers. But when you deploy resources to development environments, you don't want to enable auditing. You want to use a single template to deploy resources to all your environments.
+For example, at your toy company, you need to deploy resources to various environments. When you deploy them to a production environment, you need to ensure that auditing is enabled for your Azure SQL logical servers. But when you deploy resources to development environments, you don't want to enable auditing. You want to use a single Bicep file to deploy resources to all your environments.
 
 In this unit, you'll learn how to deploy resources conditionally.
 
@@ -22,7 +22,7 @@ In Bicep, conditions can also include expressions. In the following example, the
 
 ::: code language="bicep" source="code/2-conditional-expression.bicep" highlight="7" :::
 
-It's usually a good idea to create a variable for the expression that you're using as a condition. That way, your template is easier to understand and read. Here's an example:
+It's usually a good idea to create a variable for the expression that you're using as a condition. That way, your Bicep file is easier to understand and read. Here's an example:
 
 ::: code language="bicep" source="code/2-conditional-expression-variable.bicep" range="1-5, 8-9, 20-24, 28-29" highlight="7, 9" :::
 

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/2-use-conditions-deploy-resources.md

@@ -68,15 +68,15 @@ After you've completed all of the preceding changes, your Bicep file should look
 
 ::: code language="bicep" source="code/3-template.bicep" :::
 
-If it doesn't, either copy the example or adjust your template to match the example.
+If it doesn't, either copy the example or adjust your Bicep file to match the example.
 
 ## Deploy the Bicep file to Azure
 
 ::: zone pivot="cli"
 
 [!INCLUDE [Bootstrapping instructions for first Bicep exercise - CLI](../../includes/azure-template-bicep-exercise-sandbox-deploy-cli.md)]
 
-### Deploy the template to Azure by using the Azure CLI
+### Deploy the Bicep file to Azure by using the Azure CLI
 
 In the Visual Studio Code terminal, deploy the Bicep file to Azure by running the following code. Notice that you're explicitly setting the `location` parameter to `westus3`.
 
@@ -90,9 +90,9 @@ az deployment group create --name main --template-file main.bicep --parameters l
 
 [!INCLUDE [Bootstrapping instructions for first Bicep exercise - PowerShell](../../includes/azure-template-bicep-exercise-sandbox-deploy-powershell.md)]
 
-### Deploy the template to Azure by using Azure PowerShell
+### Deploy the Bicep file to Azure by using Azure PowerShell
 
-In the Visual Studio Code terminal, deploy the template to Azure by running the following Azure PowerShell command. This process can take a couple of minutes to complete, and then you'll have a successful deployment.
+In the Visual Studio Code terminal, deploy the Bicep file to Azure by running the following Azure PowerShell command. This process can take a couple of minutes to complete, and then you'll have a successful deployment.
 
 ```azurepowershell
 New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep -location westus3
@@ -154,7 +154,7 @@ In the previous deployment, the default value for the `environmentName` paramete
 
 Now you'll explicitly set the parameter value to `Production`. You expect that, by making this change, the storage account for auditing purposes will be deployed, and auditing will be enabled on the logical server.
 
-### Deploy the template for the production environment
+### Deploy the Bicep file for the production environment
 
 ::: zone pivot="cli"
 
@@ -168,7 +168,7 @@ az deployment group create --name main --template-file main.bicep --parameters e
 
 ::: zone pivot="powershell"
 
-In the Visual Studio Code terminal, deploy the template to Azure by running the following Azure PowerShell command:
+In the Visual Studio Code terminal, deploy the Bicep file to Azure by running the following Azure PowerShell command:
 
 ```azurepowershell
 New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep -environmentName Production -location westus3

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/3-exercise-conditions.md

@@ -44,7 +44,7 @@ Your *database.bicep* file should look like this example:
 
 ::: code language="bicep" source="code/3-template.bicep" :::
 
-If it doesn't, either copy the example or adjust your template to match the example.
+If it doesn't, either copy the example or adjust your Bicep file to match the example.
 
 ## Deploy the Bicep file to Azure
 
@@ -87,9 +87,9 @@ After the deployment is finished, you want to verify that the new logical server
 
 1. Leave the page open in your browser. You'll check on deployments again later.
 
-## Update and redeploy the template to Azure with an additional location for a logical server
+## Update and redeploy the Bicep file to Azure with an additional location for a logical server
 
-The teddy bear toy team is about to launch again, this time into Asia. The team is asking you to deploy a new server and database in the East Asia region. To do so, you need to update your Bicep parameter and redeploy your template.
+The teddy bear toy team is about to launch again, this time into Asia. The team is asking you to deploy a new server and database in the East Asia region. To do so, you need to update your Bicep parameter and redeploy your Bicep file.
 
 ::: zone pivot="cli"
 

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/5-exercise-loops.md

@@ -1,4 +1,4 @@
-By using the powerful copy loops feature, you can create dynamic and flexible templates. It's important to understand how to control the way that loops execute when they create resources and how to use loops to set resource properties and nest loops.
+By using the powerful copy loops feature, you can create dynamic and flexible Bicep files. It's important to understand how to control the way that loops execute when they create resources and how to use loops to set resource properties and nest loops.
 
 In this unit, you'll learn how to control the execution of copy loops and how to use resource property loops and nested loops in Bicep.
 
@@ -24,7 +24,7 @@ Now let's apply the `@batchSize` decorator with a value of `2`:
 
 ::: code language="bicep" source="code/6-loop-batchSize.bicep" range="2-6" highlight="1" :::
 
-When you deploy the template, Bicep will deploy in batches of two:
+When you deploy the file, Bicep will deploy in batches of two:
 
 :::image type="content" source="../media/6-batch-size-2.png" alt-text="Diagram showing time on the horizontal axis, with app1 and app2 stacked to run as one batch, and app3 to run as a second batch." border="false":::
 
@@ -35,7 +35,7 @@ You can also tell Bicep to run the loop sequentially by setting the `@batchSize`
 
 ::: code language="bicep" source="code/6-loop-batchSize.bicep" range="1, 3-6" highlight="1" :::
 
-When you deploy the template, Bicep waits for each resource deployment to finish before it starts the next one:
+When you deploy the file, Bicep waits for each resource deployment to finish before it starts the next one:
 
 :::image type="content" source="../media/6-batch-size-1.png" alt-text="Diagram showing time on the horizontal axis, with app1, app2, and app3 being deployed sequentially." border="false":::
 
@@ -63,7 +63,7 @@ You can use a nested loop to deploy the subnets within each virtual network:
 
 The nested loop uses the `range()` function to create two subnets.
 
-When you deploy the template, you get the following virtual networks and subnets:
+When you deploy the Bicep file, you get the following virtual networks and subnets:
 
 | Virtual network name | Location | Address prefix | Subnets |
 | --- | --- | --- | --- |

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/6-use-loops-advanced.md

@@ -32,7 +32,7 @@ As you do with other loops, use the `for` keyword to specify an output loop:
 
 ::: code language="bicep" source="code/7-loop-output-simple.bicep" highlight="9" :::
 
-You'll ordinarily use output loops in conjunction with other loops within your template. For example, let's look at a Bicep file that deploys a set of storage accounts to Azure regions that are specified by the `locations` parameter:
+You'll ordinarily use output loops in conjunction with other loops within your Bicep file. For example, let's look at a Bicep file that deploys a set of storage accounts to Azure regions that are specified by the `locations` parameter:
 
 ::: code language="bicep" source="code/7-loop-output-complex.bicep" range="1-14" :::
 

learn-pr/azure/build-flexible-bicep-templates-conditions-loops/includes/7-use-loops-with-variables-and-outputs.md

@@ -71,7 +71,7 @@ Your *database.bicep* file should look like this example:
 
 ::: code language="bicep" source="code/8-database.bicep" highlight="68-70" :::
 
-If they don't, either copy the examples or adjust your templates to match the examples.
+If they don't, either copy the examples or adjust your Bicep files to match the examples.
 
 ## Deploy the Bicep file to Azure