fix typos in docs/

Author: jaffrepaul

docs/cli/crons.mdx

@@ -60,7 +60,7 @@ sentry-cli monitors run my-monitor-slug -- node path/to/file.js
 
 You can also use the Sentry CLI to create or update your cron monitor when you run your job. This way, you can avoid having to first set up the monitor through the Sentry web interface.
 
-Configure the cron monitor by providing the cron schdule in crontab format using the `--schedule` or the equivalent `-s` argument when executing the `sentry cli monitors run` command. Please make sure to enclose the schedule in quotes, so that your shell parses the argument correctly, like so:
+Configure the cron monitor by providing the cron schedule in crontab format using the `--schedule` or the equivalent `-s` argument when executing the `sentry cli monitors run` command. Please make sure to enclose the schedule in quotes, so that your shell parses the argument correctly, like so:
 
 ```bash
 sentry-cli monitors run --schedule "<expected schedule>" <monitor-slug> -- <command> <args>

docs/concepts/data-management/event-grouping/fingerprint-rules.mdx

@@ -140,7 +140,7 @@ Matches on the value of the tag `tag_name`. This can be useful to filter down ce
 tags.server_name:"canary-*.mycompany.internal" -> canary-events
 ```
 
-Additionally, the folowing utility matchers are available:
+Additionally, the following utility matchers are available:
 
 ### `app`
 

docs/concepts/data-management/size-limits.mdx

@@ -13,7 +13,7 @@ The following describes how Sentry treats size limits:
 - Events, attachments, and requests exceeding payload size limits are immediately dropped with a `413 Payload Too Large` error.
 - Sentry allows compressed content encoding, and applies separate limits before and after decompression.
 - Events that exceed 200KB compressed or 1MB decompressed will be rejected.
-- Minidump uploads that exceeed 20MB compressed or 100MB decompressed (for all files combined) will also be rejected.
+- Minidump uploads that exceed 20MB compressed or 100MB decompressed (for all files combined) will also be rejected.
 - Event fields exceeding the individual size limits are trimmed and truncated afterwards.
 - The number of events rejected due to size limits is counted towards the _Dropped_ category in [usage stats](/product/stats/#usage-stats).
 

docs/concepts/key-terms/tracing/index.mdx

@@ -44,7 +44,7 @@ You can view all the traces in your organization by going to the [Traces](https:
 
 If you want more information, click on any trace ID. This will take you to the [Trace View](/concepts/key-terms/tracing/trace-view/) page, which provides a more detailed view of the trace and its spans. Here, you'll see a waterfall view of the spans in the trace, which will show you how much time each service and operation took to complete, and may give you an indicator of where a problem may originate. 
 
-![A detailed view of the Senty Traces page showing an expaned trace and spans](./img/Trace-view-page.png)
+![A detailed view of the Sentry Traces page showing an expanded trace and spans](./img/Trace-view-page.png)
 
 Alternatively, you can use the search bar to look for spans by name, project, or other criteria. You can also use the tags section to filter spans by specific tags. Learn more about the Sentry [Trace Explorer](/product/explore/traces/).
 

docs/concepts/search/searchable-properties/index.mdx

@@ -4,7 +4,7 @@ description: "Learn more about searchable properties."
 sidebar_order: 10
 ---
 
-Sentry's search provides you with reserved keywords, like `is`, `user`, `server`, and `browser`, that you can use to search on the properties of issues, events and replays (as well as the special case of releases). You can also create [custom tags](#custom-tags) on which to search. This page provides guidance for how to use these properties and links you to the respective seachable property lists.
+Sentry's search provides you with reserved keywords, like `is`, `user`, `server`, and `browser`, that you can use to search on the properties of issues, events and replays (as well as the special case of releases). You can also create [custom tags](#custom-tags) on which to search. This page provides guidance for how to use these properties and links you to the respective searchable property lists.
 
 ## Search Properties
 

docs/concepts/search/searchable-properties/issues.mdx

@@ -18,7 +18,7 @@ You'll only need to use query syntax for **datetime** and **relative time** sear
 
 ### `age`
 
-Returns issues created since the time defined by the value. The syntax is similar to the Unix find command. Supported suffixes: `m - minutes`, `h - hours`, `d - days`, `w - weeks`. For example, `age:-24h` returns isssues that are new in the last 24 hours, while `age:+12h` returns ones that are older than 12 hours. Entering `age:+12h age:-24h` would return issues created between 12 and 24 hours ago.
+Returns issues created since the time defined by the value. The syntax is similar to the Unix find command. Supported suffixes: `m - minutes`, `h - hours`, `d - days`, `w - weeks`. For example, `age:-24h` returns issues that are new in the last 24 hours, while `age:+12h` returns ones that are older than 12 hours. Entering `age:+12h age:-24h` would return issues created between 12 and 24 hours ago.
 
 - **Type:** relative time
 

docs/contributing/pages/variables.mdx

@@ -9,7 +9,7 @@ The variables available are globally scoped and configured within `remark-variab
 
 For example:
 
-```markdown {tabTitle:Replacment}
+```markdown {tabTitle:Replacement}
 JavaScript SDK: {{@inject packages.version("sentry.javascript.browser") }}
 ```
 

docs/organization/authentication/sso/ping-sso.mdx

@@ -14,7 +14,7 @@ If you change your organization slug, you'll need to make the same update in the
 
 1. Log in to [Ping Identity](https://www.pingidentity.com/en/account/sign-on.html).
 
-1. Go to the "Adminstrators" environment for your organization.
+1. Go to the "Administrators" environment for your organization.
 
 1. If you don't require a permission group for Sentry, skip to step 5.
 

docs/organization/dynamic-sampling/index.mdx

@@ -106,7 +106,7 @@ Because [distributed traces](/product/tracing/#whats-distributed-tracing) can or
 
 For example, if a trace starts in your frontend application, the sample rate you've set there will apply to a connected backend application that's part of the same trace. The same rule applies if the trace starts in a backend application.
 
-If you navigate to the [project preview](https://sentry.io/orgredirect/organizations/:orgslug/settings/dynamic-sampling/) table, you'll see the number of sent spans next to the origin project where the trace started. This includes any spans from propogated traces in other projects that are connected to the origin project. This gives you a direct view of how many spans will be affected by the sample rates you configure. To see the span counts broken down by the project they belong to, click the expand icon to the left of each project in the preview.
+If you navigate to the [project preview](https://sentry.io/orgredirect/organizations/:orgslug/settings/dynamic-sampling/) table, you'll see the number of sent spans next to the origin project where the trace started. This includes any spans from propagated traces in other projects that are connected to the origin project. This gives you a direct view of how many spans will be affected by the sample rates you configure. To see the span counts broken down by the project they belong to, click the expand icon to the left of each project in the preview.
 
 ![Diagram showing the effect of dynamic sampling on distriubuted traces](./img/client-to-backend-accumulated-sampling-effect.png)
 

docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx

@@ -56,7 +56,7 @@ Wait a few minutes as the Lambda functions are enabled. If any functions failed
 
 ### Troubleshooting
 
-If you need help solving issues with your Sentry AWS Lamba integration, you can read the edge cases documented here. If you need additional help, you can [ask on GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose). Customers on a paid plan may also contact support.
+If you need help solving issues with your Sentry AWS Lambda integration, you can read the edge cases documented here. If you need additional help, you can [ask on GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose). Customers on a paid plan may also contact support.
 
 - #### Error `SentryRole already exists`