Skip to content

Commit 7d21256

Browse files
committed
Correct formatting.
1 parent a91b75a commit 7d21256

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-arc/data/reserved-capacity-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,15 @@ For more information about how enterprise customers and pay-as-you-go customers
2929

3030
The size of reservation should be based on the total amount of compute resources measured in vCores used by the existing or soon-to-be-deployed managed instances within a specific region reservation scope.
3131

32-
For example, you run one general purpose, 16 vCore managed instance. Further, you plan to deploy within the next month an additional general purpose 16 vCore managed instance and one business critical 32 - vCore. Also, let's suppose that you know that you will need these resources for at least 1 year. In this case, you should purchase a 32 (2x16) vCores 1-year reservation for general purpose managed instance and 48 ( 2x8 + 32 ) vCore 1 year reservation for business critical.
32+
The following list demonstrates a scenario to project how you would reserve resources:
3333

3434
* **Current**: 1 general purpose, 16 vCore managed instance
3535

3636
* **In the next year you will add**:
3737
- 1 additional general purpose, 16 vCore managed instance
3838
- 1 additional business critical, 32 vCore managed instance
3939

40-
* **Purchase a reservations for:
40+
* **Purchase a reservations for**:
4141
- 32 (2x16) vCore 1-year reservation for general purpose managed instance
4242
- 48 (2x8 + 32) vCore 1 year reservation for business critical managed instance
4343

0 commit comments

Comments
 (0)