Corrected some formatting issues

Instructions/Labs/AZ400_M10_Controlling_Deployments_using_Release_Gates.md

@@ -276,7 +276,7 @@ In this task, you will make a minor change in the application code, commit the u
     > **Note**: This indicates that there are active work items. These work items need to be closed in order to proceed further. Next sampling time will be after 5 minutes.
 
 1.  Open a new browser tab, navigate to the Azure DevOps portal, in the vertical navigational pane, select **Boards** and, in the **Boards** section, select **Queries**.
-1.  On the **Queries** pane of the **Boards** view, click the **All* tab.
+1.  On the **Queries** pane of the **Boards** view, click the **All** tab.
 1.  On the **All** tab of the **Queries** pane, in the **Shared Queries** section, click the **Bugs** entry, on the **Queries > Shared Queries > Bugs** pane, and click **Run query**. 
 1.  Verify that the query returns a work item titled **Disk out of space in Canary Environment** in the **New** state.
 

Instructions/Labs/AZ400_M10_Creating_a_Release_Dashboard.md

@@ -61,7 +61,7 @@ In this task, you will create an Azure DevOps Starter resource in your Azure sub
 1.  On your lab computer, start a web browser, navigate to the [**Azure Portal**](https://portal.azure.com) and sign in with the user account that has the Owner or Contributor role in the Azure subscription you will be using in this lab.
 1.  In the Azure portal, search for and select the **DevOps Starter** resource type and, on the **DevOps Starter** blade, click **+ Add**. 
 1.  On the **DevOps Starter** blade, on the **Start fresh with a new application** pane, select the **.NET** tile and click **Next**. 
-1.  On the **DevOps Starter** blade, on the **Choose an application framework** pane, select the **ASP.NET Core** tile, move the **Add a database** slider to the **On** position, and click **Next**. 
+1.  On the **DevOps Starter** blade, on the **Choose an application framework** pane, select the **ASP<nolink>.NET Core** tile, move the **Add a database** slider to the **On** position, and click **Next**. 
 1.  On the **DevOps Starter** blade, on the **Select an Azure service to deploy the application** pane, ensure that the **Windows Web App** tile is selected and click **Next**. 
 1.  On the **DevOps Starter** blade, on the **Almost there** pane, specify the following settings:
 
@@ -134,7 +134,7 @@ In this task, you will create a dashboard and add to it release-related widgets.
     | Setting | Value |
     | ------- | ----- |
     | Build pipeline | **az400m10l02 - CI** |
-    | Linked release pipelines | **az400m10l02 - CD; **az400m10l02 - CD\dev** |
+    | Linked release pipelines | **az400m10l02 - CD; az400m10l02 - CD\dev** |
 
 1.  Back on the dashboard pane, hover over the upper right corner of the rectangle representing the **Release Health Overview** widget to reveal the ellipsis sign representing the **More actions** menu, click it, and, in the dropdown menu, click **Configure**.  
 1.  On the **Configuration** pane, specify the following settings (leave all others with their default values) and click **Save**.

Instructions/Labs/AZ400_M11_Configuring_Pipelines_as_Code_with_YAML.md

@@ -140,22 +140,22 @@ In this task, you will add a YAML build definition to the existing project.
 
 1.  On the **Where is your code?** pane, click **Azure Repos Git (YAML)** option.
 1.  On the **Select a repository** pane, click **PartsUnlimited**.
-1.  On the **Configure your pipeline** pane, click **ASP<nolink>.NET** to use this template as the starting point for your pipeline. This will open the **Review your pipeline YAML** pane.
+2.  On the **Configure your pipeline** pane, click **ASP<nolink>.NET** to use this template as the starting point for your pipeline. This will open the **Review your pipeline YAML** pane.
 
     > **Note**: The pipeline definition will be saved as a file named **azure-pipelines.yml** in the root of the repository. The file will contain the steps required to build and test a typical ASP<nolink>.NET solution. You can also customize the build as needed. In this scenario, you will update the **pool** to enforce the use of a VM running Visual Studio 2017.
 
-1.  Make sure  `trigger` is **master**.
+3.  Make sure  `trigger` is **master**.
 
     > **Note**: Review in Repos if your repository has **master** or **main** branch, organizations could choose default branch name for new repos: [Change the default branch](https://docs.microsoft.com/en-us/azure/devops/repos/git/change-default-branch?view=azure-devops#choosing-a-name). 
 
-1.  On the **Review your pipeline YAML** pane, in line **10**, replace `vmImage: 'windows-latest'` with `vmImage: 'vs2017-win2016'`.
-1.  On the **Review your pipeline YAML** pane, click **Save and run**.
-1.  On the **Save and run** pane, accept the default settings and click **Save and run**.
-1.  On the pipeline run pane, in the **Jobs** section, click **Job** and monitor its progress and verify that it completes successfully. 
+4.  On the **Review your pipeline YAML** pane, in line **10**, replace `vmImage: 'windows-latest'` with `vmImage: 'vs2017-win2016'`.
+5.  On the **Review your pipeline YAML** pane, click **Save and run**.
+6.  On the **Save and run** pane, accept the default settings and click **Save and run**.
+7.  On the pipeline run pane, in the **Jobs** section, click **Job** and monitor its progress and verify that it completes successfully. 
 
     > **Note**: Each task from the YAML file is available for review, including any warnings and errors.
 
-1.  Return to the pipeline run pane, switch from the **Summary** tab to the **Tests** tab, and review test statistics.
+8.  Return to the pipeline run pane, switch from the **Summary** tab to the **Tests** tab, and review test statistics.
 
 #### Task 3: Add continuous delivery to the YAML definition
 

Instructions/Labs/AZ400_M14_Automating_infrastructure_deployments_in_the_Cloud_with_Terraform.md

@@ -66,7 +66,7 @@ In this task, you will use Azure DevOps Demo Generator to generate a new project
 
 1.  Click **Sign in** and sign in using the Microsoft account associated with your Azure DevOps subscription.
 1.  If required, on the **Azure DevOps Demo Generator** page, click **Accept** to accept the permission requests for accessing your Azure DevOps subscription.
-1.  On the **Create New Project** page, in the **New Project Name** textbox, type *Automating infrastructure deployments with Terraform**, in the **Select organization** dropdown list, select your Azure DevOps organization, and then click **Choose template**.
+1.  On the **Create New Project** page, in the **New Project Name** textbox, type **Automating infrastructure deployments with Terraform**, in the **Select organization** dropdown list, select your Azure DevOps organization, and then click **Choose template**.
 1.  In the list of templates, in the toolbar, click **DevOps Labs**, select the **Terraform** template and click **Select Template**.
 1.  Back on the **Create New Project** page, if prompted to install a missing extension, select the checkbox below the **Replace Tokens** and **Terraform** labels and click **Create Project**.
 
@@ -101,7 +101,7 @@ In this task, you will build your application and publish the required files as
 1.  In the Azure DevOps portal, in the vertical menu bar at the left of the Azure DevOps portal, click **Pipelines**. Underneath, select **Pipelines**.
 1.  On the **Pipelines** pane, click **Terraform-CI** to select it and, on the **Terraform-CI** pane, click **Edit**.
 
-    > **Note**: This CI pipeline has tasks to compile the .Net Core project. The DotNet tasks in the pipeline will restore dependencies, build, test and publish the build output into a zip file (package), which can be deployed to a web application. In addition to the application build, we need to publish terraform files to build artifacts to make them available in CD pipeline. This is the reason for the **Copy files** task to copy Terraform file to Artifacts directory.
+    > **Note**: This CI pipeline has tasks to compile the .NET Core project. The DotNet tasks in the pipeline will restore dependencies, build, test and publish the build output into a zip file (package), which can be deployed to a web application. In addition to the application build, we need to publish terraform files to build artifacts to make them available in CD pipeline. This is the reason for the **Copy files** task to copy Terraform file to Artifacts directory.
 
 1.  Once you review the **Tasks** tab of the **Terraform-CI** pane, click the ellipsis symbol in the top right corner and, in the dropdown menu, click **Queue**.
 1.  On the **Run pipeline** pane, click **Run** to initiate the build. 
@@ -123,7 +123,7 @@ In this task, you will create Azure resources using Terraform as part of your de
 1.  In the list of tasks of the **Dev** stage, select the **Azure PowerShell** task. 
 1.  On the **Azure PowerShell** pane, in the **Azure Connection Type** dropdown list, select **Azure Resource Manager** and then, in the **Azure Subscription** dropdown list, select the newly created Azure service connection (the one under "Available Azure Service Connection").
 
-    > **Note**: To configure the Terraform [backend](https://www.terraform.io/docs/backends/), we need the access key to the Azure Storage account hosting the Terraform state. In this case, we are using Azure PowerShell task to retrieve the access key of the Azure Storage account provisioned in the previous task. By using `Write-Host "##vso[task.setvariable variable=storagekey]$key"`we are creating a pipeline variable that we will be able to use on later tasks.
+    > **Note**: To configure the Terraform [backend](https://www.terraform.io/docs/backends/), we need the access key to the Azure Storage account hosting the Terraform state. In this case, we are using Azure PowerShell task to retrieve the access key of the Azure Storage account provisioned in the previous task. By using `Write-Host "##vso[task.setvariable variable=storagekey]$key"` we are creating a pipeline variable that we will be able to use on later tasks.
 
 1.  In the list of tasks of the **Dev** stage, select the **Replace tokens in Terraform file** task.
 
@@ -178,7 +178,7 @@ In this exercise, you will remove the Azure resources provisioned in this lab to
 
 #### Task 1: Remove the Azure lab resources
 
-In this task, you will use Azure Cloud Shell to remove the Azure resources provisione in this lab to eliminate unnecessary charges. 
+In this task, you will use Azure Cloud Shell to remove the Azure resources provisioned in this lab to eliminate unnecessary charges. 
 
 1.  In the Azure portal, open the **Bash** shell session within the **Cloud Shell** pane.
 1.  List all resource groups created throughout the labs of this module by running the following command: