From 731524d6443d2b1cde3637ed336b2f5e36a3fa1c Mon Sep 17 00:00:00 2001
From: Cathy Teng <70817427+cathteng@users.noreply.github.com>
Date: Fri, 12 Jan 2024 11:26:19 -0800
Subject: [PATCH] fix(spike protection): clarify cap on num_projects in
 heuristic (#8869)

---
 src/docs/product/accounts/quotas/spike-protection.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/product/accounts/quotas/spike-protection.mdx b/src/docs/product/accounts/quotas/spike-protection.mdx
index c3bd51cd69840..6c1d7842829f9 100644
--- a/src/docs/product/accounts/quotas/spike-protection.mdx
+++ b/src/docs/product/accounts/quotas/spike-protection.mdx
@@ -82,7 +82,7 @@ As mentioned above, our Spike Protection Algorithm is based on the higher of two
 
 ### Minimum Event Calculation
 
-This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 500 events or the result of the following formula `(3 \* your quota)/(720 \* number of projects)`. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike.
+This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 500 events or the result of the following formula `(3 \* your quota)/(720 \* number of projects)`. The number of projects is capped at 5 and is used to adjust the floor. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike.
 
 ### Usage-Based Calculation