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

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

Author: rohinchandra-li

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

@@ -127,7 +127,7 @@ 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`.*  |
 | `<BaseSizeTib>`                  | The amount of base units to provision. For Azure CLI extension elastic-san versions 1.3.0 and greater, this is an optional parameter with default value 20. |
-| `<ExtendedCapacitySizeTiB>`      | The amount of capacity-only units to provision. For Azure CLI extension elastic-san versions 1.3.0 and greater, this is an optional parameter with default value 0. |
+| `<ExtendedCapacitySizeTiB>`      | The amount of capacity-only units to provision. For Azure CLI extension elastic-san versions 1.3.0 and newer, this is an optional parameter with default value 0. |
 | `<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 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. |