edits

Author: v-albemi

learn-pr/azure/child-extension-bicep-templates/8-knowledge-check.yml

@@ -44,7 +44,7 @@ quiz:
       explanation: Incorrect. You can define child resources by using a nested resource definition, but you can't define extension resources in this way.
   - content: Which of these statements is true?
     choices:
-    - content: Using the `existing` keyword on a resource declaration means that Bicep redeploys the resource.
+    - content: When you use the `existing` keyword on a resource declaration, Bicep redeploys the resource.
       isCorrect: false
       explanation: Incorrect. The `existing` keyword means that Bicep doesn't attempt to deploy the resource. Use the keyword to refer to the resource within your Bicep template.
     - content: All resource definitions in a Bicep file need to have an SKU property set, even existing resources.

learn-pr/azure/child-extension-bicep-templates/includes/4-exercise-define-child-resources.md

@@ -30,7 +30,7 @@ First, you create a new Bicep template that contains an Azure Cosmos DB account.
    > [!TIP]
    > Bicep is strict about where you put line breaks, so be sure to add line breaks only where shown here.
 
-   This Bicep template deploys an Azure Cosmos DB account that is the parent resource you build upon in the next section.
+   This Bicep template deploys an Azure Cosmos DB account that's the parent resource you build upon in the next section.
 
 1. Save the changes to the file.
 
@@ -83,7 +83,7 @@ After you complete the preceding steps, your _main.bicep_ file should look like
 
 :::code language="bicep" source="code/4-complete.bicep" :::
 
-If it doesn't, either copy the example or adjust your template to match the example.
+If it doesn't look the same, either copy the example or adjust your template to match the example.
 
 ## Deploy the template to Azure
 
@@ -93,7 +93,7 @@ If it doesn't, either copy the example or adjust your template to match the exam
 
 ### Deploy the template to Azure
 
-Run the following code from the terminal in Visual Studio Code to deploy the Bicep template to Azure. This operation can take a minute or two to complete, before you see a successful deployment.
+Run the following code from the terminal in Visual Studio Code to deploy the Bicep template to Azure. It might take a minute or two before you see a successful deployment.
 
 ```azurecli
 az deployment group create --name main --template-file main.bicep
@@ -107,7 +107,7 @@ az deployment group create --name main --template-file main.bicep
 
 ### Deploy the template to Azure
 
-Deploy the template to Azure by using the following Azure PowerShell command in the terminal. This operation can take a minute or two to complete, before you see a successful deployment.
+Deploy the template to Azure by using the following Azure PowerShell command in the terminal. It might take a minute or two before you see a successful deployment.
 
 ```azurepowershell
 New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep
@@ -120,7 +120,7 @@ New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep
 1. Go to the [Azure portal](https://portal.azure.com?azure-portal=true) and make sure you're in the sandbox subscription:
 
    1. Select your avatar in the upper-right corner of the page, and then select **Switch directory**. 
-   1. A list of directories appears. Select the **Switch** button next to Microsoft Learn Sandbox.
+   1. A list of directories appears. Select the **Switch** button next to **Microsoft Learn Sandbox**.
 
 1. On the home page, select **Resource groups**. The **Resource groups** pane appears.
 
@@ -138,4 +138,4 @@ New-AzResourceGroupDeployment -Name main -TemplateFile main.bicep
 
     :::image type="content" source="../media/4-deployment-details.png" alt-text="Screenshot of the Azure portal interface for the specific deployment, with three Cosmos DB resources listed." border="true":::
 
-1. Leave the page open in your browser, so you can check on deployments again later.
+1. Leave the page open in your browser so you can check on deployments again later.

learn-pr/azure/child-extension-bicep-templates/includes/5-define-extension-resources.md

@@ -36,7 +36,7 @@ Notice that the example uses the `scope` property with the Azure Cosmos DB accou
 
 ## Extension resource IDs
 
-An ID for an extension resource is slightly different than IDs for other resources. It consists of its parent resource ID, the separator `/providers/`, and the extension resource ID.
+An ID for an extension resource is slightly different from IDs for other resources. It consists of its parent resource ID, the separator `/providers/`, and the extension resource ID.
 
 Say you deployed the previously mentioned Azure Cosmos DB account, and the account was named `toyrnd`. Here's what the lock's resource ID would look like:
 

learn-pr/azure/child-extension-bicep-templates/includes/6-work-with-existing-resources.md

@@ -76,7 +76,7 @@ Resources often need to refer to the properties of other resources. For example,
 > [!TIP]
 > It's a best practice to look up keys from other resources in this way instead of passing them around through outputs. You'll always get the most up-to-date data. Also, it's important to note that outputs aren't designed to handle secure data like keys.
 
-The way that you access the information about a resource depends on the type of information you're getting. If it's a property that isn't secure, you ordinarily use only the `properties` of the resource. The following example template deploys an Azure Functions application and uses the access details (*instrumentation key*) for an existing Application Insights instance:
+The way that you access the information about a resource depends on the type of information you're getting. If it's a property that isn't considered sensitive, you ordinarily use only the `properties` of the resource. The following example template deploys an Azure Functions application and uses the access details (*instrumentation key*) for an existing Application Insights instance:
 
 :::code language="bicep" source="code/6-existing-properties.bicep" highlight="1-3,15":::
 

learn-pr/azure/includes/azure-template-exercise-sandbox-sign-in-powershell.md

@@ -12,9 +12,9 @@ ms.author: jgao
     Connect-AzAccount
     ```
 
-   A browser opens so that you can sign in to your Azure account. The browser might be opened in the background.  
+   A browser opens so that you can sign in to your Azure account. The browser might open in the background.  
 
-1. After you've signed in to Azure, the terminal displays a list of the subscriptions associated with this account. If you've activated the sandbox, a subscription named *Concierge Subscription* is displayed. Select it for the rest of the exercise.
+1. After you sign in to Azure, the terminal displays a list of the subscriptions associated with this account. If you activated the sandbox, a subscription named *Concierge Subscription* is displayed. Select it for the rest of the exercise.
 
     If you've used more than one sandbox recently, the terminal might display more than one instance of *Concierge Subscription*. In this case, use the next two steps to set one as the default subscription.