docs: Fix PR comments

Author: patrikbraborec

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

@@ -12,11 +12,11 @@ sidebar_position: 3
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-The pay-per-event pricing model offers a flexible monetization option for Actors on Apify Store. Unlike pay per result, PPE allows you to charge users based on specific events triggered programmatically by your Actor's code.
+The PPE pricing model offers a flexible monetization option for Actors on Apify Store. Unlike pay per result, PPE allows you to charge users based on specific events triggered programmatically by your Actor's code.
 
 PPE lets you define pricing for individual events. You can charge for specific events directly from your Actor using the [JS](/sdk/js/reference/class/Actor#charge)/[Python](/sdk/python/reference/class/Actor#charge) SDK, or by calling the [PPE charging API](/api/v2/post-charge-run) directly. Common events include Actor start, dataset item creation, and external API calls.
 
-The details on how your cost is computed can be found in [Example of a pay-per-event pricing model](#example-of-a-pay-per-event-pricing-model).
+The details on how your cost is computed can be found in [Example of a PPE pricing model](#example-of-a-ppe-pricing-model).
 
 ## How is profit computed
 
@@ -40,7 +40,7 @@ An Actor's negative net profit does not affect the positive profit of another Ac
 
 :::
 
-## How to set pricing for pay-per-event Actors
+## How to set pricing for PPE Actors
 
 1. _Understand your costs_: Analyze resource usage (e.g CPU, memory, proxies, external APIs) and identify cost drivers
 1. _Define clear events_: break your Actor's functionality into measurable, chargeable events.
@@ -51,7 +51,7 @@ An Actor's negative net profit does not affect the positive profit of another Ac
 1. _Test your pricing_: Run your Actor and analyze cost-effectiveness using a special dataset.
 1. _Communicate value_: Ensure pricing reflects the value provided and is competitive.
 
-## Best practices for pay-per-event Actors
+## Best practices for PPE Actors
 
 Use our SDKs (JS and, Python or use [`apify actor charge`](/cli/docs/next/reference#apify-actor-charge-eventname) when using our Apify CLI) to simplify PPE implementation into your Actor. This tool can handle pricing, usage tracking, idempotency keys, API errors, and, event charging via an API.
 
@@ -77,9 +77,9 @@ When using browser automation tools like Puppeteer or Playwright for web scrapin
 
 :::
 
-### Charge for "Actor start"
+### Charge for `Actor start`
 
-Charge for "Actor start" to prevent users from running your Actor for free.
+Charge for `Actor start` to prevent users from running your Actor for free.
 
 <Tabs groupId="main">
 <TabItem value="JavaScript" label="JavaScript">
@@ -317,7 +317,7 @@ Try to limit the number of events. Fewer events make it easier for users to unde
 
 For Actors that produce data, events should map to something concrete in the user's dataset or storage.
 
-However, we acknowledge that some events don't produce tangible results (such as running AI workflows or processing external API calls). This flexibility is what makes pay-per-event pricing powerful. It gives you the freedom to charge for special operations, complex workflows, and unique value propositions.
+However, we acknowledge that some events don't produce tangible results (such as running AI workflows or processing external API calls). This flexibility is what makes PPE pricing powerful. It gives you the freedom to charge for special operations, complex workflows, and unique value propositions.
 
 Examples:
 
@@ -330,9 +330,9 @@ Examples:
 
 If you're not using the Apify SDKs (JS/Python), you need to handle idempotency (ensuring the same operation produces the same result when called multiple times) manually to prevent charging the same event multiple times.
 
-## Example of a pay-per-event pricing model
+## Example of a PPE pricing model
 
-You make your Actor pay-per-event and set the following pricing:
+You make your Actor PPE and set the following pricing:
 
 - _`actor-start` event_: $0.10 per start
 - _`scraped-product` event_: $0.01 per product
@@ -356,9 +356,9 @@ Your profit is computed only from the first two users, since they are on Apify p
 - _Total underlying cost_: $3.20 + $1.50 = $4.70
 - _Your profit_: 80% of revenue minus costs = 0.8 × $25.20 - $4.70 = $15.46
 
-## PPE event names
+## Event names
 
-To implement pay-per-event pricing, you need to define specific events in your Actor code. You can retrieve the list of available pricing event names using the [Get Actor](https://apify.com/docs/api/v2/act-get) API endpoint.
+To implement PPE pricing, you need to define specific events in your Actor code. You can retrieve the list of available pricing event names using the [Get Actor](https://apify.com/docs/api/v2/act-get) API endpoint.
 
 ## Next steps
 

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

@@ -14,20 +14,14 @@ import TabItem from '@theme/TabItem';
 
 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.
 
-The details on how your cost is computed can be found in [Example of a pay-per-result pricing model](#example-of-a-pay-per-result-pricing-model).
+The details on how your cost is computed can be found in [Example of a PPR pricing model](#example-of-a-ppr-pricing-model).
 
 :::tip Additional benefits
 
-Actors that implement pay-per-result pricing receive additional benefits, including increased visibility in the Apify Store and enhanced discoverability for users looking for monetized solutions.
+Actors that implement PPR pricing receive additional benefits, including increased visibility in the Apify Store and enhanced discoverability for users looking for monetized solutions.
 
 :::
 
-## Pay-per-result (PPR) vs. pay-per-event (PPE)
-
-Unlike PPR, which charges based on the number of results produced, PPE lets you define pricing for individual events. You can charge for specific events directly from your Actor by calling the PPE charging API. Common events include Actor start, dataset item creation, and external API calls.
-
-If you're interested in learning more about PPE, check out the [Pay per event (PPE)](/platform/actors/publishing/monetize/pay-per-event) section.
-
 ## How is profit computed
 
 Your profit is calculated from the mentioned formula:
@@ -37,11 +31,11 @@ Your profit is calculated from the mentioned formula:
 where:
 
 - _Revenue_: The amount charged for results via the PPR pricing API or through JS/Python SDK. You receive 80% of this revenue.
-- _Platform costs_: The underlying platform usage costs for running the Actor, calculated in the same way as for PPE. For more details, visit the [Example of a pay-per-result pricing model](#example-of-a-pay-per-result-pricing-model) section.
+- _Platform costs_: The underlying platform usage costs for running the Actor, calculated in the same way as for PPE. For more details, visit the [Example of a PPR pricing model](#example-of-a-ppr-pricing-model) section.
 
 Only revenue and cost for Apify customers on paid plans are taken into consideration when computing your profit. Users on free plans are not reflected there.
 
-## Best practices for pay-per-result Actors
+## Best practices for PPR Actors
 
 To ensure profitability, check the following best practices.
 
@@ -69,7 +63,7 @@ When using browser automation tools like [Puppeteer](https://pptr.dev/) or [Play
 
 This check prevents your Actor from generating more results than the user has paid for, protecting both you and your users from unexpected costs.
 
-The `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable contains the user-set limit on returned results for pay-per-results Actors. Do not exceed this limit. You can see the example implementation in the following code snippets.
+The `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable contains the user-set limit on returned results for PPR Actors. Do not exceed this limit. You can see the example implementation in the following code snippets.
 
 <Tabs groupId="main">
 <TabItem value="JavaScript" label="JavaScript">
@@ -85,7 +79,7 @@ let isGettingItemCount = false;
 let pushedItemCount = 0;
 
 export const pushDataMaxAware = async (data: Parameters<Actor['pushData']>[0]): Promise<{ shouldStop: boolean }> => {
-    // If this isn't pay-per-result, just push like normallyå
+    // If this isn't PPR, just push like normally
     if (!MAX_ITEMS) {
         await Actor.pushData(data);
         return { shouldStop: false };
@@ -136,7 +130,7 @@ class PayPerResultManager:
         self.pushed_item_count = 0
 
     async def push_data_max_aware(self, data: Union[Dict[Any, Any], List[Dict[Any, Any]]]) -> Dict[str, bool]:
-        # If this isn't pay-per-result, just push like normally
+        # If this isn't PPR, just push like normally
         if not self.max_items:
             await Actor.push_data(data)
             return {'shouldStop': False}
@@ -205,9 +199,9 @@ Example scenarios:
 
 This ensures that every run generates at least one result, guaranteeing that users are charged appropriately for using your Actor.
 
-## Example of pay-per-result pricing model
+## Example of PPR pricing model
 
-You make your Actor pay-per-result and set the price to be _$1/1,000 results_. During the first month, three users use your Actor:
+You make your Actor PPR and set the price to be _$1/1,000 results_. During the first month, three users use your Actor:
 
 - _User 1 (paid plan)_: Gets 50,000 results, costing them $50
 - _User 2 (paid plan)_: Gets 20,000 results, costing them $20