docs: align Slack and scheduled scan guides

platform/automations/scheduled-whitebox-scans.mdx

@@ -1,17 +1,17 @@
 ---
 title: "Scheduled whitebox scans"
 description: "Schedule recurring whitebox scans with saved settings for each environment."
 ---
 
 [Automations](/platform/automations/overview) can run whitebox scans on a schedule. Each environment has saved scan settings for its repositories, scope, targets, and credit limit.
 
 Organization **Admins** create and manage scheduled scans. Runs spend the organization's [Whitebox Scan credits](/white-box-pentest/billing).
 
 ## Create a scheduled scan
 
 On **Automations**, select **New automation**, give it a name, and add the repositories or [applications](/platform/context/applications) to scan on the **Environments** tab.
 
-An automation with **On a schedule** runs a whitebox scan of each of its environments at the times you set. Adding the trigger sets the action to **Start whitebox scan**, which the **Settings** tab shows as **Start a whitebox scan for each configured environment**. Removing the trigger removes that action too.
+Choose **On a schedule** to run a whitebox scan of each environment at the times you set. Hacktron adds **Start whitebox scan** automatically. Removing the schedule also removes that scan action.
 
 <Steps>
   <Step title="Set the schedule">
@@ -31,12 +31,12 @@
     <div className="block dark:hidden">
 
   <Frame>
     <img src="/images/automation-schedule-light.webp" alt="A weekly schedule at 02:00 UTC on the Settings tab, with its next three runs and the whitebox scan action" />
   </Frame>
 </div>
 <div className="hidden dark:block">
   <Frame>
     <img src="/images/automation-schedule-dark.webp" alt="A weekly schedule at 02:00 UTC on the Settings tab, with its next three runs and the whitebox scan action" />
   </Frame>
 </div>
 
@@ -44,7 +44,7 @@
 
   </Step>
   <Step title="Set up the scan for each environment">
-    On the **Environments** tab, each environment now has **Set up scan** in place of the branch picker. Select it to open the environment's scan settings. They reuse the steps of the [Whitebox Scans wizard](/white-box-pentest/quickstart), with **Scan options** in place of the cost calculation and checkout:
+    On the **Environments** tab, each environment now has **Set up scan** in place of the branch picker. Select it to open the environment's scan settings. Configure the scan using these steps. The [Whitebox quickstart](/white-box-pentest/quickstart) explains source selection, scope, and dynamic testing.
 
     | Step | What it sets |
     | --- | --- |
@@ -70,11 +70,11 @@
 
 Saved login instructions are checked before every scan. If the login fails, that scan doesn't start. To check them straight away, select **Save and check login** on the last step of the scan settings. The result shows on the **Define targets** and **Review details** steps, and the check appears in the [run history](#run-history) as **Login check**.
 
 If authenticated testing isn't enabled for your organization, Hacktron keeps the login instructions, but scans that need them can't start until it's enabled.
 
 ## Credits and skipped scans
 
 Scheduled scans spend the organization's [Whitebox Scan credits](/white-box-pentest/billing). Each scan gets a fresh cost estimate. **Max whitebox credits per scan** includes the scan and any human triage it needs. A scan above that limit, or one the balance can't cover, doesn't start, and its run shows **Needs attention** with the reason. If the previous scan for an environment is still in progress when the next one is due, the next one is skipped. Missed scans are skipped too.
 
 ## Run history