Update integrate-environments-devops-pipeline.md

Author: j-martens

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

@@ -16,7 +16,7 @@ You would ordinarily perform each of these tasks individually in your own custom
 ## Prerequisites
 Before you can integrate your CI/CD pipeline with Azure DevTest Labs, you must: 
 1. Install [Azure DevTest Labs Tasks](https://marketplace.visualstudio.com/items?itemName=ms-azuredevtestlabs.tasks) extension from Visual Studio Marketplace. 
-1. [Create a lab](devtest-lab-create-lab.md) and ensure configured to use **Public Environment**.
+1. [Create a lab](devtest-lab-create-lab.md) and ensure it is configured to use **Public Environment**, which is turned on by default.
 
 ## Create a release definition & environment
 To create the release definition, follow these steps:
@@ -44,7 +44,7 @@ To create the release definition, follow these steps:
    |**Repository Name**|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**|Select the name of the environment template from your source code repository. Manually entering the friendly name will cause failures, use the drop-down lists to select the information.| 
    |**Environment Name**|Enter a name to uniquely identify the environment instance within the lab.  It must be unique within the lab.|
-   |**Parameters File** & **Parameter overrides**|Use to pass custom parameters to the environment. Either or both can be used to set the parameter values. For example, you can use these fields to pass the encrypted password.|
+   |**Parameters File** & **Parameter overrides**|Use to pass custom parameters to the environment. Either or both can be used to set the parameter values. For example, you can use these fields to pass the encrypted password. You can also use variables to avoid passing secret information in the logs and even hook it up to Azure Key Vault.|
 
 ## Delete the environment
 The final stage is to delete the Environment that you deployed in your Azure DevTest Labs instance. You would ordinarily delete the environment after you execute the dev tasks or run the tests that you need on the deployed resources.