📝 typo docs (#1118)

README.md

···
 - [Next.js](https://nextjs.org/)
 - [Tailwind CSS](https://tailwindcss.com/)
 - [shadcn/ui](https://ui.shadcn.com/)
-- [tinybird](http://tinybird.co/?ref=openstatus.dev)
-- [turso](http://turso.tech/)
+- [tinybird](https://tinybird.co/?ref=openstatus.dev)
+- [turso](https://turso.tech/)
 - [drizzle](https://orm.drizzle.team/)
 - [Resend](https://resend.com/)
 

apps/docs/src/content/docs/alerting/overview.mdx

···
 ---
 title: Overview
+description: "Discover the different notification channels available in OpenStatus"
 ---
 import { Card } from '@astrojs/starlight/components';
 import { CardGrid } from '@astrojs/starlight/components';
···
   <LinkCard title="Pagerduty 📟" href="/alerting/providers/pagerduty" description="Receive a pagerduty notification"/ >
   <LinkCard title="Phone 📞" href="/alerting/providers/phone-call" description="Get called on your phone" />
   <LinkCard title="Telegram 📡" href="/alerting/providers/telegram" description="Get notified on Telegram" />
-</CardGrid>
+</CardGrid>

apps/docs/src/content/docs/alerting/providers/discord.mdx

···
 ---
 title: Discord
+description: "How to set up Discord notifications in OpenStatus to get alerts when your synthetic check fail"
 ---
 
 When a monitor is down you can set up a webhook to send a message to a Discord

apps/docs/src/content/docs/alerting/providers/email.mdx

···
 ---
 title: Email
+description: "How to set up Email notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 
 When we create an incident we send an email to the email provided.

apps/docs/src/content/docs/alerting/providers/pagerduty.mdx

···
 ---
 title: PagerDuty
+description: "How to set up PagerDuty notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 import { Image} from 'astro:assets';
 import PagerDuty1 from '../../../../assets/notification/pagerduty/pagerduty-1.png';
···
 
 You are now connected to PagerDuty.  Give your integration a name and save it.
 
-You will receive some notifications if we detect an incident
+You will receive some notifications if we detect an incident

apps/docs/src/content/docs/alerting/providers/phone-call.mdx

···
 ---
 title: Phone call
+description: "How to set up phone call notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 
 Receive a phone call when your monitor is down.

apps/docs/src/content/docs/alerting/providers/slack.mdx

···
 ---
 title: Slack
+description: "How to set up Slack notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 
 When a monitor is down, a message can be sent to a Slack channel. To enable this

apps/docs/src/content/docs/alerting/providers/sms.mdx

···
 ---
 title: SMS
+description: "How to set up SMS notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 
 When you subscribe to a paid plan you can receive SMS notifications when your

apps/docs/src/content/docs/alerting/providers/telegram.mdx

···
 ---
 title: Telegram
+description: "How to set up Telegram notifications in OpenStatus to get alerts when your synthetic check fail"
+
 ---
 
 🚧 Coming soon 🚧

apps/docs/src/content/docs/cli/commands/monitors.mdx

···
 ---
 title: Monitors
+description: "Manage your monitors in OpenStatus from the command line"
 ---
 
 The monitors command is used to manage your monitors. You trigger, view and list your monitors using this command.
···
 ```bash
 openstatus monitors trigger <monitor-id>
 ```
-

apps/docs/src/content/docs/cli/commands/run.mdx

···
 ---
 title: Run
+description: "How to run a list of synthetic checks in OpenStatus from the command line"
 ---
 
 This command is used to run a list of synthetic check.
···
 
 ### Options
 
-- `--config` - Path to the config file. Default is `config.openstatus.yaml`.
+- `--config` - Path to the config file. Default is `config.openstatus.yaml`.

apps/docs/src/content/docs/cli/commands/whoami.mdx

···
 ---
 title: Whoami
+description: "How to check the currently authenticated user in OpenStatus with the whoami command"
 ---
 
-The `whoami` command is used to display the currently authenticated user. This command is useful to check if you are logged in and to see the workspace details.
+The `whoami` command is used to display the currently authenticated user. This command is useful to check if you are logged in and to see the workspace details.

apps/docs/src/content/docs/cli/getting-started.mdx

···
 ---
 title: Getting Started
+description: "Get started with OpenStatus CLI and start triggering your synthetic checks from your terminal"
 ---
 
 import { Image } from 'astro:assets';
···
 
 ```bash
 openstatus [COMMAND] --access-token your-api-token
-```
+```

apps/docs/src/content/docs/incident/incident-detail.mdx

···
 ---
 title: Incident Detail
+description: "Discover the incident details in OpenStatus"
 order: 2
 ---
 

apps/docs/src/content/docs/incident/overview.mdx

···
 ---
 title: Overview
-description: "How incident are created, how to acknowledge, and resolve them"
+description: "Discover what is an incident in OpenStatus"
 ---
 
 

apps/docs/src/content/docs/incident/work-with-incident.mdx

···
 ---
 title: Work with Incidents
+description: "How to acknowledge and resolve incidents in OpenStatus"
 ---
 
 An incident can have the following states:

apps/docs/src/content/docs/monitoring/clone-monitor.mdx

···
 ---
 title: How to clone a monitor?
-description: "How to clone your first monitor with OpenStatus.dev"
+description: "How to clone a monitor with OpenStatus"
 ---
 
 import { Image } from 'astro:assets';
···
     src={monitorDetail}
     alt="Charts with status code and response time"
   />
-

apps/docs/src/content/docs/monitoring/create-monitor.mdx

···
 ---
 title: How to create a monitor?
-description: "How to create your first monitor with OpenStatus.dev"
+description: "How to create your first monitor with OpenStatus"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/monitoring/customization/assertions.mdx

···
 ---
 title: Assertions
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to set up assertions for your synthetic checks in OpenStatus"
 ---
 
 
···
 Define the **body string** you want to check for.
 
 Supports `Equal`, `Not equal`, `Contains`, `Does not Contain`, `Empty`, `Not empty`, `Greater than`, `Less than`, `Greater than or equal`, `Less than or equal` assertions.
-

apps/docs/src/content/docs/monitoring/customization/frequency.mdx

···
 ---
 title: Frequency
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to change the frequency of your synthetic checks in OpenStatus"
 ---
 
 By default, OpenStatus.dev will check your service every 30 minutes.
···
 - Every 5 minutes
 - Every 10 minutes
 - Every 30 minutes
-- Every 1 hour
+- Every 1 hour

apps/docs/src/content/docs/monitoring/customization/notification.mdx

···
 ---
 title: Notifications
+description: "How to set up notifications for your synthetic checks in OpenStatus"
 ---
 import { Image } from 'astro:assets';
 import { Aside} from '@astrojs/starlight/components';
···
 
 <Aside>
 By default your monitor won't send any notification on failure. You can enable notifications for your monitor by connecting it to a notification channel.
-</Aside>
+</Aside>

apps/docs/src/content/docs/monitoring/customization/regions.mdx

···
 ---
 title: Regions
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to change the regions for your synthetic checks in OpenStatus"
 ---
 
 For free users, OpenStatus will monitor your service from six location, one on every continent. For paid users, you can choose from multiple locations around the world to monitor your service.
···
 
 Oceania
 
-- Sydney, Australia 🇦🇺 (free)
+- Sydney, Australia 🇦🇺 (free)

apps/docs/src/content/docs/monitoring/customization/timing.mdx

···
 ---
 title: Timing
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to set up timing threshold for your synthetic checks in OpenStatus"
 ---
 
 By default, OpenStatus will timeout after `45s` but you can set a custom timeout (max. `45s`).
 
 You can also set a custom degraded threshold. If the response time is higher than the degraded threshold, the status will be set to `Degraded` and we will send a notification.
 
-To change assertions for your monitors: _Select a monitor → Settings → Timing & Assertions_.
+To change assertions for your monitors: _Select a monitor → Settings → Timing & Assertions_.

apps/docs/src/content/docs/monitoring/group-monitor-tag.mdx

···
 ---
 title: How to group your monitors
+description: "How to group your monitors in OpenStatus to manage them more efficiently"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/monitoring/monitor-data-collected.mdx

···
 ---
 title: Monitor Data Points
-description: "Monitor metrics are the data points that are collected by the monitor during the check."
+description: "Monitor metrics are the data points that are collected by the monitor during the check in OpenStatus."
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/monitoring/overview.mdx

···
 <CardGrid>
     <LinkCard
         title="HTTP Monitor"
-        href="/type/http"
+        href="/monitoring/type/http"
     />
     <LinkCard
         title="TCP Monitor"
-        href="/type/tcp"
+        href="/monitoring/type/tcp"
     />
 </CardGrid>
-

apps/docs/src/content/docs/monitoring/type/http.mdx

···
 ---
 title: HTTP
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to monitor your HTTP services with OpenStatus"
 ---
 import { Image } from 'astro:assets';
 

apps/docs/src/content/docs/monitoring/type/tcp.mdx

···
 ---
 title: TCP
-description: "How to monitor your TCP services with OpenStatus.dev"
+description: "How to monitor your TCP services with OpenStatus"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/status-page/advanced/badge.mdx

···
 ---
 title: Badge
+description: "How to embed the status page badge on your website or GitHub README"
 ---
 
 You can embed the status page badge on your website or GitHub README to show the

apps/docs/src/content/docs/status-page/advanced/custom-domain.mdx

···
 ---
 title: Custom Domain
+description: "How to connect a custom domain to your status page in OpenStatus"
 ---
 
 import { Aside } from '@astrojs/starlight/components';

apps/docs/src/content/docs/status-page/advanced/description.mdx

···
 ---
 title: Description
+description: "How to set a custom description for your status page in OpenStatus"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/status-page/advanced/icon.mdx

···
 ---
 title: Icon
+description: "How to set a custom icon for your status page in OpenStatus"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/status-page/advanced/monitors.mdx

···
 ---
 title: Monitors
+description: "How to connect your monitors for your status page in OpenStatus"
 ---
 
 Connect your created monitors to your status page to display the current status of your services.

apps/docs/src/content/docs/status-page/advanced/password.mdx

···
 ---
 title: Password protection
+description: "How to password protect your status page in OpenStatus"
 ---
 
 import { Aside } from '@astrojs/starlight/components';

apps/docs/src/content/docs/status-page/advanced/widget.mdx

···
 ---
 title: Public Status Widget
+description: "How to embed the public status widget in your React application"
 ---
 import { Aside } from '@astrojs/starlight/components';
 
···
 <Aside>
   We have released an `@openstatus/react` npm package that allows you to easily
   integrate the pre-typed status into your React projects or use the default
-  widget. Read more [here](/packages/react).
+  widget. Read more [here](/tools/react).
 </Aside>
 
 The response is a JSON object with the following structure:

apps/docs/src/content/docs/status-page/create-status-page.mdx

···
 ---
 title: How to create a status page?
+description: "How to create a status page in OpenStatus"
 ---
 
 import { Image } from 'astro:assets';

apps/docs/src/content/docs/status-page/overview.mdx

···
 ---
 title: Status page
+description: "Discover what is a status page in OpenStatus"
 ---
 import { Image } from 'astro:assets';
 
···
 services. It shows the current status of your services and the history of
 incidents.
 
-You can create a status page with OpenStatus.dev and display the status of your synthetic checks.
+You can create a status page with OpenStatus and display the status of your synthetic checks.
 
 You can see our own status page at [https://status.openstatus.dev](https://status.openstatus.dev).
 

apps/docs/src/content/docs/tools/terraform.mdx

···
 ---
 title: Terraform Provider
 description:
-  "Use OpenStatus Terraform provider to manage your monitors and  status page."
+  "Use OpenStatus Terraform provider to manage your monitors and status page."
 ---
 
 Here you can find the official OpenStatus Terraform provider. This provider

apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx

···
  As we progressed, we talked to a lot of users, VC. We explored various directions, sometimes feeling a bit lost in the sea of possibilities:
 
 1. **Serverless monitoring**: Given that most of our users were Vercel customers, we considered specializing in this area.
-2. **Incident management**: Inspired by products like [incident.io](http://incident.io/), we contemplated starting with status pages and expanding into incident management. However, we realized this would target larger, Series B+ startups, involving longer sales processes and diverging from our core audience of small teams from bootstrapped businesses or Series A startups.
+2. **Incident management**: Inspired by products like [incident.io](https://incident.io/), we contemplated starting with status pages and expanding into incident management. However, we realized this would target larger, Series B+ startups, involving longer sales processes and diverging from our core audience of small teams from bootstrapped businesses or Series A startups.
 3. **AI-enhanced alerting systems**: We briefly considered focusing on our product's alerting capabilities and incorporating AI for smart alerts. In retrospect, this seemed more like an attempt to capitalize on the AI trend rather than a strategic decision.
 4. **Real User Monitoring (RUM)**: We implemented this feature, but after discussions, we recognized the need to focus on our core strength: synthetic monitoring.
 
···
 
 ### Riding the OSS train
 
-We started at the right time where lots of Open-Source Software companies like our friends at [papermark.io](http://papermark.io?ref=openstatus.dev), [uninbox.com](http://uninbox.com?ref=openstatus.dev) or [documenso.com](http://documenso.com?ref=openstatus.dev) flourished at the same time and made it into the oss-friends list by [formbricks.com](http://formbricks.com?ref=openstatus.dev).
+We started at the right time where lots of Open-Source Software companies like our friends at [papermark.io](https://papermark.io?ref=openstatus.dev), [uninbox.com](http://uninbox.com?ref=openstatus.dev) or [documenso.com](http://documenso.com?ref=openstatus.dev) flourished at the same time and made it into the oss-friends list by [formbricks.com](http://formbricks.com?ref=openstatus.dev).
 
 **Sometimes, you have to be lucky! We were fortunate to be in the right place at the right time, gaining the visibility that helped set us apart.**
 
···
 
 ### Tools and Components
 
-Additionally, creating tools and components people love is a great way to draw attention and leverage SEO: [time.openstatus.dev](http://time.openstatus.dev) - a shadcn time picker drives 3k visitors per month organically. Same goal is with [data-table.openstatus.dev](http://data-table.openstatus.dev) - an extensive data-table for your realtime data.
+Additionally, creating tools and components people love is a great way to draw attention and leverage SEO: [time.openstatus.dev](https://time.openstatus.dev) - a shadcn time picker drives 3k visitors per month organically. Same goal is with [data-table.openstatus.dev](https://data-table.openstatus.dev) - an extensive data-table for your realtime data.
 
 > We want to show users we are here to build with and for you. And of course in the open.
 
···
 To infinity and beyond  🚀
 
 Want to join us on this journey? [Star us on GitHub](https://www.github.com/openstatusHQ/openstatus)! 🌟
-Or create an account on [Openstatus](https://www.openstatus.dev/app/login) and start monitoring your services today!
+Or create an account on [Openstatus](https://www.openstatus.dev/app/login) and start monitoring your services today!

apps/web/src/content/posts/secure-api-with-unkey.mdx

···
 ```
 
 To test key creation, you can simply go to the
-[Unkey Dashboard](http://unkey.dev/app) and create an API key manually instead
+[Unkey Dashboard](https://unkey.dev/app) and create an API key manually instead
 of using the SDK. The SDK is useful once you want your users to create API keys
 programmatically.
 
···
 user, not the infrastructure behind it. We also get **key verification
 insights** out of the box and can target specific users based on their usage.
 
-[@chronark\_](http://twitter.com/chronark_) has recently published an
+[@chronark\_](https://twitter.com/chronark_) has recently published an
 [`@unkey/hono`](https://docs.unkey.dev/libraries/ts/hono) package that uses a
 similar implementation under the hood, reducing some boilerplate code for you.
 Highly recommend checking it out if you are using Hono.js.

apps/web/src/content/posts/the-first-48-hours.mdx

···
 We conducted a DDOS attack on Vercel's firewalls from Upstash servers because we
 where pining every single vercel region for every monitor (18 \* 315 = 5.670)
 more or less at once. Before considering the removal of
-[QStash](http://upstash.com/qstash?ref=openstatus), we implemented a hotfix to
+[QStash](https://upstash.com/qstash?ref=openstatus), we implemented a hotfix to
 introduce random delays of 0 to 180 seconds between each ping. This prevented us
 from overwhelming Vercel with simultaneous requests, significantly reducing the
 number of retries on QStash. As a result of these measures, we now have a