From ff3416a6487c860ebd45c4454fe19f9e0a3ee3ff Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 15 Nov 2024 09:43:48 +0000
Subject: [PATCH] Update website/docs/docs/deploy/advanced-ci.md

---
 website/docs/docs/deploy/advanced-ci.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/website/docs/docs/deploy/advanced-ci.md b/website/docs/docs/deploy/advanced-ci.md
index 4936857133..e502a140b8 100644
--- a/website/docs/docs/deploy/advanced-ci.md
+++ b/website/docs/docs/deploy/advanced-ci.md
@@ -33,7 +33,6 @@ dbt reports the comparison differences in:
 
 ### Speeding up comparisons
 
-It's common for CI jobs to only [build a subset of data](/best-practices/best-practice-workflows#limit-the-data-processed-when-in-development) (for example only the last 7 days of data). 
 
 When an [`event_time`](/reference/resource-configs/event-time) column is specified on your model, compare changes can optimize comparisons by using only the overlapping timeframe (meaning the timeframe exists in both the CI and production environment), helping you avoid incorrect row-count changes and return results faster.