Skip to content

Commit 3e132e9

Browse files
committed
implemented pr suggestions
1 parent d4ef2ef commit 3e132e9

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

sources/platform/actors/publishing/monetize/pay_per_result.mdx

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,23 +12,23 @@ sidebar_position: 2
1212
import Tabs from '@theme/Tabs';
1313
import TabItem from '@theme/TabItem';
1414

15-
:::warning Legacy pricing model
15+
:::warning Pay per result is deprecated
1616

17-
Pay per result is deprecated and will be superseded by Pay per event early in 2026. [Migrate to PPE in one click](#one-click-migration-to-ppe) (backward compatible)
17+
This pricing model is deprecated and will be removed in 2026. You can migrate to [pay per event with one click](#one-click-migration-to-ppe), and the migration is backward compatible.
1818

1919
:::
2020

2121
In this model, you set a price per 1,000 results. Users are charged based on the number of results your Actor produces and stores in the run's default dataset. Your profit is calculated as 80% of the revenue minus platform usage costs.
2222

23-
The details on how your cost is computed can be found in [Example of a PPR pricing model](#example-of-a-ppr-pricing-model).
23+
The details on how your cost is computed can be found in [Example of a PPR pricing model](#example-of-ppr-pricing).
2424

2525
## One click migration to PPE
2626

27-
Select your PPR Actor, go to the Publication tab, open the Monetization section, and click the `Migrate to Pay per event` button.
27+
Select your PPR Actor, go to the **Publication** tab, open the **Monetization** section, and click the **Migrate to Pay per event** button.
2828

2929
![Migration button](../images/ppr-to-ppe-migration-button.png)
3030

31-
### Why should I migrate?
31+
### Why should I migrate
3232

3333
The Pay per event pricing model offers superior flexibility in charging not only for the results but also for any event.
3434
This helps you to pass on the costs of external APIs or additional processing directly to your users, price different functionalities of your Actor differently, avoid revenue loss from small but usage-heavy runs, and more.
@@ -44,12 +44,10 @@ This change does not count towards the pricing change limits that you are allowe
4444

4545
**Code changes:** No changes to your Actor code are required if it already respects the `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable (the price limit set by users).
4646

47-
**After migration:** With Pay per event, you can define additional custom events beyond dataset items. [Learn more](./pay-per-event)
47+
**After migration:** With [pay per event](./pay-per-event), you can define additional custom events beyond dataset items.
4848

4949
**Respecting user spending limits:** You can continue using the `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable to respect user-specified price limits.
5050

51-
Bleu sky and flying high free as a bird
52-
5351
## How is profit computed
5452

5553
Your profit is calculated from the mentioned formula:
@@ -69,7 +67,7 @@ PPR charges based on the number of results produced. PPE lets you define pricing
6967

7068
:::info Learn more about PPE
7169

72-
If you want to learn more about PPE, refer to the [Pay per event](/platform/actors/publishing/monetize/pay-per-event) section.
70+
If you want to learn more about PPE, refer to the [pay per event](/platform/actors/publishing/monetize/pay-per-event) section.
7371

7472
:::
7573

0 commit comments

Comments
 (0)