Update elastic-san-expand.md

Updated policy removing variables and adding numbers

Author: adarshv98

articles/storage/elastic-san/elastic-san-expand.md

@@ -42,9 +42,9 @@ az elastic-san update -e $sanName -g $resourceGroupName --base-size-tib $newBase
 
 As a preview feature, you can choose to automatically scale up your SAN by specific increments until a specified maximum size. The capacity increments have a minimum of 1 TiB, and you can only set up an autoscale policy for additional capacity units. So when autoscaling, your performance won't automatically scale up as your storage does. A sample autoscale policy would look like this:  
 
-If spare capacity (unused capacity) is less than X TiB of space, increase capacity by Y TiB, up to a maximum of Z TiB.
+If spare capacity (unused capacity) is less than 20 TiB of space, increase capacity by 5 TiB, up to a maximum of 150 TiB.
 
-Here, X is the amount of storage capacity you require to be unused. Y is the increment by which you're increasing the capacity of the SAN, with a minimum increment requirement of 1 TiB. Z is the maximum capacity up to which you want the SAN to scale up via autoscale. For example, if you have a SAN of 100 TiB and you want to scale up your storage in 5 TiB increments, you can set up a policy that says whenever the unused capacity is less than or equal to 20 TiB of space, increase capacity by 5 TiB up to a maximum of 150 TiB. The policy triggers when you have less than X TiB of unused space on your SAN. Space is consumed at the SAN level via provisioning volumes and taking snapshots. Therefore, if your usage exceeds the required value of unused space at the SAN level, the policy triggers and the SAN size increases by Y TiB.
+Here, 20 TiB is the amount of storage capacity you require to be unused. 5 TiB is the increment by which you're increasing the capacity of the SAN, with a minimum increment requirement of 1 TiB. 150 TiB is the maximum capacity up to which you want the SAN to scale up via autoscale. If your SAN is 100 TiB, the policy will trigger when you have less than 20 TiB of unused space on your SAN, which means when you have used 80 TiB or more. Space is consumed at the SAN level via provisioning volumes and taking snapshots. Therefore, if your usage exceeds the required value of unused space at the SAN level, the policy triggers and the SAN size increases by 5 TiB as defined.
 
 A SAN can't automatically scale down. To reduce the size of your SAN, follow the manual process in the previous section. If you have configured an autoscaling policy and the amount in TiB by which you are scaling down the SAN is greater than the value of the unused capacity field set in the policy, the request fails and you'll have to edit or disable your policy to complete this action. For example, if you have a SAN of size 6 TiB and a policy that states that the unused capacity should be 2 TiB, you can't reduce the total size of the SAN by 4 TiB because it would leave less than 2 TiB of unused capacity.