diff --git a/docs/pricing/quotas/manage-event-stream-guide.mdx b/docs/pricing/quotas/manage-event-stream-guide.mdx
index 9eb4b9b77028e5..b2bc2d581b22cb 100644
--- a/docs/pricing/quotas/manage-event-stream-guide.mdx
+++ b/docs/pricing/quotas/manage-event-stream-guide.mdx
@@ -51,12 +51,6 @@ Once the changes are applied, sort the "Results" table by the "COUNT()" column t
 
 Once you know where your quota is being used, you can start taking the steps below to control it.
 
-## Grace Period
-
-All accounts have access to a one-time grace period. This means that if an account depletes its error event volume and has never previously triggered a grace period, we continue to accept events for the next three days at a maximum rate of 10,000 events per hour. If you choose not to increase your error volume, Sentry will stop accepting events for the remainder of the current billing month. However, if you increase your volume, error events accepted during the grace period will be counted as consumed volume.
-
-While this grace period isn't dependent on the [Spike Protection feature](#7-spike-protection), you'll probably get a notification that you've entered a grace period along with a notification of a spike.
-
 ## Spike Protection
 
 Spike Protection protects users from spiking event volume. Typically, spikes are caused by anomalies and have the potential to deplete your available event volume rapidly. Your baseline consumption is used to compute a threshold and spike protection is triggered if event volume exceeds this threshold. When spike protection is triggered, events start getting dropped, ensuring that you don't get charged for the excess volume.