Skip to content

Commit 404fb57

Browse files
authored
Update virtual-machine-scale-sets-configure-rolling-upgrades.md
1 parent ec57740 commit 404fb57

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,7 @@ Stop-AzVmssRollingUpgrade `
245245

246246
## Restart a rolling upgrade
247247

248-
If you decide to cancel a rolling upgrade or the upgrade has stopped due to any policy breach, any more changes that result in another scale set model change trigger a new rolling upgrade. If you want to restart a rolling upgrade, to trigger a generic model update. This tells the scale set to check if all the instances are up to date with the latest model.
248+
If you decide to cancel a rolling upgrade or the upgrade has stopped due to any policy breach, any more changes that result in another scale set model change trigger a new rolling upgrade. If you want to restart a rolling upgrade, trigger a generic model update. This tells the scale set to check if all the instances are up to date with the latest model.
249249

250250
### [CLI](#tab/cli4)
251251
To restart a rolling upgrade after its been canceled, you need to trigger the scale set to check if the instances in the scale set are up to date with the latest scale set model. You can do this by running [az vmss update](/cli/azure/vmss#az-vmss-update).

0 commit comments

Comments
 (0)