Apply suggestions from code review

patrikbraborec · TC-MO · web-flow · commit ed58c593e05e · 2025-09-08T15:32:46.000+02:00
Co-authored-by: Michał Olender &lt;92638966+TC-MO@users.noreply.github.com&gt;
diff --git a/sources/platform/actors/publishing/monetize/index.mdx b/sources/platform/actors/publishing/monetize/index.mdx
@@ -18,10 +18,10 @@ Apify Store allows you to monetize your web scraping, automation and AI Agent pr
 
 Actors in Apify Store can be published under one of the following pricing models:
 
-1. **Free**: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor.
-2. **Rental**: Users pay for the platform usage costs. However, after a trial period, they need to pay a flat monthly fee to the developer to continue using the Actor.
-3. **Pay per result (PPR)**: Users don't pay for the platform usage costs. Instead, they pay the developer based on the number of results produced by the Actor.
-4. **Pay per event (PPE)**: Users don't pay for the platform usage cost the Actor generates. Instead, they pay based on specific events that are programmatically triggered from the Actor's source code. These events are defined by the developer and can include actions such as generating a single result or starting an Actor.
+1. _Free_: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor.
+2. _Rental_: Users pay for the platform usage costs. However, after a trial period, they need to pay a flat monthly fee to the developer to continue using the Actor.
+3. _Pay per result (PPR)_: Users don't pay for the platform usage costs. Instead, they pay the developer based on the number of results produced by the Actor.
+4. _Pay per event (PPE)_: Users don't pay for the platform usage cost the Actor generates. Instead, they pay based on specific events that are programmatically triggered from the Actor's source code. These events are defined by the developer and can include actions such as generating a single result or starting an Actor.
 
 For a detailed comparison of pricing models from the perspective of your users, refer to [Actors in Store](/platform/actors/running/actors-in-store) page.
 
@@ -107,7 +107,7 @@ All metrics can be exported as JSON for custom analysis and reporting.
 
 ## Promoting your Actor
 
-Create serach-engine-optimized descriptions and README files to improve search engine visibility. Share your Actor on multiple channels:
+Create search-engine-optimized descriptions and README files to improve search engine visibility. Share your Actor on multiple channels:
 
 - Post on Reddit, Quora, and social media platforms
 - Create tutorial videos demonstrating key features
diff --git a/sources/platform/actors/publishing/monetize/pay_per_event.mdx b/sources/platform/actors/publishing/monetize/pay_per_event.mdx
@@ -1,5 +1,5 @@
 ---
-title: Pay per event (PPE)
+title: Pay per event
 description: Learn how to monetize your Actor with pay-per-event (PPE) pricing, charging users for specific actions like Actor starts, dataset items, or API calls, and understand how to set profitable, transparent event-based pricing.
 slug: /actors/publishing/monetize/pay-per-event
 sidebar_position: 3
@@ -114,7 +114,7 @@ await Actor.exit();
 </TabItem>
 <TabItem value="Python" label="Python">
 
-```python
+```py
 from apify import Actor
 
 async def charge_for_actor_start():
@@ -139,7 +139,7 @@ async def main():
 
 :::note Actor migrations and charging
 
-Actors can migrate between servers during execution, which restarts the process and clears memory. When using PPE charging, avoid charging the start event multiple times after a migration by checking your charging state.
+Actors can migrate between servers during execution, which restarts the process and clears memory. When using PPE pricing model, avoid charging the start event multiple times after a migration by checking your charging state.
 
 :::
 
@@ -196,7 +196,7 @@ await Actor.exit();
 </TabItem>
 <TabItem value="Python" label="Python">
 
-```python
+```py
 from apify import Actor
 import requests
 
@@ -237,7 +237,7 @@ async def main():
 
 ### Respect user spending limits
 
-Finish the Actor run once charging reaches user-configured Maximum cost per run. Apify SDKs (JS and Python) return ChargeResult that helps determine when to finish.
+Finish the Actor run once charging reaches user-configured Maximum cost per run. Apify SDKs (JS and Python) return `ChargeResult` that helps determine when to finish.
 
 The `eventChargeLimitReached` property checks if the current event type can be charged more. If you have multiple event types, analyze the `chargeableWithinLimit` property to see if other events can still be charged before stopping the Actor.
 
@@ -277,7 +277,7 @@ await Actor.exit();
 </TabItem>
 <TabItem value="Python" label="Python">
 
-```python
+```py
 from apify import Actor
 
 async def charge_for_api_product_detail():
diff --git a/sources/platform/actors/publishing/monetize/pay_per_result.mdx b/sources/platform/actors/publishing/monetize/pay_per_result.mdx
@@ -1,5 +1,5 @@
 ---
-title: Pay per result (PPR)
+title: Pay per result
 description: Learn how to monetize your Actor with pay-per-result (PPR) pricing, charging users based on the number of results produced and stored in the dataset, and understand how to set profitable, transparent result-based pricing.
 slug: /actors/publishing/monetize/pay-per-result
 sidebar_position: 2
@@ -122,7 +122,7 @@ export const pushDataMaxAware = async (data: Parameters<Actor['pushData']>[0]):
 </TabItem>
 <TabItem value="Python" label="Python">
 
-```python
+```py
 import os
 import asyncio
 from apify import Actor
@@ -205,9 +205,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 a pay-per-result pricing model
+## Example of pay-per-result 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 pay-per-result 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
diff --git a/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx b/sources/platform/actors/publishing/monetize/pricing_and_costs.mdx
@@ -21,7 +21,7 @@ Platform usage by _FREE_ tier users is covered by Apify and does not contribute
 
 :::
 
-To calculate your costs in dollars for a specific run by paying user, multiply the unit cost of each service by the quantity consumed. For example, if a _BRONZE_ tier user run uses 10 compute units (CUs) at $0.4/CU, your cost would be $4.
+To calculate your costs for a specific run by paying user, multiply the unit cost of each service by the quantity consumed. For example, if a _BRONZE_ tier user run uses 10 compute units (CUs) at $0.4/CU, your cost would be $4.
 
 As highlighted in the [How to attract larger customers of PPE and PPR Actors](#how-to-attract-larger-customers-of-ppe-and-ppr-actors) section, if your Actor uses tiered pricing, the user's discount tier determines the unit costs applied to their runs. Your costs are lower for higher tiers, enabling you to offer more competitive pricing to these customers, while sustaining healthy profit margins.
 
diff --git a/sources/platform/actors/publishing/monetize/rental.mdx b/sources/platform/actors/publishing/monetize/rental.mdx
@@ -49,7 +49,7 @@ Based on the reasons mentioned in [Disadvantages of the rental pricing model](#d
 
 ## Example of a rental pricing model
 
-You make your Actor rental with **7-day free trial** and then **$30/month**. During the first calendar month, three users start to use your Actor:
+You make your Actor rental with _7-day free trial_ and then _$30/month_. During the first calendar month, three users start to use your Actor:
 
 - _User 1 (paid plan)_: Starts free trial on the 15th
 - _User 2 (paid plan)_: Starts free trial on the 25th  
