fix(spike protection): mention all applicable categories (#7573)

Author: cathteng

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

@@ -5,7 +5,9 @@ sidebar_order: 10
 description: "Learn how to manage your quota and make sure that your volume isn't consumed all at once with Spike Protection."
 ---
 
-A spike is a significant, temporary increase in your error event volume. Because Sentry bills based on the number of monthly events sent, spikes can quickly consume your quota for an entire month. Spike Protection guards against this by establishing a spike threshold for the average number of error events each of your projects sends and then dropping them after that threshold is reached.
+A spike is a significant, temporary increase in your event volume. Because Sentry bills based on the number of events sent monthly, spikes can quickly consume your quota for an entire month. Spike Protection guards against this by establishing a spike threshold for the average number of events each of your projects sends and then dropping them after that threshold is reached.
+
+Spike Protection currently applies to errors, transactions, and attachments.
 
 <Note>
 
@@ -25,7 +27,7 @@ If you're an existing Sentry user with Spike Protection enabled on an org level,
 
 ## How Sentry Detects Spikes {#how-to-detect}
 
-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 error 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 error 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.
+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 Protection will automatically deactivate once the spike event passes, until the next time a spike is detected.
 
@@ -53,12 +55,12 @@ We recommend taking the following steps to manage your spikes:
 
 - Check to see which issues are [consuming your quota](https://sentry.sentry.io/stats/).
 - Set [rate limits](/product/accounts/quotas/manage-event-stream-guide/#6-rate-limiting) on the DSN keys for the projects related to the spike.
-- Set up [metric alerts](/product/alerts/alert-types/#metric-alerts) for the number of errors in a project.
+- Set up [metric alerts](/product/alerts/alert-types/#metric-alerts) for the number of events in a project.
 - If a specific release version has caused the spike, add the version identifier to the project's [inbound filters](/product/accounts/quotas/manage-event-stream-guide/#3-inbound-data-filters) to avoid accepting events from that release.
 - Set up an [on-demand budget](/product/accounts/quotas/manage-event-stream-guide/#on-demand-budget) to make sure you have time to adjust your volume in the event of a future spike.
 - Set up [spend allocations](/product/accounts/quotas/#spend-allocation) to ensure your critical projects are guaranteed a portion of your reserved volume, even if there are spikes in other projects.
 
-To review the error events that were dropped to save your quota with Spike Protection, go to the "Usage Stats" tab of the **Stats** page for your Sentry org and select "Errors" in the "Category" dropdown. You can see project-level details of your stats by using the project selector. Sentry can show the spike threshold for a time duration greater than 6hrs and less than 30 days.
+To review the events that were dropped to save your quota with Spike Protection, go to the "Usage Stats" tab of the **Stats** page for your Sentry org and select the desired event in the "Category" dropdown. You can see project-level details of your stats by using the project selector. Sentry can show the spike threshold for a time duration greater than 6hrs and less than 30 days.
 
 ![Spike limit threshold](spike-limit-threshold.png)