Update docs/product/monitors-and-alerts/index.mdx

Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

Author: sfanahata

docs/product/monitors-and-alerts/index.mdx

@@ -12,7 +12,7 @@ early_access: true
 Sentry separates **what you detect** from **what you do about it**:
 
 - [**Monitors**](/product/monitors-and-alerts/monitors/) watch your application and operational signals. There are default detectors that pull data from your SDK integration. Custom configurations like, cron schedules, HTTP uptime, metric thresholds on spans and custom metrics, can also be monitored. With Monitors, these signals are turned into **issues** when conditions are met.
-- [**Alerts**](/product/monitors-and-alerts/alerts/) run when **issues** match the triggers and filters you configure, and carry out **actions** like Slack, email, PagerDuty, webhooks notifications, or creating work items in Jira and similar tools.
+- [**Alerts**](/product/monitors-and-alerts/alerts/) run when **issues** match the triggers and filters you configure, and carry out **actions** like sending notifications via Slack, email, PagerDuty, or webhooks, or creating work items in Jira and similar tools.
 
 Using both Monitors and Alerts gives you a path from signal → triageable issue → team workflow, without wiring every integration by hand for every edge case.