Apply suggestions from code review

Updated based on Roy's suggestions

Co-authored-by: rogara <[email protected]>

Author: adarshv98

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

@@ -54,9 +54,9 @@ Use one of these sets of sample code to create an Elastic SAN that uses locally
 | `<Location>`                     | The region where the new resources will be created. |
 | `<Zone>`                         | The availability zone where the Elastic SAN will be created.<br> *Specify the same availability zone as the zone that will host your workload.*<br>*Use only if the Elastic SAN will use locally redundant storage.*<br> *Must be a zone supported in the target location such as `1`, `2`, or `3`.*  |
 | `<AutoScalePolicyEnforcement>`   | The setting that determines whether or not autoscaling is enabled for the Elastic SAN. <br>*This value is optional but if passed in, must be 'Enabled' or 'Disabled'* |
-| `<UnusedSizeTiB>`                | The capacity (in TiB) on your Elastic SAN that you want to keep free and unused. If you use more space than this amount, the scale-up operation is automatically triggered, increasing the size of your SAN. This parameter is optional, but it is required to enable autoscaling. |
-|`<IncreaseCapacityUnitByTiB>`     | This parameter sets the TiB of additional capacity units that your SAN scales up by when autoscale gets triggered. This parameter is optional but required to enable autoscaling. |
-|`<CapacityUnitScaleUpLimit>`      | This parameter sets the maximum capacity (size) that your SAN can grow to using autoscaling. Your SAN won't automatically scale past this size. |
+| `<UnusedSizeTiB>`                | The capacity (in TiB) on your Elastic SAN that you want to keep free and unused. If you use more space than this amount, the scale-up operation is automatically triggered, increasing the size of your SAN. This parameter is optional but is required to enable autoscaling. |
+|`<IncreaseCapacityUnitByTiB>`     | This parameter sets the TiB of additional capacity units that your SAN scales up by when autoscale gets triggered. This parameter is optional but is required to enable autoscaling. |
+|`<CapacityUnitScaleUpLimit>`      | This parameter sets the maximum capacity (size) that your SAN can grow to using autoscaling. Your SAN won't automatically scale past this size. This parameter is optional but is required to enable autoscaling. |
 
 The following command creates an Elastic SAN that uses locally redundant storage without autoscaling enabled.
 
@@ -125,9 +125,9 @@ Use one of these sets of sample code to create an Elastic SAN that uses locally
 | `<Location>`                     | The region where the new resources will be created. |
 | `<Zone>`                         | The availability zone where the Elastic SAN will be created.<br> *Specify the same availability zone as the zone that will host your workload.*<br>*Use only if the Elastic SAN uses locally redundant storage.*<br> *Must be a zone supported in the target location such as `1`, `2`, or `3`.*  |
 | `<AutoScalePolicyEnforcement>`   | The setting that determines whether or not autoscaling is enabled for the Elastic SAN. <br>*This value is optional but if passed in, must be 'Enabled' or 'Disabled'* |
-| `<UnusedSizeTiB>`                | The capacity (in TiB) on your Elastic SAN that you want to keep free and unused. If you use more space than this amount, the scale-up operation is automatically triggered, increasing the size of your SAN. This parameter is optional, but it is required to enable autoscaling. |
-|`<IncreaseCapacityUnitByTiB>`     | This parameter sets the TiB of additional capacity units that your SAN scales up by when autoscale gets triggered. This parameter is optional but required to enable autoscaling. |
-|`<CapacityUnitScaleUpLimit>`      | This parameter sets the maximum capacity (size) that your SAN can grow to using autoscaling. Your SAN won't automatically scale past this size. |
+| `<UnusedSizeTiB>`                | The capacity (in TiB) on your Elastic SAN that you want to keep free and unused. If you use more space than this amount, the scale-up operation is automatically triggered, increasing the size of your SAN. This parameter is optional but is required to enable autoscaling. |
+|`<IncreaseCapacityUnitByTiB>`     | This parameter sets the TiB of additional capacity units that your SAN scales up by when autoscale gets triggered. This parameter is optional but is required to enable autoscaling. |
+|`<CapacityUnitScaleUpLimit>`      | This parameter sets the maximum capacity (size) that your SAN can grow to using autoscaling. Your SAN won't automatically scale past this size. This parameter is optional but is required to enable autoscaling. |
 
 
 The following command creates an Elastic SAN that uses locally redundant storage without autoscaling enabled.

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

