Skip to content

Commit 7f1c639

Browse files
committed
update
1 parent 3b894f9 commit 7f1c639

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/ai-services/openai/how-to/provisioned-throughput-onboarding.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Quota and commitments work together to govern the creation of deployments within
6262
- Quota must be available for the desired model within the desired region and subscription. This means you can't exceed your subscription/region-wide limit for the model.
6363
- Committed PTUs must be available on the resource where you create the deployment. (The capacity you assign to the deployment is paid-for).
6464

65-
### Commitment Properties and Charging Model
65+
### Commitment properties and charging model
6666

6767
A commitment includes several properties.
6868

@@ -74,7 +74,7 @@ A commitment includes several properties.
7474
|Expiration Date| The expiration date of the commitment. This time of expiration is midnight UTC.| Initially, 30 days from creation. However, the expiration date changes if the commitment is renewed.|
7575
|Renewal Policy| There are three options for what to do upon expiration: <br><br> - Autorenew: A new commitment term begins for another 30 days at the current number of PTUs <br>- Autorenew with different settings: This setting is the same as *Autorenew*, except that the number of PTUs committed upon renewal can be decreased <br>- Don't autorenew: Upon expiration, the commitment ends and isn't renewed.| Initially set at commitment creation, and can be changed at any time.|
7676

77-
### Commitment Charges
77+
### Commitment charges
7878

7979
Provisioned Throughput Commitments generate charges against your Azure subscription at the following times:
8080

0 commit comments

Comments
 (0)