Typos, broken links, other small fixes (#1277)

* broken link

* thank you Triplechecker

* fix broken links

Author: serverless-mom

site/content/docs/accounts-and-users/multi-factor-authentication.md

@@ -28,4 +28,4 @@ From now on when logging in you will be asked to provide a one time password.
 
 ## Removing or changing MFA
 - To stop using MFA, toggle the 'Enable multi-factor authentication' setting under User Settings.
-- If you have lost access to your authenticator app or removed the Checkly configuration from it, contact [[email protected]](mailto:[email protected]) for help with resetting your configration.
+- If you have lost access to your authenticator app or removed the Checkly configuration from it, contact [[email protected]](mailto:[email protected]) for help with resetting your configuration.

site/content/docs/api-checks/assertions.md

@@ -234,7 +234,7 @@ Regular expressions give you the power to extract specific parts of text from a
 You can use regular expressions with two assertions sources:
 
 1. **Text body:** Use the property field to add your regex.
-2. **Headers:** First select the header you are interested in in the property field, then click "add regex".
+2. **Headers:** First select the header you are interested in the property field, then click "add regex".
 
 Under the hood, we use the stock Javascript regular expressions implementation. Specifically, we use the [.match()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/match)
 method. We *do not use the `/g` modifier* and return the first matched group the expression finds.

site/content/docs/api-checks/request-settings.md

@@ -77,7 +77,7 @@ Form encodes bodies are commonly used "traditional" HTML form submissions.
 
 ### Raw data
 
-If the predefined data types don't work for you, use `Raw data`. Make sure to define your `Content-Type` header explicitely then.
+If the predefined data types don't work for you, use `Raw data`. Make sure to define your `Content-Type` header explicitly then.
 
 > To monitor an XML/SOAP-based API define `text/xml; charset=utf-8` as `Content-Type` header, send your XML as `Raw data` and [use a setup script to parse required access tokens](/docs/api-checks/setup-script-examples/#parse-xmlsoap-data).
 

site/content/docs/browser-checks/degraded-state.md

@@ -12,7 +12,7 @@ menu:
 
 If you want to monitor your service for non-critical errors or performance degradations you can use the degraded check state. This allows you to signal that parts of a Browser check performed slower than expected, or that it triggered assertions that are of lower criticality. 
 
-The degraded state does not affect your check's success ratio like a failed state does. You can [configure alert channels](/docs/alerting-and-retries/alert-channels/#managing-alert-channels) to notifiy you when a check has degraded. 
+The degraded state does not affect your check's success ratio like a failed state does. You can [configure alert channels](/docs/alerting-and-retries/alert-channels/#managing-alert-channels) to notify you when a check has degraded. 
 
 To catch errors that are relevant for a degraded scenario you can use soft assertions. Soft assertions keeps your Playwright test running after it has encountered an error, unlike regular assertions which terminate the test. See the [playwright docs](https://playwright.dev/docs/test-assertions#soft-assertions) for more information on soft assertions.
 

site/content/docs/browser-checks/multiple-tabs.md

@@ -62,7 +62,7 @@ Playwright Test will record videos for each of your tabs. You can find them in y
 
 ![Checkly Playwright Test UI](/docs/images/browser-checks/multiple-tabs-pwt-report.mp4)
 
-Playwright's Trace Viewer displays your tabs conveniently in a waterfall timeline to access all neccessary information:
+Playwright's Trace Viewer displays your tabs conveniently in a waterfall timeline to access all necessary information:
 ![mutiple tabs - trace viewer](/docs/images/browser-checks/multiple-tabs-trace-viewer.png)
 
 

site/content/docs/dashboards/authentication.md

@@ -30,4 +30,4 @@ After enabling password protection for your dashboard, you can continue to visit
 
 > Checkly account login is only available to Enterprise customers.
 
-If visiting via the `https://[dashboardId].checkly-dashboards.com` domain, you can also select "Login with Checkly" and signin with your existing Checkly account via any of the supported methods (i.e. Google, Github, Username and Password). This is an enterprise only feature.
+If visiting via the `https://[dashboardId].checkly-dashboards.com` domain, you can also select "Login with Checkly" and sign in with your existing Checkly account via any of the supported methods (i.e. Google, Github, Username and Password). This is an enterprise only feature.

site/content/docs/dashboards/custom-css.md

@@ -30,7 +30,7 @@ help you explore the possibilities you have available.
 
 ### Amazon Web Services style
 
-In this example we aim to replicate the brand style of [Amazon Web Sevices (AWS)](https://aws.amazon.com/). 
+In this example we aim to replicate the brand style of [Amazon Web Services (AWS)](https://aws.amazon.com/). 
 
 ![Dashboard with custom style to match AWS](/docs/images/dashboards-v2/aws_dashboard.png)
 

site/content/docs/integrations/prometheus-v2.md

@@ -95,7 +95,7 @@ In addition, the check metrics all contain the following labels:
 | `tags` | The tags of the check. |
 
 
-> You can set `key:value` tags in your checks and groups and they will be exported as custom labels in Prometheus. For instance the tag `env:production` will be exposed as a custome label `env="production"`. You can disable this by adding the query param `disableTagParsing=true`. Please note that Prometheus label names may only contain ASCII letters, numbers, as well as underscores (see the official [docs](https://prometheus.io/docs/concepts/data_model/)). Tags containing other characters in the label name will be sanitized.
+> You can set `key:value` tags in your checks and groups and they will be exported as custom labels in Prometheus. For instance the tag `env:production` will be exposed as a custom label `env="production"`. You can disable this by adding the query param `disableTagParsing=true`. Please note that Prometheus label names may only contain ASCII letters, numbers, as well as underscores (see the official [docs](https://prometheus.io/docs/concepts/data_model/)). Tags containing other characters in the label name will be sanitized.
 
 > The counter and histogram metrics are reset every hour. These resets can be handled in Prometheus by using the [rate](https://prometheus.io/docs/prometheus/latest/querying/functions/#rate) or [increase](https://prometheus.io/docs/prometheus/latest/querying/functions/#increase) functions.
 

site/content/docs/integrations/prometheus.md

@@ -33,7 +33,7 @@ Each `checkly_check` metric has the following labels:
 - `check_type`, either `api` or `browser`.
 - `tags`, this check's tags.
 
-> You can set `key:value` tags in your checks/groups and they will be exported as custom labels in Prometheus. For instance the tag `env:production` will be exposed as a custome label `env="production"`. You can disable this by adding the query param `disableTagParsing=true`.
+> You can set `key:value` tags in your checks/groups and they will be exported as custom labels in Prometheus. For instance the tag `env:production` will be exposed as a custom label `env="production"`. You can disable this by adding the query param `disableTagParsing=true`.
 
 The `checkly_private_location` metrics contain the labels:
 

site/content/docs/integrations/telegram.md

@@ -43,7 +43,7 @@ You can retrieve your own Telegram Chat ID by starting a chat with another bot.
 
 Alternatively, we can use the API token we generated with the bot earlier and query the Telegram API for our own Chat ID.
 
-1. In a browser enter the the following URL, `https://api.telegram.org/bot<API_TOKEN>/getUpdates`, of course replacing the `<API_TOKEN>` part with the actual token we obtained previously. Your browser should now display some JSON formatted data which looks like the following:
+1. In a browser enter the following URL, `https://api.telegram.org/bot<API_TOKEN>/getUpdates`, of course replacing the `<API_TOKEN>` part with the actual token we obtained previously. Your browser should now display some JSON formatted data which looks like the following:
 
    ![setup checkly telegram_bot step 5](/docs/images/integrations/telegram/telegram_step5.png)