docs: Fix another PR comments

Author: patrikbraborec

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

@@ -334,10 +334,10 @@ If you're not using the Apify SDKs (JS/Python), you need to handle idempotency (
 
 You make your Actor pay-per-event and set the following pricing:
 
-- _"actor-start" event_: $0.10 per start
-- _"scraped-product" event_: $0.01 per product
-- _"scraped-product-detail" event_: $0.05 per detail
-- _"ai-analysis" event_: $0.15 per analysis
+- _`actor-start` event_: $0.10 per start
+- _`scraped-product` event_: $0.01 per product
+- _`scraped-product-detail` event_: $0.05 per detail
+- _`ai-analysis` event_: $0.15 per analysis
 
 During the first month, three users use your Actor:
 

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

@@ -61,15 +61,15 @@ Set memory limits using `minMemoryMbytes` and `maxMemoryMbytes` in your [`actor.
 
 :::note Memory requirements for browser-based scraping
 
-When using browser automation tools like Puppeteer or Playwright for web scraping, increase the memory limits to accommodate the browser's memory usage.
+When using browser automation tools like [Puppeteer](https://pptr.dev/) or [Playwright](https://playwright.dev/) for web scraping, increase the memory limits to accommodate the browser's memory usage.
 
 :::
 
 ### Implement the `ACTOR_MAX_PAID_DATASET_ITEMS` check
 
 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 paid-per-result 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 pay-per-results 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">

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

@@ -27,20 +27,20 @@ As highlighted in the [How to attract larger customers of PPE and PPR Actors](#h
 
 The following table summarizes the platform unit costs used for your cost computation  across different discount tiers.
 
-| Service                         | Price is per | _FREE_  | _BRONZE_ | _SILVER_ | _GOLD_  |
-|:-------------------------------|:--------------|--------:|---------:|---------:|--------:|
-| Compute unit                   | CU            | $0.4    | $0.4     | $0.3     | $0.25   |
-| Residential proxies            | GB            | $8      | $8       | $7.5     | $7      |
-| SERPs proxy                    | 1,000 SERPs   | $2.5    | $2.5     | $2       | $1.7    |
-| Data transfer - external       | GB            | $0.2    | $0.2     | $0.19    | $0.18   |
-| Data transfer - internal       | GB            | $0.05   | $0.05    | $0.045   | $0.04   |
-| Dataset - reads               | 1,000 reads   | $0.0004 | $0.0004  | $0.00036 | $0.00032|
-| Dataset - writes              | 1,000 writes  | $0.005  | $0.005   | $0.0045  | $0.004  |
-| Key-value store - reads       | 1,000 reads   | $0.005  | $0.005   | $0.0045  | $0.004  |
-| Key-value store - writes      | 1,000 writes  | $0.05   | $0.05    | $0.045   | $0.04   |
-| Key-value store - lists       | 1,000 lists   | $0.05   | $0.05    | $0.045   | $0.04   |
-| Request queue - reads         | 1,000 reads   | $0.004  | $0.004   | $0.0036  | $0.0032 |
-| Request queue - writes        | 1,000 writes  | $0.02   | $0.02    | $0.018   | $0.016  |
+| Service (unit)                        | _FREE_  | _BRONZE_ | _SILVER_ | _GOLD_  |
+|:--------------------------------------|--------:|---------:|---------:|--------:|
+| Compute unit (per CU)                 | $0.4    | $0.4     | $0.3     | $0.25   |
+| Residential proxies (per GB)          | $8      | $8       | $7.5     | $7      |
+| SERPs proxy (per 1,000 SERPs)         | $2.5    | $2.5     | $2       | $1.7    |
+| Data transfer - external (per GB)     | $0.2    | $0.2     | $0.19    | $0.18   |
+| Data transfer - internal (per GB)     | $0.05   | $0.05    | $0.045   | $0.04   |
+| Dataset - reads (per 1,000 reads)     | $0.0004 | $0.0004  | $0.00036 | $0.00032|
+| Dataset - writes (per 1,000 writes)   | $0.005  | $0.005   | $0.0045  | $0.004  |
+| Key-value store - reads (per 1,000)   | $0.005  | $0.005   | $0.0045  | $0.004  |
+| Key-value store - writes (per 1,000)  | $0.05   | $0.05    | $0.045   | $0.04   |
+| Key-value store - lists (per 1,000)   | $0.05   | $0.05    | $0.045   | $0.04   |
+| Request queue - reads (per 1,000)     | $0.004  | $0.004   | $0.0036  | $0.0032 |
+| Request queue - writes (per 1,000)    | $0.02   | $0.02    | $0.018   | $0.016  |
 
 If you decide not to offer tiered discounts on your Actor, the unit prices for _FREE_ tier apply. To offer enterprise level services and unlock even cheaper unit prices for enterprise customers, please reach out to us.
 
@@ -50,7 +50,6 @@ When you monetize your Actor in Standby mode using pay per event mode only, you
 
 :::
 
-
 ## Discount tiers and pricing strategy
 
 Each user running your PPE or PPR Actor belongs to a discount tier:

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

@@ -41,7 +41,7 @@ The rental model, while easy to set up, is less profitable because its pricing d
 
 ### AI compatibility limitations
 
-The growing limitation is AI compatibility. Apify's MCP server explicitly excludes rental Actors from search results, making them invisible to AI systems that dynamically select and execute tools. This significantly reduces your Actor's discoverability in AI workflows.
+The growing limitation is AI compatibility. [Apify's MCP server](/platform/integrations/mcp) explicitly excludes rental Actors from search results, making them invisible to AI systems that dynamically select and execute tools. This significantly reduces your Actor's discoverability in AI workflows.
 
 ## Consider pay-per-result or pay-per-event pricing models