Skip to content

Commit 7bcd469

Browse files
committed
aviate-usage-ai-tutorial.adoc: Address typos from PR review
1 parent 2a62478 commit 7bcd469

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

html5/_main_toc.html.slim

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -366,7 +366,7 @@ nav.sidebar-nav
366366
a.nav-link href="/latest/aviate-wallet.html"
367367
| Wallet
368368
li.bd-sidenav-active
369-
a.nav-link href="/latest/aviate-usage-tutorial.html"
369+
a.nav-link href="/latest/aviate-usage-ai-tutorial.html"
370370
| Usage Tutorial (AI use case)
371371
li
372372
.icon-title

userguide/aviate/aviate-usage-tutorial.adoc renamed to userguide/aviate/aviate-usage-ai-tutorial.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this example, we simulate an AI use cases where input tokens are recorded as
1919
You will need:
2020

2121
* A running Kill Bill with the Aviate plugin installed.
22-
* A valid API access tokens for all Aviate APIs calls - referred to is `ID_TOKEN`
22+
* A valid API access tokens for all Aviate APIs calls - referred to as `ID_TOKEN`
2323

2424
== Setup: Configuring a Tenant
2525

@@ -41,7 +41,7 @@ curl -v -X POST -u admin:password \
4141

4242
=== Step 2: Create a billing meter
4343

44-
A BillingMeter defines how usage points are filtered and aggregated. Before creating a Plan with usage, a valid billing meter must exist. This is a new abstraction in Aviate that extends the default capabilities from Kill Bill open-source.
44+
A BillingMeter defines how usage points are filtered and aggregated. Before creating a Plan with usage, a valid billing meter must exist. This is an Aviate specific abstraction that extends the default capabilities from Kill Bill open-source.
4545

4646
For reference, this uses the https://docs.killbill.io/latest/aviate-metering[aviate metering capabilities].
4747

@@ -92,7 +92,7 @@ The Plan includes a usage section linked to the billing meter. The usage section
9292
For reference, this uses the https://docs.killbill.io/latest/aviate-catalog-plugin[aviate catalog capabilities].
9393

9494

95-
The full paylaod and API call can be seens below:
95+
The full payload and API call can be seen below:
9696

9797
Use aviate API: https://killbill.github.io/slate/aviate-catalog.html#create-plan-product-pricelist
9898

userguide/tutorials/consumable_in_arrear.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ The calls to record usage are made per subscription, but they can include multip
121121

122122
In our example, the online store could directly make the call to Kill Bill using that API to record each video as they are consumed.
123123

124-
Note that in scenarios where the consumption is much higher (for e.g in the case of a telecom company offering cell-phone minutes), one would need to use a *metering system* that would first *aggregate* the units on a daily granularity before making the call to Kill Bill. You can check the initial implementation of our https://github.com/killbill/killbill-meter-plugin[metring module] that provides that aggregation functionality.
124+
Note that in scenarios where the consumption is much higher (for e.g in the case of a telecom company offering cell-phone minutes), one would need to use a *metering system* that would first *aggregate* the units on a daily granularity before making the call to Kill Bill. You can check the initial implementation of our https://docs.killbill.io/latest/aviate-metering[metring module] that provides that aggregation functionality.
125125

126126

127127
=== Example of a Customer Usage

0 commit comments

Comments
 (0)