fix: replace typo in RateLimits section (#6113)

Corrected only one word `approximantely` -> `approximately`

Author: olksdr

src/docs/product/accounts/quotas/manage-event-stream-guide.mdx

@@ -261,7 +261,7 @@ A good way to set a project rate limit is by figuring out the expected event vol
 1. In the "KEY USAGE IN THE LAST 30 DAYS" graph, look for the highest point, or the maximum daily rate. In the example below, the maximum daily rate in the last month is less than 34K:
    ![Calculating rate limits](manage-event-stream-14-new.png)
    <!-- image notes: Sentry, airflow, Santry, app-frontend -->
-1. Based on the rate, choose a **daily** maximum value or ceiling. In this example, we calculated a daily maximum of approximantely 35K, which is around 1458 events an **hour**, or about 24 events a **minute**.
+1. Based on the rate, choose a **daily** maximum value or ceiling. In this example, we calculated a daily maximum of approximately 35K, which is around 1458 events an **hour**, or about 24 events a **minute**.
 1. Set a daily, hourly, or minute-based rate limit. We recommend using a minute-based rate to avoid situations where a random event spike might exhaust your daily or hourly quota and leave you without event data for a long period.
 
 You should periodically go back and check the graph to see the number of events dropped due to rate limiting and, if needed, revisit your settings.