fix typos in develop-docs/ and source files

Author: jaffrepaul

app/[[...path]]/page.tsx

@@ -199,7 +199,7 @@ export async function generateMetadata(props: MetadataProps): Promise<Metadata>
   const domain = isDeveloperDocs
     ? 'https://develop.sentry.dev'
     : 'https://docs.sentry.io';
-  // enable og iamge preview on preview deployments
+  // enable og image preview on preview deployments
   const previewDomain = process.env.VERCEL_URL
     ? `https://${process.env.VERCEL_URL}`
     : domain;

develop-docs/application-architecture/multi-region-deployment/cross-region-rpc.mdx

@@ -59,7 +59,7 @@ Service classes act as stubs that define the interface a service will have. In t
 - `local_mode` defines which silo mode this service uses it’s ‘local implementation’. Services can have local implementations in either silo mode.
 - `get_local_implementation` is used by the RPC machinery to find the implementation service when the silo mode matches or is `MONOLITH`.
 
-RPC methods like `get_org_by_slug` must be defined as `abstractmethod` and must have either `rpc_method` or `regional_rpc_method` applied. If a method has `local_mode = REGION` it should use `regional_rpc_method` with a resolve ‘resolver’. There are several resolvers that accomodate a variety of method call signatures:
+RPC methods like `get_org_by_slug` must be defined as `abstractmethod` and must have either `rpc_method` or `regional_rpc_method` applied. If a method has `local_mode = REGION` it should use `regional_rpc_method` with a resolve ‘resolver’. There are several resolvers that accommodate a variety of method call signatures:
 
 - `ByOrganizationSlug` will extract the `organization_slug` parameter and use it to locate the region using `sentry_organizationmapping`.
 - `ByOrganizationId` will extract the `organization_id` parameter and use it to locate the organization’s region using `sentry_organizationmapping`

develop-docs/application-architecture/overview.mdx

@@ -40,7 +40,7 @@ This graph is extremely simplified mostly due to layout constraints. Missing fro
 * How Relay fetches project configs. Answer: from sentry-web
 * How Relay caches project configs. Answer: In memory, and in Redis
 * How Relay counts events and keeps track of quotas. Answer: more Redis
-* Symbolicator as auxilliary service to symbolicate-event
+* Symbolicator as auxiliary service to symbolicate-event
 * How alerting is triggered. Answer: postprocess-event, a Celery task which is responsible for alerting (spawned by a Kafka consumer in Sentry reading from eventstream)
 * Possibly more
 

develop-docs/backend/api/design.mdx

@@ -3,7 +3,7 @@ title: Design Principles
 sidebar_order: 2
 ---
 
