diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
index 477a1d7c996..e34d33b8165 100644
--- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx
+++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
@@ -365,6 +365,7 @@ You can see your query scan operations and any limit incidents in the [limits UI
 
 When matching events to alert queries, all events from the [data type](/docs/nrql/get-started/introduction-nrql-new-relics-query-language/#what-you-can-query) that the query references must be examined. Here are a few common ways to have fewer events in a given data type (which will decrease the alert query scan operations):
 * 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/analyze-monitor-data-trends-metrics/) to aggregate data.