docs: Fix grammar and spelling mistakes for Kestra integration docs.

Author: ammeek

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

@@ -1,26 +1,26 @@
 ---
 title: Kestra integration
-description: Connect Apify with Kestra to orchestrate workflows — run Flows, extract structured data, and react to Actor or task events in real time.
+description: Connect Apify with Kestra to orchestrate workflows — run flows, extract structured data, and react to Actor or task events in real time.
 sidebar_label: Kestra
 sidebar_position: 7
 slug: /integrations/kestra
 ---
 
-**Connect Apify with Kestra to orchestrate workflows — run Flows, extract structured data, and react to Actor or task events in real time.**
+**Connect Apify with Kestra to orchestrate workflows — run flows, extract structured data, and react to Actor or task events in real time.**
 
 ---
 
 [Kestra](https://kestra.io/) is an open-source, event-driven orchestration platform that unifies workflows for all engineers.
-With the [Apify plugin for Kestra](https://github.com/apify/kestra-plugin-apify), you can seamlessly connect Apify Actors and storage to your workflows.
+With the [Apify plugin for Kestra](https://github.com/kestra-io/plugin-kestra), you can seamlessly connect Apify Actors and storage to your workflows.
 Run scrapers, extract structured data — all defined declaratively in YAML and orchestrated directly from the UI.
-In this guide, you'll learn how to set up authentication and incorporate it into a Kestra flows.
+In this guide, you'll learn how to set up and incorporate authentication into a Kestra flows.
 
 ## Prerequisites
 
 Before you begin, make sure you have:
 
 - An [Apify account](https://console.apify.com/)
-- An [Kestra instance](https://kestra.io/docs/getting-started/quickstart) (self‑hosted or cloud)
+- A [Kestra instance](https://kestra.io/docs/getting-started/quickstart) (self‑hosted or cloud)
 
 Once installed, the next step is authentication.
 
@@ -50,15 +50,15 @@ or fetching data.
 Tasks allow you to perform operations like running an Actor within a workflow.
 
 1. Create a new flow.
-1. Inside the **Flow code** tab change the hello tasks type to be **io.kestra.plugin.apify.actor.Run**.
-1. Change the tasks id to be **run_apify_actor**
+1. Inside the **Flow code** tab change the hello task's type to be **io.kestra.plugin.apify.actor.Run**.
+1. Change the task's id to be **run_apify_actor**
 1. Remove the message property.
 1. Configure the **run_apify_actor** task by adding your required values for the properties listed below:
     - **actor id**: Actor ID or a tilde-separated owner's username and Actor name.
     - **apiToken**: A reference to the secret value you set up earlier. For example "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}"
 1. Add a new task below the **run_apify_actor** with an ID of **get_dataset** and a type of **io.kestra.plugin.apify.dataset.Get**.:
 1. Configure the **get_dataset** to fetch the dataset generated by the **run_apify_actor** task by configuring the following values:
-    - **datasetId**: The Id of the dataset to fetch. You can use the value from the previous task using the following syntax: "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}"
+    - **datasetId**: The ID of the dataset to fetch. You can use the value from the previous task using the following syntax: "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}"
     - **apiToken**: A reference to the secret value you set up earlier. For example '\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}'
     - **input**: Input for the Actor run. The input is optional and can be used to pass data to the Actor. For our example we will add 'hashtags: ["fyp"]'
     - **maxItems**: The maximum number of items to fetch from the dataset. For our example we will set this to 5.