Update articles/virtual-machines/linux/tutorial-azure-devops-blue-green-deployment-strategy.md

Co-Authored-By: Julia Kulla-Mader <[email protected]>

Author: raiyanalam

articles/virtual-machines/linux/tutorial-azure-devops-blue-green-deployment-strategy.md

@@ -52,7 +52,7 @@ Here is the step-by-step walkthrough.
 ![AzDevOps_bluegreen_pipeline](media/tutorial-devops-azure-pipelines-classic/azure-devops-blue-green-pipeline.png)
 
 
-9. Click on  **Edit** release pipeline in Azure DevOps to see the pipeline configuration. The pipeline consists of three phases - first phase is a DG phase and deploys to VMs that are tagged as _green_ (standby VMs). The second phase pauses the pipeline and waits for manual intervention to resume the run. Once a user is satisfied that deployment is stable, he can now redirect the traffic to _green_ VMs and resume the pipeline run which will then swap _blue_ and _green_ tags in the VMs. This makes sure that the VMs that have older application version are tagged as _green_ and are deployed to in the next pipeline run.
+9. Click on  **Edit** release pipeline in Azure DevOps to see the pipeline configuration. The pipeline consists of three phases. The first phase is a deployment group phase and deploys to VMs that are tagged as _green_ (standby VMs). The second phase pauses the pipeline and waits for manual intervention to resume the run. Once a user is satisfied that deployment is stable, they can now redirect the traffic to _green_ VMs and resume the pipeline run which will then swap _blue_ and _green_ tags in the VMs. This makes sure that the VMs that have older application version are tagged as _green_ and are deployed to in the next pipeline run.
 ![AzDevOps_bluegreen_task](media/tutorial-devops-azure-pipelines-classic/azure-devops-blue-green-tasks.png)