docs: fix high and medium inaccuracies in integrations pages

sources/platform/integrations/ai/lindy.md

@@ -46,9 +46,9 @@ This section demonstrates how to integrate Apify's data extraction capabilities
 
     ![Apify "Run Actor" module configuration in Lindy, showing a dropdown or search for Actors, with "Instagram profile scraper" selected.](images/lindy/lindy-instagram-actor.png)
 
-:::tip Actor Availability
+:::tip Actor availability
 
-You have access to thousands of Actors available on the [Apify Store](https://apify.com/store). Please note that Actors using the _rental pricing model_ are not available for use with this integration. For details on Actor pricing models, refer to our [Pricing Documentation](/platform/actors/publishing/monetize#rental-pricing-model).
+You have access to thousands of Actors available on the [Apify Store](https://apify.com/store). Please note that Actors using the _rental pricing model_ are not available for use with this integration. The rental pricing model is being retired during 2026 and migrated to pay-per-usage. For details, refer to our [rental pricing model documentation](/platform/actors/publishing/monetize/rental).
 
 :::
 

sources/platform/integrations/ai/mastra.md

@@ -116,7 +116,7 @@ await mcpClient.disconnect();
 
 :::note Use any Apify Actor
 
-Since it uses the [Apify MCP server](https://mcp.apify.com), swap in any Apify Actor from the [Apify Store](https://apify.com/store) by updating the startup request’s `actors` parameter.
+Since it uses the [Apify MCP server](https://mcp.apify.com), swap in any Apify Actor from the [Apify Store](https://apify.com/store) by adding it to the `tools` query parameter in the server URL (for example, `https://mcp.apify.com/?tools=apify/rag-web-browser`).
 No other changes are needed in the agent code.
 
 :::

sources/platform/integrations/programming/webhooks/actions.md

@@ -51,7 +51,7 @@ You can also use [Headers template](/platform/integrations/webhooks/actions#head
 
 :::
 
-Note that webhook HTTP requests have a timeout of _30 seconds_.
+Note that webhook HTTP requests have a timeout of _2 minutes_.
 If your endpoint performs a time-consuming operation, respond to the request immediately to prevent timeouts before Apify receives the response. To ensure reliable completion of the time-consuming operation, consider using a message queue internally to retry the operation on internal failure.
 
 In rare cases, the webhook might be invoked more than once.

sources/platform/integrations/workflows-and-notifications/gumloop/index.md

@@ -71,7 +71,7 @@ To use the Apify integration in Gumloop, you need an Apify account, a Gumloop ac
 
 1. _Create and save tasks in Apify_
 
-   The Apify Task Runner node fetches tasks from your saved tasks in Apify Console. To create a task, navigate to [**Actors**](https://console.apify.com/actors), click on the Actor you want to use, and then click **Create a task** next to the Run button. Configure your task settings and save.
+   The Apify Task Runner node fetches tasks from your saved tasks in Apify Console. To create a task, navigate to [**Actors**](https://console.apify.com/actors), click on the Actor you want to use, and then click **Save as a new task** next to the Run button. Configure your task settings and save.
 
     ![Create a task on an Actor](images/create_apify_task.png)
 

sources/platform/integrations/workflows-and-notifications/slack.md

@@ -54,7 +54,7 @@ A few rules apply to every template:
 
 - The template must be between 2 and 4000 characters long.
 - The text supports [Slack's mrkdwn syntax](https://api.slack.com/reference/surfaces/formatting), which uses single-asterisk bold (`*bold*`) and `<url|label>` for links rather than the standard Markdown `[label](url)`.
-- Apify automatically appends a "Sent by Apify" attribution line that links to apify.com, so you don't need to add one yourself.
+- Apify automatically appends a "Sent by Apify" attribution line that links to the integration's settings page in Apify Console, so you don't need to add one yourself.
 - `TEST` events ignore the template and post a fixed test message. Use them to verify channel delivery.
 - An empty template falls back to Apify's built-in run-status preset.
 
@@ -126,8 +126,8 @@ For `ACTOR.BUILD.*` events, `resource` is the build document - the same object r
 
 The `resource.status` field uses these values:
 
-- Actor run: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `ABORTED`, `TIMED-OUT`, `ABORTING`.
-- Actor build: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `ABORTED`, `TIMED-OUT`.
+- Actor run: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `TIMING-OUT`, `TIMED-OUT`, `ABORTING`, `ABORTED`.
+- Actor build: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `TIMING-OUT`, `TIMED-OUT`, `ABORTING`, `ABORTED`.
 
 :::tip Full resource object