Line edits2

Author: lootle1

learn-pr/azure-devops/manage-release-cadence/2-what-are-deployment-patterns.yml

@@ -25,7 +25,7 @@ quiz:
       explanation: "With A/B testing, you could randomly show both versions of the website to users. Then the marketing team can use statistical analysis to decide which version performs better."
     - content: "Feature toggles"
       isCorrect: false
-      explanation: "Feature toggles are better suited to exposing new features to a small, select number of users to see how they react."
+      explanation: "Feature toggles are better suited to exposing new features to a small and select number of users to see how they react."
   - content: "You have a new feature for your website, and you're ready to deploy it. However, this feature is risky because it changes the way your users interact with the site. Which deployment patterns might you use to release to a small group of early adopters who have signed up to see new features?"
     choices:
     - content: "Canary release or progressive-exposure deployment"

learn-pr/azure-devops/manage-release-cadence/includes/1-introduction.md

@@ -23,7 +23,7 @@ We also recommend that you start at the beginning of this learning path, [Deploy
 
 If you want to go through just this module, then you need to set up a development environment on your Windows, macOS, or Linux system. You'll need the following resources:
 
-- An [Azure DevOps organization](/azure/devops/pipelines/get-started/pipelines-sign-up) with access to [parallel jobs](/azure/devops/pipelines/licensing/concurrent-jobs). If your organization does not have access to parallel jobs, you can request parallel jobs for free for public or private projects using [this form](https://aka.ms/azpipelines-parallelism-request). Your request will take 2-3 business days.
+- An [Azure DevOps organization](/azure/devops/pipelines/get-started/pipelines-sign-up) with access to [parallel jobs](/azure/devops/pipelines/licensing/concurrent-jobs). If your organization doesn't have access to parallel jobs, you can request parallel jobs for free for public or private projects using [this form](https://aka.ms/azpipelines-parallelism-request). Your request will take 2-3 business days.
 - An [Azure subscription](https://azure.microsoft.com/free/?azure-portal=true)
 - A [GitHub](https://github.com/join?azure-portal=true) account
 - [Visual Studio Code](https://code.visualstudio.com?azure-portal=true)

learn-pr/azure-devops/manage-release-cadence/includes/3-set-up-environment.md

@@ -250,7 +250,7 @@ To add the variables:
 1. Under **Properties**, for the variable group name, enter *Release*.
 1. Under **Variables**, select **+ Add**.
 1. For the name of your variable, enter *WebAppNameDev*. As its value, enter the name of the App Service instance that corresponds to your *Dev* environment, such as *tailspin-space-game-web-dev-1234*.
-1. Repeat steps 5 and 6 twice more to create variables for your T*est and *Staging* environments, as shown in this table:
+1. Repeat steps 5 and 6 twice more to create variables for your *Test* and *Staging* environments, as shown in this table:
 
     | Variable name         | Example value                            |
     |-----------------------|------------------------------------------|