edits

Author: v-albemi

learn-pr/azure/child-extension-bicep-templates/includes/1-introduction.md

@@ -1,28 +1,28 @@
-Child and extension resources allow your Azure deployments to access the advanced functionality and power of the Azure platform. You can create these resource types in Bicep by using a clear and understandable template syntax. 
+Child and extension resources enable your Azure deployments to access the advanced functionality and power of the Azure platform. You can create these resource types in Bicep by using a clear and understandable template syntax. 
 
-You can also use Bicep to refer to resources that were created outside the Bicep file itself. For example, you can refer to resources that your colleagues created manually by using the Azure portal, or from within another Bicep template or module, even if they're in a different resource group or subscription. By using these features of Bicep, you can unlock the ability to create powerful templates that deploy all aspects of your Azure infrastructure.
+You can also use Bicep to refer to resources that were created outside of the Bicep file. For example, you can refer to resources that your colleagues created manually by using the Azure portal, or from within another Bicep template or module, even if the resources are in a different resource group or subscription. By using these features of Bicep, you can unlock the ability to create powerful templates that deploy all the components of your Azure infrastructure.
 
 ## Example scenario
 
 Suppose you're responsible for deploying and configuring Azure infrastructure at a toy company. Your company's R&D department contacts you because they're working on a new toy drone that sprays glitter over unsuspecting targets. R&D team members are starting to test the drone. They plan to collect telemetry about the distance the drone can fly, the amount of glitter it can spray, and the battery level.
 
 They want you to set up a new Azure Cosmos DB database for storing this valuable and highly sensitive product test data. They need you to log all database-access attempts so that they can feel confident that no competitors are accessing the data.
 
-The team created a storage account to store all their product design documents, and they want you to help audit all attempts to access them.
+The team created a storage account to store all their product design documents, and they want you to help audit all attempts to access the documents.
 
 :::image type="content" source="../media/1-architecture-diagram.png" alt-text="Architecture diagram showing how logs are sent from the new Azure Cosmos DB account and the storage account to the Log Analytics workspace." border="false":::
 
-## What will we be doing?
+## What will you be doing?
 
 In this module, you learn about Azure resource types, and how child and extension resources are used throughout Azure. You create a Bicep template that deploys a set of Azure resources, and you use several features of Bicep, including:
 
-- Child resource definitions, through nested resources, the `parent` property, and by constructing multipart resource names.
+- Child resource definitions, through nested resources and the `parent` property, and by constructing multipart resource names.
 - Extension resource definitions, by using the `scope` property.
 - Existing resource references, by using the `existing` keyword.
 
-## What is the main goal?
+## What's the main goal?
 
-By the end of this module, you're able to create Bicep templates that include child and extension resources. You're also able to create Bicep templates that refer to pre-existing Azure resources that were created outside the template file.
+By the end of this module, you'll be able to create Bicep templates that include child and extension resources. You'll also be able to create Bicep templates that refer to pre-existing Azure resources that were created of outside the template file.
 
 ## Prerequisites
 
@@ -31,10 +31,10 @@ You should be familiar with:
 - Creating and deploying basic Bicep templates.
 - Azure, including the Azure portal, subscriptions, resource groups, and resource definitions.
 