-This document contains a set of design principles and requirements whish should be applied to all Sentry APIs. These are _requirements_ when designing public APIs (such as Sentry's Web API), but internal APIs (such as an an internal service that Sentry communicates with) should attempt to adhere to these principles as well where it makes sense.
+This document contains a set of design principles and requirements which should be applied to all Sentry APIs. These are _requirements_ when designing public APIs (such as Sentry's Web API), but internal APIs (such as an an internal service that Sentry communicates with) should attempt to adhere to these principles as well where it makes sense.
 
 In the Sentry monolith, we use [Django REST framework](https://www.django-rest-framework.org/) (DRF).
 

develop-docs/backend/api/serializers.mdx

@@ -163,7 +163,7 @@ class ModelSerializer(Serializer):
 
 **get_attrs Method**
 
-Why do this when Django Rest Framework has similar functionality? The `get_attrs` method is the reason. It allows you to do a bulk query versus multiple queries. In our example, instead of calling `ExampleTypes.objects.get(...)` multiple items, I can filter for the ones I want and assign them to the item in question using python. In the case of `attr` dictionary, the `key` is the item iteself. and the `value` is a dictionary with the name of the attribute you want to add and it's values.
+Why do this when Django Rest Framework has similar functionality? The `get_attrs` method is the reason. It allows you to do a bulk query versus multiple queries. In our example, instead of calling `ExampleTypes.objects.get(...)` multiple items, I can filter for the ones I want and assign them to the item in question using python. In the case of `attr` dictionary, the `key` is the item itself. and the `value` is a dictionary with the name of the attribute you want to add and it's values.
 
 ```python
 attrs[item] = {'attribute_name': attribute}

develop-docs/backend/application-domains/feature-flags/flagpole.mdx

@@ -84,11 +84,11 @@ Flagpole currently supports the following `operator` types:
 
 `contains`
 
-: Given a single int, string, float, or boolean value, evalutes to `True` if the context property value is a list containing the provided value.
+: Given a single int, string, float, or boolean value, evaluates to `True` if the context property value is a list containing the provided value.
 
 `not_contains`
 
-: The inverse of `contains`, evalutes to `True` if the context property value is a list which does not contain the provided value.
+: The inverse of `contains`, evaluates to `True` if the context property value is a list which does not contain the provided value.
 
 `equals`
 
@@ -114,7 +114,7 @@ Here are some common properties we surface via our Sentry and GetSentry context
 
 `sentry_region` [str]
 
-: The sentry region or single-tenant the flag check is being perfomed in.
+: The sentry region or single-tenant the flag check is being performed in.
 
 `sentry_singletenant` [bool]
 

develop-docs/backend/application-domains/grouping.mdx

@@ -8,7 +8,7 @@ which can be customized [on the client](https://docs.sentry.io/platforms/python/
 and on the server via [fingerprint rules](https://docs.sentry.io/product/data-management-settings/event-grouping/fingerprint-rules/)
 and [stack trace rules](https://docs.sentry.io/product/data-management-settings/event-grouping/stack-trace-rules/).
 
-This documentation attemps to explain how the system currently functions and what limitations exist presently with it.
+This documentation attempts to explain how the system currently functions and what limitations exist presently with it.
 
 # Basics
 
@@ -192,8 +192,8 @@ The following general paths forward are current envisioned:
 
 The consequences of making too many groups today are alert spam and the inability to work with multiple
 issues at once.  If Sentry were to no longer be alerting on all new groups and tools existed to work
-across multiple groups more opportunies arise.  In particular the grouping algorithm could continue to
-just fingerprint the stack trace but a secondary process could come in peridically and sweep up related
+across multiple groups more opportunities arise.  In particular the grouping algorithm could continue to
+just fingerprint the stack trace but a secondary process could come in periodically and sweep up related
 fingerprints into a larger group.  If we take the `get_current_user` example the creation of 50 independent
 groups is not much of an issue if no alerts are fired.  If after 5 minute the system detected that they are
 in fact all very related (eg: the bug is "in `get_current_user`") it could leave the 50 generated groups

develop-docs/backend/application-domains/nodestore.mdx

@@ -26,4 +26,4 @@ If you have a favorite data storage solution, it only has to operate under a few
 - get key
 - delete key
 
-For more information on implementating your own backend, take a look at `sentry.nodestore.base.NodeStorage`.
+For more information on implementing your own backend, take a look at `sentry.nodestore.base.NodeStorage`.

develop-docs/backend/application-domains/pii/selectors.mdx

@@ -102,7 +102,7 @@ Select known parts of the schema using the following:
   [Remove] [Anything] from [$frame.vars]
   ```
 
-### Escaping Specal Characters
+### Escaping Special Characters
 
 If the object key you want to match contains whitespace or special characters,
 you can use quotes to escape it:

develop-docs/development-infrastructure/analytics.mdx

@@ -308,11 +308,11 @@ If your analytics aren't showing up after you added it, you can't find an event
 - Check Amplitude for blocked events: In Amplitude, go to the "Data" section in the sidebar. From there, navigate to "Events" and search for your event name. It will show up with status "Blocked" if blocked, which means events won't show up. Some events may be blocked in favor of automatic route or button analytics.
 - For route analytics, confirm that the analytic event isn't being blocked with `useDisableRouteAnalytics`. Some components already had an analytic event so the route analytics were disabled.
 - Check the types of the data you are sending. Arrays aren't recommended data types to send (they can be hard to query and produce some unexpected behavior). Try to remove those if you are using them.
-- Remember there will always be some discrepency. Ad-blockers, for example, can block events from being sent. This could be a cause of why some numbers aren't adding up.
+- Remember there will always be some discrepancy. Ad-blockers, for example, can block events from being sent. This could be a cause of why some numbers aren't adding up.
 
 ## Metrics
 
-Track aggregrate stats with [Metrics](/backend/metrics/). For example, this can be used to track aggregate response codes for an endpoint.
+Track aggregate stats with [Metrics](/backend/metrics/). For example, this can be used to track aggregate response codes for an endpoint.
 
 Import the metrics library and use the `metrics.inc` function. The key needs to be unique.