Skip to content

Commit 69f3574

Browse files
Apply suggestions from PR review
Co-authored-by: Shannon Leavitt <[email protected]>
1 parent 3d0008b commit 69f3574

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-scale-in-policy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,11 +25,11 @@ The scale-in policy feature provides users a way to configure the order in which
2525

2626
### Default scale-in policy
2727

28-
##Flexible Orchestration
29-
With this policy, virtual machines are scaled-in after balancing across availability zones (if the scale set is in zonal configuration) and the oldest virtual machine as per createdTime is scaled-in first.
28+
#### Flexible orchestration
29+
With this policy, virtual machines are scaled-in after balancing across availability zones (if the scale set is in zonal configuration), and the oldest virtual machine as per `createdTime` is scaled-in first.
3030
Note that balancing across fault domain is not available in Default policy with flexible orchestration mode.
3131

32-
##Uniform Orchestration
32+
#### Uniform orchestration
3333
By default, Virtual Machine Scale Set applies this policy to determine which instance(s) will be scaled in. With the *Default* policy, VMs are selected for scale-in in the following order:
3434

3535
1. Balance virtual machines across availability zones (if the scale set is deployed in zonal configuration)

0 commit comments

Comments
 (0)