@@ -40,18 +40,19 @@ az elastic-san update -e $sanName -g $resourceGroupName --base-size-tib $newBase
 
 ## Autoscale (preview)
 
-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:  
+As a preview feature, you can 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. Here's an example of setting an autoscale policy using Azure CLI:  
 
-If spare capacity (unused capacity) is less than 20 TiB of space, increase capacity by 5 TiB, up to a maximum of 150 TiB.
+`az elastic-san update -n mySanName -g myVolGroupName --auto-scale-policy-enforcement "Enabled" --unused-size-tib 20 --increase-capacity-unit-by-tib 5 --capacity-unit-scale-up-limit-tib 150`
 
-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.
+Running that example command would set the following policy on the SAN it's run on: If your SAN's unused capacity (free space) is less than 20 TiB, increase the SAN's additional capacity by 5 TiB, until its unused capacity is at least 20 TiB. Don't allow the SAN's total capacity to exceed 150 TiB.
 
-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.
+You can't use an autoscale policy to scale down. To reduce the size of your SAN, follow the manual process in the previous section. If you have configured an autoscaling policy, disable it before reducing the size of your SAN.
 
 
 
+The following script can be run to enable an autoscale policy for an existing Elastic SAN.
+
 # [PowerShell](#tab/azure-powershell-autoscale)
-Here is a script you can run to enable autoscale for a SAN that has already been created.
 ```azurepowershell
 # Define some variables.
 autoscalePolicyEnforcement = "Enabled" # Whether autoscale is enabled or disabled at the SAN level
@@ -63,7 +64,6 @@ Update-AzElasticSan -ResourceGroupName myresourcegroup -Name myelasticsan -AutoS
 ```
 
 # [Azure CLI](#tab/azure-cli-autoscale)
-Here is a script you can run to enable autoscale for a SAN that has already been created.
 ```azurecli
 # Define some variables.
 autoscalePolicyEnforcement = "Enabled" # Whether autoscale is enabled or disabled at the SAN level

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

@@ -40,7 +40,11 @@ Using the same example of a 100 TiB SAN that has 500,000 IOPS and 20,000 MB/s. S
 
 ### Autoscaling (preview)
 
-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. For example, if you have a SAN of 100 TiB and you want your storage to scale up in 5 TiB increments, you can set a policy so that whenever the unused capacity is less than or equal to 20 TiB of space, the additional capacity units on your SAN increase by 5 TiB, up to a maximum of 150 TiB. This is useful for environments using snapshots, because you can ensure that you have extra space for your snapshots, and guard against your snapshots failing due to having run out of space on your SAN. The last parameter allows you to set a size limit for your SAN, beyond which the capacity will not expand via autoscale. You can modify your autoscaling policy at any point. 
+As a preview feature, you can automatically scale up your SAN by specific increments until a specified maximum size using an autoscale policy. An autoscale policy is helpful for environments where storage consumption continually increases, like environments using volume snapshots. Volume snapshots consume some of the total capacity of an elastic SAN, and having an autoscale policy helps ensure your SAN doesn't run out of space to store volume snapshots.
+
+When setting an autoscale policy, there's a minimum capacity increment of 1 TiB, and you can only automatically scale additional capacity, rather than base capacity. So when autoscaling, the IOPS and throughput of your SAN won't automatically scale up.
+
+Here's an example of how an autoscale policy works. Say you have an elastic SAN that has 100 TiB total storage capacity. This SAN has volume snapshots configured, so you want the capacity to automatically scale to accommodate your snapshots. You can set a policy so that whenever the unused capacity is less than or equal to 20 TiB, additional capacity on your SAN increases by 5 TiB, up to a maximum of 150 TiB total storage. So, if you use 80 TiB of space, 5 more TiB is automatically provisioned, so your SAN now has a total storage capacity of 105 TiB.
 
 ## Networking