Skip to content

Commit 89d4c26

Browse files
authored
Update reserved-capacity.md
1 parent 98f404c commit 89d4c26

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/cosmos-db/reserved-capacity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -124,17 +124,17 @@ Imagine this hypothetical scenario: A company is working on a new application bu
124124
* Total of 800 RU/s: eight units of the 100 RU/s option, with a 20% discount.
125125
* Scoped to the development resource group.
126126
* One year term, since the project lasts for nine months.
127-
* Paid upfront, since it's a small value.
127+
* They paid upfront, it's a small value.
128128
* On day 30 they purchased reserved capacity for their tests environment:
129129
* 750,000 RU/s: 7,500 units of the 100 RU/s option, with a 20% discount.
130130
* Scoped to the test subscription.
131131
* One year term.
132-
* Paid monthly.
132+
* They choose to pay monthly.
133133
* On day 180 they purchased reserved capacity for the production environment:
134134
* 3,500,000 RU/s: One unit of the 3,000,000 RU/s option, with a 43.2% discount. And 5,000 units of the 100 RU/s option, with a 20% discount.
135135
* Scoped to the production subscription.
136136
* Three-years term, to maximize the discounts.
137-
* Paid Monthly.
137+
* They choose to pay monthly too.
138138

139139
## Sample scenario 2
140140

@@ -233,7 +233,7 @@ The reservation discount is applied automatically to the Azure Cosmos DB resourc
233233
* [Azure reservations in the Partner Center CSP program](/partner-center/azure-reservations)
234234

235235
Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
236-
* If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](convert-vcore-to-request-unit.md)
236+
* If all you know is the number of vCores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](convert-vcore-to-request-unit.md)
237237
* If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](estimate-ru-with-capacity-planner.md)
238238

239239
## Need help? Contact us.

0 commit comments

Comments
 (0)