ref(spike protection): add note about recalculating thresholds during spike (#8728)

Author: cathteng

src/docs/product/accounts/quotas/spike-protection.mdx

@@ -35,6 +35,8 @@ If you're an existing Sentry user with Spike Protection enabled on an org level,
 
 Sentry uses an algorithm to establish a spike threshold for each project. When this threshold is reached, a spike is flagged. Sentry then applies a dynamic rate limit to your project and begins discarding events to keep your quota from being consumed too quickly. This protects you from short-term spikes. But because of the algorithm's dynamic nature, if the event volume continues to be high for a sustained period of time, it'll become your new baseline and you may quickly run through your quota.
 
+Spike thresholds are recalculated every hour for the duration of the spike. This is done to gradually increase thresholds over time to account for new traffic patterns.
+
 Spike Protection will automatically deactivate once the spike event passes, until the next time a spike is detected.
 
 ### A Dynamic Algorithm