Fix typos (#68659)

Fix usage of `cound`.

### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

Author: ViToni

src/sentry/issues/escalating_issues_alg.py

@@ -55,7 +55,7 @@ def generate_issue_forecast(
     is relative to the data. The CV is then placed into an exponential equation that outputs
     a multiplier inversely related to how high the cv is. The multiplier is bounded between 2 and 5. The
     ceilings for the next week are all the same - which is the maximum number of events in an hour over the
-    past week multiplied by this multiplier. This calculation is to accound for bursty issues or those that
+    past week multiplied by this multiplier. This calculation is to account for bursty issues or those that
     have a very high variance.
     The final spike limit for each hour is set to the max of the bursty limit bound or the calculated limit.
     :param data: Dict of Snuba query results - hourly data over past 7 days

static/app/utils/replays/hooks/useLogReplayDataLoaded.tsx

@@ -29,7 +29,7 @@ function useLogReplayDataLoaded({fetchError, fetching, projectSlug, replay}: Pro
 
     // BUG(replay): This will often report the discrepancy between errors
     // accociated with the replay, and errors the replay knows about.
-    // ie: When an error is filtered server-side, it would cound as a replay with 1
+    // ie: When an error is filtered server-side, it would count as a replay with 1
     // backend error.
     const feErrorIds = replayRecord.error_ids || [];
     const beErrorCount = allErrors.filter(