Skip to content

Commit 10c1a10

Browse files
committed
continuous-integration-deployment
1 parent 9eddba9 commit 10c1a10

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/data-factory/continuous-integration-deployment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Following is a sample overview of the continuous integration and delivery lifecy
5555

5656
![Build your own template](media/continuous-integration-deployment/custom-deployment-build-your-own-template.png)
5757

58-
1. Select **Load file** and then select the generated Resource Manager template.
58+
1. Select **Load file**, and then select the generated Resource Manager template.
5959

6060
![Edit template](media/continuous-integration-deployment/custom-deployment-edit-template.png)
6161

@@ -177,9 +177,9 @@ There are two ways to handle secrets:
177177

178178
### Update active triggers
179179

180-
Deployment can fail if you try to update active triggers. To update active triggers, you need to manually stop them and then restart them after the deployment. You can do this by using an Azure Powershell task:
180+
Deployment can fail if you try to update active triggers. To update active triggers, you need to manually stop them and then restart them after the deployment. You can do this by using an Azure PowerShell task:
181181

182-
1. On the **Tasks** tab of the release, add an **Azure Powershell** task.
182+
1. On the **Tasks** tab of the release, add an **Azure PowerShell** task.
183183

184184
1. Select **Azure Resource Manager** as the connection type, and select your subscription.
185185

0 commit comments

Comments
 (0)