Skip to content

Commit 98a4521

Browse files
committed
final minor changes
1 parent bf8c18d commit 98a4521

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cost-management-billing/reservations/reservation-exchange-policy-changes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You can continue to exchange VM sizes (with instance size flexibility). However,
2020

2121
The current cancellation policy for reserved instances isn't changing. The total canceled commitment can't exceed 50,000 USD in a 12-month rolling window for a billing profile or single enrollment.
2222

23-
A compute reservation exchange for another compute reservation exchange is not the same process as a reservation [trade-in](../savings-plan/reservation-trade-in.md) for a savings plan. You can always trade-in your Azure reserved instances for compute for a savings plan. There's no time limit for trade-ins.
23+
A compute reservation exchange for another compute reservation exchange is similar to, but not the same as a reservation [trade-in](../savings-plan/reservation-trade-in.md) for a savings plan. The difference is that you can always trade-in your Azure reserved instances for compute for a savings plan. There's no time limit for trade-ins.
2424

2525
You can continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration and need or want more savings.
2626

0 commit comments

Comments
 (0)