Commitment Flexibility Appendix

specification/appendix/commitment_discounts/size_flexibility.md → specification/appendix/commitment_discounts/commitment_flexibility.md

@@ -1,8 +1,10 @@
-# Size-Flexibility
+# Commitment Flexibility
 
-A usage-based commitment discount obligates a customer to a usage amount for one or more related SKUs in return for reduced rates.  For example, a usage-based commitment discount is purchased to cover a specific database SKU, this commitment will cover every hour over the term where at least one instance of this SKU is running. It can also cover eligible resources wholly, where 1 hour is covered by 1 resource, or partially, where 1 committed hour can be split across multiple resources or 1 resource can be fully covered with unused commitment discount costs. These latter two examples are commonly known as *size-flexibility*.
+A usage-based commitment discount obligates a customer to a usage amount for one or more related SKUs in return for reduced rates.  For example, a usage-based commitment discount is purchased to cover a specific database SKU, this commitment will cover every hour over the term where at least one instance of this SKU is running. It can also cover eligible resources wholly, where 1 hour is covered by 1 resource, or partially, where 1 committed hour can be split across multiple resources or 1 resource can be fully covered with unused commitment discount costs. These latter two examples are commonly known as *commitment flexibility*.
 
-Since providers have different rules for when size-flexibility is or is not enabled, the following, fictitious SKU pricing attributes will be used in each example below, and each example will be categorized under size-flexibility enabled or disabled sections.
+When mixing usage-based commitment discounts with and without commitment flexibility with `CommitmentDiscountQuantity` measured by time, it is important to differentiate the `CommitmentDiscountUnit` for each type of commitment discount. In each scenario below, commitment discounts *without* commitment flexibility applied use "Hour" as a `CommitmentDiscountUnit`, and conversely commitment discounts *with* commitment flexibility use "Normalized Hour" as a `CommitmentDiscountUnit`.
+
+Since providers have different rules for when commitment flexibility is or is not enabled, the following, fictitious SKU pricing attributes will be used in each example below, and each example will be categorized under commitment flexibility enabled or disabled sections.
 
 ## SKUs & Rates
 
@@ -13,9 +15,9 @@ Since providers have different rules for when size-flexibility is or is not enab
 | TinyCloud    | Compute | VM_Large  | $2.00          | $1.00                | 4                     |
 | TinyCloud    | Compute | VM_XLarge | $4.00          | $2.00                | 8                     |
 
-The above, fictitious SKU pricing attributes show that this provider, *TinyCloud*, only has 1 service that offers 4 virtual machine SKUs with various list rates, committed rates, and normalization factors. Each SKU's normalization factor classifies its relative size to its committed rate. Usage-based commitment discounts with size-flexibility can fully cover any combination of 1 or more SKUs where the sum of their normalization factor equals the normalization factor of the commitment discount.
+The above, fictitious SKU pricing attributes show that this provider, *TinyCloud*, only has 1 service that offers 4 virtual machine SKUs with various list rates, committed rates, and normalization factors. Each SKU's normalization factor classifies its relative size to its committed rate. Usage-based commitment discounts with commitment flexibility can fully cover any combination of 1 or more SKUs where the sum of their normalization factor equals the normalization factor of the commitment discount.
 
-### Scenarios *without* size-flexibility
+### Scenarios *without* commitment flexibility
 
 #### Scenario #1: 100% utilization with matching resources
 
@@ -97,14 +99,14 @@ The VM_Large commitment discount is unused because no VM_Large resources are run
 ]
 ```
 
-### Scenarios *with* size-flexibility
+### Scenarios *with* commitment flexibility
 
 #### Scenario #1: 100% utilization with 2 VM_medium resources
 
 Purchase: 1 commitment discount purchased for 1 year (2023) for 1 VM_XLarge with a normalization factor of 8.
 Usage: 2 VM_Medium resources run from 2023-01-01T00:00:00 to 2023-01-01T01:00:00 with a normalization factor of 4 for each resource.
 
-1 commitment discount for a VM_XLarge has a normalization factor of 8, and 2 VM_Medium resources have a normalization factor of 4, each. Therefore, with size-flexibility, 1 VM_XLarge commitment discount can fully cover 2 VM_Medium resources resulting in a $2 amortized cost.
+1 commitment discount for a VM_XLarge has a normalization factor of 8, and 2 VM_Medium resources have a normalization factor of 4, each. With commitment flexibility, 1 VM_XLarge commitment discount can fully cover 2 VM_Medium resources resulting in a $2 amortized cost.
 
 ```json
 [