diff --git a/src/content/docs/docs/incident-management/integrations/index.mdx b/src/content/docs/docs/incident-management/integrations/index.mdx
index cb063c6..94f8755 100644
--- a/src/content/docs/docs/incident-management/integrations/index.mdx
+++ b/src/content/docs/docs/incident-management/integrations/index.mdx
@@ -28,7 +28,10 @@ KloudMate Alarm and CloudWatch Alarm sources use built-in templates. To integrat
 
 Open **Incident Management → Alert Sources** to see every source with its name, description, type, service, and escalation policy.
 
-![image](./images/integrations-1.jpeg)
+:::note[Placeholder image]
+Screenshot pending — the Alert Sources list showing each source's name, type, service, and escalation policy.
+:::
+![Alert sources list](../../_placeholders/screenshot-placeholder.png)
 
 ## Alert source details
 
diff --git a/src/content/docs/docs/incident-management/integrations/integrating-with-aws-cloudwatch.mdx b/src/content/docs/docs/incident-management/integrations/integrating-with-aws-cloudwatch.mdx
index 1712fdc..7e91ca0 100644
--- a/src/content/docs/docs/incident-management/integrations/integrating-with-aws-cloudwatch.mdx
+++ b/src/content/docs/docs/incident-management/integrations/integrating-with-aws-cloudwatch.mdx
@@ -35,7 +35,7 @@ Create a unique ingestion endpoint in KloudMate to receive your CloudWatch alert
 
 6. Click **Save**.
 
-7. From the details page of your new alert source, copy the **Source URL** (e.g., `https://api.kloudmate.com/im/hooks/cw-a1b2c3d4e5f6`).
+7. From the details page of your new alert source, copy the **Source URL** (e.g. `https://api.kloudmate.com/im/hooks/cw-a1b2c3d4e5f6`).
 </Steps>
 
 :::note[Placeholder image]
@@ -103,7 +103,7 @@ KloudMate processes incoming CloudWatch alarm payloads automatically to keep you
 
 ### Grouping and deduplication
 
-To prevent alert fatigue and duplicate notifications, KloudMate groups incoming alarm events:
+To prevent alert fatigue and duplicate notifications, KloudMate groups incoming alert events:
 
 - When an alarm enters the `ALARM` state, AWS SNS pushes the event payload to KloudMate.
 - KloudMate generates a unique **Group ID** by hashing the `AlarmName` from the payload.
@@ -116,7 +116,7 @@ When the underlying issue clears, KloudMate resolves the incident automatically:
 
 - When the CloudWatch alarm transitions back to `OK`, AWS SNS pushes the state change to KloudMate.
 - KloudMate inspects the payload (`NewStateValue == "OK"`), identifies it as a recovery signal, and automatically marks the active incident as **Resolved**.
-- This immediately halts the escalation policy, stopping any further team paging or alerts.
+- This immediately halts the escalation policy, stopping any further notifications.
 
 ## Related
 
diff --git a/src/content/docs/docs/incident-management/integrations/integrating-with-kloudmate-alerts.mdx b/src/content/docs/docs/incident-management/integrations/integrating-with-kloudmate-alerts.mdx
index 6c1c94b..dda594d 100644
--- a/src/content/docs/docs/incident-management/integrations/integrating-with-kloudmate-alerts.mdx
+++ b/src/content/docs/docs/incident-management/integrations/integrating-with-kloudmate-alerts.mdx
@@ -44,7 +44,7 @@ Screenshot pending — the Notification Channels create form with KloudMate Inci
 ## Step 2 — Route alerts to the channel
 
 <Steps>
-1. Open **Settings → Routing Rules → Create**.
+1. Open **Alerts → Routing Rules → Create**.
 
 2. Name the rule and set a priority (lower wins).