updates3

Author: LiSeda

learn-pr/azure/build-first-bicep-file/8-exercise-refactor-template-modules.yml renamed to learn-pr/azure/build-first-bicep-file/8-exercise-refactor-file-modules.yml

@@ -1,4 +1,4 @@
-[!INCLUDE [Sandbox explanation](../../includes/azure-file-exercise-sandbox-subscription.md)]
+[!INCLUDE [Sandbox explanation](../../includes/azure-template-exercise-sandbox-subscription.md)]
 
 For your toy-launch website, you decide to first create a proof of concept by creating a basic Bicep file. In this exercise, you'll create a storage account, Azure App Service plan, and app. Later, you'll modify the file to make it more reusable.
 
@@ -11,7 +11,7 @@ During the process, you'll:
 > - Add an App Service plan and app to the file.
 > - Provision the infrastructure again to see the new resources.
 
-[!INCLUDE [Install the Bicep extension for Visual Studio Code](../../includes/azure-file-bicep-exercise-vscode-extension.md)]
+[!INCLUDE [Install the Bicep extension for Visual Studio Code](../../includes/azure-template-bicep-exercise-vscode-extension.md)]
 
 ## Create a Bicep file that contains a storage account
 
@@ -25,7 +25,7 @@ During the process, you'll:
 
 1. Add the following Bicep code into the file. You'll deploy the file soon. It's a good idea to type the code yourself instead of copying and pasting so you can see how the tooling helps you to write your Bicep files.
 
-   :::code language="bicep" source="code/4-file.bicep" range="1-11":::
+   :::code language="bicep" source="code/4-template.bicep" range="1-11":::
 
    > [!TIP]
    > Bicep is strict about where you put line breaks, so make sure you don't put line breaks in different places than listed here.
@@ -43,7 +43,7 @@ During the process, you'll:
 
 ::: zone pivot="cli"
 
-[!INCLUDE [Bootstrapping instructions for first Bicep exercise - CLI](../../includes/azure-file-bicep-exercise-sandbox-deploy-cli.md)]
+[!INCLUDE [Bootstrapping instructions for first Bicep exercise - CLI](../../includes/azure-template-bicep-exercise-sandbox-deploy-cli.md)]
 
 ### Deploy the file to Azure
 
@@ -59,7 +59,7 @@ You'll see `Running...` in the terminal.
 
 ::: zone pivot="powershell"
 
-[!INCLUDE [Bootstrapping instructions for first Bicep exercise - PowerShell](../../includes/azure-file-bicep-exercise-sandbox-deploy-powershell.md)]
+[!INCLUDE [Bootstrapping instructions for first Bicep exercise - PowerShell](../../includes/azure-template-bicep-exercise-sandbox-deploy-powershell.md)]
 
 ### Deploy the file to Azure
 

learn-pr/azure/build-first-bicep-file/includes/4-exercise-define-resources-bicep-file.md

@@ -25,7 +25,7 @@ During the process, you'll:
 
    Also notice that you're using a variable for the Azure App Service plan name, but you're using parameters for the other names. Storage accounts and App Service apps need globally unique names, but App Service plan names need to be unique only within their resource group. This difference means it's not a concern to use the same App Service plan name across different deployments, as long as the deployments are all going into different resource groups.
 
-   [!INCLUDE [Sandbox location note](../../includes/azure-file-bicep-exercise-sandbox-location.md)]
+   [!INCLUDE [Sandbox location note](../../includes/azure-template-bicep-exercise-sandbox-location.md)]
 
 1. Find the places within the resource definitions where the `location` and `name` properties are set, and update them to use the parameter values. After you're finished, the resource definitions within your Bicep file should look like this:
 

learn-pr/azure/build-first-bicep-file/includes/6-exercise-add-parameters-variables-bicep-file.md

@@ -14,7 +14,7 @@ Bicep modules help you address these challenges by splitting your code into smal
 
 After you've created a module, you can reuse it in multiple Bicep files, even if the files are for different projects or workloads. For example, when you build out one solution, you might create separate modules for the app components, the database, and the network-related resources. Then, when you start to work on another project with similar network requirements, you can reuse the relevant module.
 
-:::image type="content" source="../../includes/media/bicep-templates-modules.png" alt-text="Diagram that shows a template referencing three modules: application, database, and networking. The networking module is then reused in another template." border="false":::
+:::image type="content" source="../../includes/media/bicep-files-modules.png" alt-text="Diagram that shows a template referencing three modules: application, database, and networking. The networking module is then reused in another template." border="false":::
 
 You can even share modules within your team, within your organization, or with the Azure community. You'll learn more about sharing Bicep modules in a future Microsoft Learn module.