From d4bf2905785b97f0c88e406a23e7feac5bfe8c32 Mon Sep 17 00:00:00 2001
From: Haus Owens <98408+haus@users.noreply.github.com>
Date: Tue, 29 Oct 2024 14:01:32 -0700
Subject: [PATCH] Tweak language in a few bullets

---
 src/content/docs/alerts/admin/rules-limits-alerts.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
index a0164794cc5..ab563f45cf4 100644
--- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx
+++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
@@ -372,8 +372,8 @@ When matching events to alert queries, all events from the [data type](/docs/nrq
 * When alerting on Logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries.
 * When alerting on Custom Events, break up larger custom event types
 * Use Custom Events instead of alerting on Transaction events
-* [Create metrics](/docs/data-apis/convert-to-metrics/create-metrics-other-data-types/) when possible
-* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction
+* [Create metrics](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) to aggregate data
+* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction events
 
 In addition to the above tips, cleaning up any unused or unneeded alert queries (alert conditions) will decrease the number of query scan operations.