Merge pull request #179733 from j-martens/patch-20

typo

Author: PRMerger8

articles/devtest-labs/integrate-environments-devops-pipeline.md

@@ -40,7 +40,7 @@ To create the release definition, follow these steps:
    |Field|Description|
    |-----|-----------|
    |**Azure RM Subscription**|This is the Azure Resource Manager subscription to configure before running. Select a connection in the **Available Azure Service Connections** list, or create a more restricted permissions connection to your Azure subscription. For more information, see [Azure Resource Manager service endpoint](/azure/devops/pipelines/library/service-endpoints).|
-   |**Lab Name**|Select the name of a lab you created earlier (see prerequisites). In practice, you should select the lab against which you want to deploy. The resource will be create in this lab.  You can also use variables, `$(labName)`.  Manually entering the friendly name will cause failures, use the drop-down lists to select the information.|
+   |**Lab Name**|Select the name of a lab you created earlier (see prerequisites). In practice, you should select the lab against which you want to deploy. The resource is created in this lab.  You can also use variables, `$(labName)`.  Manually entering the friendly name will cause failures, use the drop-down lists to select the information.|
    |**Environment name**|Name of the environment to be created within the selected lab.|
    |**Repository Name**|Name of the source code repository containing the template. You can choose the default repository, `Public Environment Repo`, or another repo containing the template you want to use. Repositories are designed in the lab policies.  Manually entering the friendly name will cause failures, use the drop-down lists to select the information.|
    |**Template Name**|Name of the template to use to create the environment. Select the name of the environment template. Manually entering the friendly name will cause failures, use the drop-down lists to select the information.|