-To follow along with the exercises in the module, you need:
+To complete the exercises in the module, you need:
 
 - [Visual Studio Code](https://code.visualstudio.com), installed locally.
 - The [Bicep extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep), installed.
-- Either:
+- One of the following:
   - The latest [Azure CLI](/cli/azure/install-azure-cli) tools, installed locally.
   - The latest version of [Azure PowerShell](/powershell/azure/install-az-ps), installed locally.

learn-pr/azure/child-extension-bicep-templates/includes/2-understand-azure-resources.md

@@ -2,7 +2,7 @@ All Azure resources are deployed with a specific *type*. The type identifies the
 
 ## Resource providers
 
-Azure Resource Manager is designed so that many different *resource providers* can be managed through Resource Manager APIs and ARM templates. A resource provider is a logical grouping of resource types, which usually relate to one or a few Azure services. Examples of resource providers include:
+Azure Resource Manager is designed so that many different *resource providers* can be managed through Resource Manager APIs and Azure Resource Manager (ARM) templates. A resource provider is a logical grouping of resource types that usually relate to one or a few Azure services. Examples of resource providers include:
 
 - `Microsoft.Compute`, which is used for virtual machines.
 - `Microsoft.Network`, which is used for networking resources like virtual networks, network security groups, and route tables.
@@ -22,37 +22,37 @@ Resource providers have to be registered for your subscription before you can us
 
 A resource provider exposes multiple different types. Each resource type has its own set of properties and behaviors that define the resource and what it can do. For example, within the `Microsoft.Web` resource provider, there are several resource types, including:
 
-- `sites`: Defines an App Service application or Azure Functions application. Properties include the environment variables that your application uses, and the supported protocols (HTTP and HTTPS) to access the application. 
-- `serverFarms`: Defines an App Service plan, the infrastructure that runs your applications. Properties include the size and SKU of the servers, and the number of instances of your plan that you want to deploy.
+- `sites`. Defines an App Service application or Azure Functions application. Properties include the environment variables that your application uses, and the supported protocols (HTTP and HTTPS) to access the application. 
+- `serverFarms`. Defines an App Service plan, the infrastructure that runs your applications. Properties include the size and SKU of the servers, and the number of instances of your plan that you want to deploy.
 
-When you define resources in Bicep, you have to specify their resource type and the version of the resource provider's API that you want Bicep to use for the resource. This information helps the Bicep tooling and the Resource Manager understand which properties should be provided with the resource definition.
+When you define resources in Bicep, you have to specify their resource type and the version of the resource provider's API that you want Bicep to use for the resource. This information helps the Bicep tooling and the Resource Manager determine which properties should be provided with the resource definition.
 
 > [!TIP]
 > It's a good idea to use a recent API version for each resource. New features in Azure services are sometimes available only in newer API versions.
 
-You combine the resource provider and type name to make a fully qualified resource type name. The fully qualified type name consists of the resource provider name, a slash (`/`), and the resource type. For example, a storage account’s fully qualified type name is `Microsoft.Storage/storageAccounts`. In this instance, its resource provider name is `Microsoft.Storage`, and the resource type is `storageAccounts`.
+You combine the resource provider and type name to make a fully qualified resource type name. The fully qualified type name consists of the resource provider name, a slash (`/`), and the resource type. For example, a storage account's fully qualified type name is `Microsoft.Storage/storageAccounts`. In this instance, its resource provider name is `Microsoft.Storage` and the resource type is `storageAccounts`.
 
 ## Resource IDs
 
 Every Azure resource has a unique resource ID. This ID includes information that helps disambiguate the resource from any other resource of the same type, or even from different resources that might share the same name. A resource ID for a storage account looks like this:
 
 ```
-/subscriptions/A123b4567c-1234-1a2b-2b1a-1234abc12345/resourceGroups/ToyDevelopment/providers/Microsoft.Storage/storageAccounts/secrettoys
+/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/ToyDevelopment/providers/Microsoft.Storage/storageAccounts/secrettoys
 ```
 
-Let's look at a visual representation of the same information:
+Here's a visual representation of the same information:
 
 :::image type="content" source="../media/2-resource-id.png" alt-text="Resource ID for a storage account, split with key/value pair on a separate line." border="false":::
 
-You can see that a resource ID interleaves information about the resource type and the specific resource you deployed. Let's break this example resource ID into its components:
+You can see that a resource ID contains information about the resource type and the specific resource you deployed. Here's a breakdown of this example resource ID into its components:
 
-- `subscriptions/A123b4567c-1234-1a2b-2b1a-1234abc12345` indicates that this resource is within the Azure subscription with ID. `A123b4567c-1234-1a2b-2b1a-1234abc12345`.
-- `resourceGroups/ToyDevelopment` indicates that the resource is within the resource group named `ToyDevelopment`.
+- `subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e` indicates that the resource is in the Azure subscription that has ID `aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e`.
+- `resourceGroups/ToyDevelopment` indicates that the resource is in the resource group named `ToyDevelopment`.
 - `providers/Microsoft.Storage` indicates that the resource is using a type from the `Microsoft.Storage` resource provider.
 - `storageAccounts` is the resource type.
 - `secrettoys` is the name of the storage account.
 
 > [!TIP]
-> You can access the ID of any resource in Bicep by using the symbolic name and the `id` property. For example, if you define a storage account with the symbolic name `toyDesignDocumentsStorageAccount`, you can access its resource ID by using the expression `toyDesignDocumentsStorageAccount.id`.
+> You can access the ID of any resource in Bicep by using the symbolic name and the `id` property. For example, if you define a storage account that has the symbolic name `toyDesignDocumentsStorageAccount`, you can access its resource ID by using the expression `toyDesignDocumentsStorageAccount.id`.
 
-Now that you understand the basics of resource types and resource IDs, let's look at child resources.
+Now that you understand the basics of resource types and resource IDs, you'll look at child resources.

learn-pr/azure/child-extension-bicep-templates/index.yml

@@ -2,8 +2,8 @@
 uid: learn.azure.child-extension-bicep-templates
 metadata:
   moduleType: standard
-  title: Deploy child and extension resources by using Bicep
-  description: Learn how to deploy child and extension resources, and refer to existing resources, within your Bicep code.
+  title: Deploy Child and Extension Resources by Using Bicep
+  description: Learn how to deploy child and extension resources, and refer to existing resources, in Bicep code.
   ms.service: azure-resource-manager
   manager: jasongroce
   ms.date: 05/27/2025
@@ -13,7 +13,7 @@ metadata:
   ms.devlang: bicep
 title: Deploy child and extension resources by using Bicep
 summary: |
-  Deploy various Azure resources in your Bicep code. Define and use child and extension resources. Work with resources that you created outside a Bicep template or module.
+  Deploy various Azure resources in your Bicep code. Define and use child and extension resources. Work with resources that you created outside of a Bicep template or module.
 abstract: |
   After completing this module, you'll be able to:
     - Explain resource types and resource IDs
@@ -24,10 +24,10 @@ prerequisites: |
   - Creating and deploying basic Bicep templates.
   - Azure, including the Azure portal, subscriptions, resource groups, and resource definitions.
 
-  To follow along with the exercises in the module, you need:
+  To complete the exercises in the module, you need:
   - [Visual Studio Code](https://code.visualstudio.com), installed locally.
   - The [Bicep extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep), installed.
-  - Either:
+  - One of the following:
     - The latest [Azure CLI](/cli/azure/install-azure-cli) tools, installed locally.
     - The latest version of [Azure PowerShell](/powershell/azure/install-az-ps), installed locally.
 iconUrl: /training/achievements/bicep/child-extension-bicep-templates.svg