Skip to content

Open-source status page, incident response and uptime monitoring

πŸ“ typo docs (#1118)

Thibault Le Ouay1b8fc26717e3
diff --git a/README.md b/README.md
index 3390c6190..f90397099 100644
--- a/README.md
+++ b/README.md
@@ -75,8 +75,8 @@ Made with [Contrib.rocks](https://contrib.rocks)
- [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/)
diff --git a/apps/docs/src/content/docs/alerting/overview.mdx b/apps/docs/src/content/docs/alerting/overview.mdx
index 5c92c295c..2de0b4157 100644
--- a/apps/docs/src/content/docs/alerting/overview.mdx
+++ b/apps/docs/src/content/docs/alerting/overview.mdx
@@ -1,5 +1,6 @@
---
title: Overview
+description: "Discover the different notification channels available in OpenStatus"
---
import { Card } from '@astrojs/starlight/components';
import { CardGrid } from '@astrojs/starlight/components';
@@ -28,4 +29,4 @@ By default we don't send any notification. You need to connect your monitor to a
<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>
\ No newline at end of file
+</CardGrid>
diff --git a/apps/docs/src/content/docs/alerting/providers/discord.mdx b/apps/docs/src/content/docs/alerting/providers/discord.mdx
index fddcec40e..5cc6c0c6d 100644
--- a/apps/docs/src/content/docs/alerting/providers/discord.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/discord.mdx
@@ -1,5 +1,6 @@
---
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
diff --git a/apps/docs/src/content/docs/alerting/providers/email.mdx b/apps/docs/src/content/docs/alerting/providers/email.mdx
index e23dd4643..62734712a 100644
--- a/apps/docs/src/content/docs/alerting/providers/email.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/email.mdx
@@ -1,5 +1,7 @@
---
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.
diff --git a/apps/docs/src/content/docs/alerting/providers/pagerduty.mdx b/apps/docs/src/content/docs/alerting/providers/pagerduty.mdx
index 45faf78fb..c28b7d3c5 100644
--- a/apps/docs/src/content/docs/alerting/providers/pagerduty.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/pagerduty.mdx
@@ -1,5 +1,7 @@
---
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';
@@ -36,4 +38,4 @@ Select the service you want to use to send notifications. You can create a new s
You are now connected to PagerDuty. Give your integration a name and save it.
-You will receive some notifications if we detect an incident
\ No newline at end of file
+You will receive some notifications if we detect an incident
diff --git a/apps/docs/src/content/docs/alerting/providers/phone-call.mdx b/apps/docs/src/content/docs/alerting/providers/phone-call.mdx
index 131de504e..4b6936f59 100644
--- a/apps/docs/src/content/docs/alerting/providers/phone-call.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/phone-call.mdx
@@ -1,5 +1,7 @@
---
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.
diff --git a/apps/docs/src/content/docs/alerting/providers/slack.mdx b/apps/docs/src/content/docs/alerting/providers/slack.mdx
index 781806254..e1cb206a3 100644
--- a/apps/docs/src/content/docs/alerting/providers/slack.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/slack.mdx
@@ -1,5 +1,7 @@
---
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
diff --git a/apps/docs/src/content/docs/alerting/providers/sms.mdx b/apps/docs/src/content/docs/alerting/providers/sms.mdx
index 31d935433..50a91fded 100644
--- a/apps/docs/src/content/docs/alerting/providers/sms.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/sms.mdx
@@ -1,5 +1,7 @@
---
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
diff --git a/apps/docs/src/content/docs/alerting/providers/telegram.mdx b/apps/docs/src/content/docs/alerting/providers/telegram.mdx
index d1f332b51..382598648 100644
--- a/apps/docs/src/content/docs/alerting/providers/telegram.mdx
+++ b/apps/docs/src/content/docs/alerting/providers/telegram.mdx
@@ -1,5 +1,7 @@
---
title: Telegram
+description: "How to set up Telegram notifications in OpenStatus to get alerts when your synthetic check fail"
+
---
🚧 Coming soon 🚧
diff --git a/apps/docs/src/content/docs/cli/commands/monitors.mdx b/apps/docs/src/content/docs/cli/commands/monitors.mdx
index c83153b6a..71b903bc7 100644
--- a/apps/docs/src/content/docs/cli/commands/monitors.mdx
+++ b/apps/docs/src/content/docs/cli/commands/monitors.mdx
@@ -1,5 +1,6 @@
---
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.
@@ -32,4 +33,3 @@ You can trigger a monitor using the following command.
```bash
openstatus monitors trigger <monitor-id>
```
-
diff --git a/apps/docs/src/content/docs/cli/commands/run.mdx b/apps/docs/src/content/docs/cli/commands/run.mdx
index dee84ace1..63a4c6f9a 100644
--- a/apps/docs/src/content/docs/cli/commands/run.mdx
+++ b/apps/docs/src/content/docs/cli/commands/run.mdx
@@ -1,5 +1,6 @@
---
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.
@@ -21,4 +22,4 @@ openstatus run
### Options
-- `--config` - Path to the config file. Default is `config.openstatus.yaml`.
\ No newline at end of file
+- `--config` - Path to the config file. Default is `config.openstatus.yaml`.
diff --git a/apps/docs/src/content/docs/cli/commands/whoami.mdx b/apps/docs/src/content/docs/cli/commands/whoami.mdx
index 1cb86bbc1..a85843ac5 100644
--- a/apps/docs/src/content/docs/cli/commands/whoami.mdx
+++ b/apps/docs/src/content/docs/cli/commands/whoami.mdx
@@ -1,5 +1,6 @@
---
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.
\ No newline at end of file
+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.
diff --git a/apps/docs/src/content/docs/cli/getting-started.mdx b/apps/docs/src/content/docs/cli/getting-started.mdx
index dac0bd1c6..4b33dce3c 100644
--- a/apps/docs/src/content/docs/cli/getting-started.mdx
+++ b/apps/docs/src/content/docs/cli/getting-started.mdx
@@ -1,5 +1,6 @@
---
title: Getting Started
+description: "Get started with OpenStatus CLI and start triggering your synthetic checks from your terminal"
---
import { Image } from 'astro:assets';
@@ -49,4 +50,4 @@ or you can set the `--access-token` option in the CLI command.
```bash
openstatus [COMMAND] --access-token your-api-token
-```
\ No newline at end of file
+```
diff --git a/apps/docs/src/content/docs/incident/incident-detail.mdx b/apps/docs/src/content/docs/incident/incident-detail.mdx
index 365e36ddd..32af80e44 100644
--- a/apps/docs/src/content/docs/incident/incident-detail.mdx
+++ b/apps/docs/src/content/docs/incident/incident-detail.mdx
@@ -1,5 +1,6 @@
---
title: Incident Detail
+description: "Discover the incident details in OpenStatus"
order: 2
---
diff --git a/apps/docs/src/content/docs/incident/overview.mdx b/apps/docs/src/content/docs/incident/overview.mdx
index 3c29165d8..e622083e5 100644
--- a/apps/docs/src/content/docs/incident/overview.mdx
+++ b/apps/docs/src/content/docs/incident/overview.mdx
@@ -1,6 +1,6 @@
---
title: Overview
-description: "How incident are created, how to acknowledge, and resolve them"
+description: "Discover what is an incident in OpenStatus"
---
diff --git a/apps/docs/src/content/docs/incident/work-with-incident.mdx b/apps/docs/src/content/docs/incident/work-with-incident.mdx
index 5d436e0f0..0f6c29171 100644
--- a/apps/docs/src/content/docs/incident/work-with-incident.mdx
+++ b/apps/docs/src/content/docs/incident/work-with-incident.mdx
@@ -1,5 +1,6 @@
---
title: Work with Incidents
+description: "How to acknowledge and resolve incidents in OpenStatus"
---
An incident can have the following states:
diff --git a/apps/docs/src/content/docs/monitoring/clone-monitor.mdx b/apps/docs/src/content/docs/monitoring/clone-monitor.mdx
index 362f033bd..19c1a10b5 100644
--- a/apps/docs/src/content/docs/monitoring/clone-monitor.mdx
+++ b/apps/docs/src/content/docs/monitoring/clone-monitor.mdx
@@ -1,6 +1,6 @@
---
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';
@@ -15,4 +15,3 @@ By default, the cloned monitor will be in the **inactive** state to allow you to
src={monitorDetail}
alt="Charts with status code and response time"
/>
-
diff --git a/apps/docs/src/content/docs/monitoring/create-monitor.mdx b/apps/docs/src/content/docs/monitoring/create-monitor.mdx
index 953e7ccc0..b2af51e74 100644
--- a/apps/docs/src/content/docs/monitoring/create-monitor.mdx
+++ b/apps/docs/src/content/docs/monitoring/create-monitor.mdx
@@ -1,6 +1,6 @@
---
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';
diff --git a/apps/docs/src/content/docs/monitoring/customization/assertions.mdx b/apps/docs/src/content/docs/monitoring/customization/assertions.mdx
index 2186e935d..f1db24b74 100644
--- a/apps/docs/src/content/docs/monitoring/customization/assertions.mdx
+++ b/apps/docs/src/content/docs/monitoring/customization/assertions.mdx
@@ -1,6 +1,6 @@
---
title: Assertions
-description: "How to monitor your HTTP services with OpenStatus.dev"
+description: "How to set up assertions for your synthetic checks in OpenStatus"
---
@@ -38,4 +38,3 @@ Supports `Equal`, `Not equal`, `Contains`, `Does not Contain`, `Empty`, `Not emp
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.
-
diff --git a/apps/docs/src/content/docs/monitoring/customization/frequency.mdx b/apps/docs/src/content/docs/monitoring/customization/frequency.mdx
index 3136dd3b4..fefbc527d 100644
--- a/apps/docs/src/content/docs/monitoring/customization/frequency.mdx
+++ b/apps/docs/src/content/docs/monitoring/customization/frequency.mdx
@@ -1,6 +1,6 @@
---
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.
@@ -16,4 +16,4 @@ We support the following frequencies:
- Every 5 minutes
- Every 10 minutes
- Every 30 minutes
-- Every 1 hour
\ No newline at end of file
+- Every 1 hour
diff --git a/apps/docs/src/content/docs/monitoring/customization/notification.mdx b/apps/docs/src/content/docs/monitoring/customization/notification.mdx
index c4e1f2355..5cf94517f 100644
--- a/apps/docs/src/content/docs/monitoring/customization/notification.mdx
+++ b/apps/docs/src/content/docs/monitoring/customization/notification.mdx
@@ -1,5 +1,6 @@
---
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';
@@ -22,4 +23,4 @@ You need to create a notification channel before connecting your monitor to it.
<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>
\ No newline at end of file
+</Aside>
diff --git a/apps/docs/src/content/docs/monitoring/customization/regions.mdx b/apps/docs/src/content/docs/monitoring/customization/regions.mdx
index 47ff086cc..33e2bee33 100644
--- a/apps/docs/src/content/docs/monitoring/customization/regions.mdx
+++ b/apps/docs/src/content/docs/monitoring/customization/regions.mdx
@@ -1,6 +1,6 @@
---
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.
@@ -57,4 +57,4 @@ South America
Oceania
-- Sydney, Australia πŸ‡¦πŸ‡Ί (free)
\ No newline at end of file
+- Sydney, Australia πŸ‡¦πŸ‡Ί (free)
diff --git a/apps/docs/src/content/docs/monitoring/customization/timing.mdx b/apps/docs/src/content/docs/monitoring/customization/timing.mdx
index 4d4de8a43..7a4f3ee1e 100644
--- a/apps/docs/src/content/docs/monitoring/customization/timing.mdx
+++ b/apps/docs/src/content/docs/monitoring/customization/timing.mdx
@@ -1,10 +1,10 @@
---
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 &rarr; Settings &rarr; Timing & Assertions_.
\ No newline at end of file
+To change assertions for your monitors: _Select a monitor &rarr; Settings &rarr; Timing & Assertions_.
diff --git a/apps/docs/src/content/docs/monitoring/group-monitor-tag.mdx b/apps/docs/src/content/docs/monitoring/group-monitor-tag.mdx
index 950fa16c8..7019fcfc7 100644
--- a/apps/docs/src/content/docs/monitoring/group-monitor-tag.mdx
+++ b/apps/docs/src/content/docs/monitoring/group-monitor-tag.mdx
@@ -1,5 +1,6 @@
---
title: How to group your monitors
+description: "How to group your monitors in OpenStatus to manage them more efficiently"
---
import { Image } from 'astro:assets';
diff --git a/apps/docs/src/content/docs/monitoring/monitor-data-collected.mdx b/apps/docs/src/content/docs/monitoring/monitor-data-collected.mdx
index 9971f4b85..919a067e2 100644
--- a/apps/docs/src/content/docs/monitoring/monitor-data-collected.mdx
+++ b/apps/docs/src/content/docs/monitoring/monitor-data-collected.mdx
@@ -1,6 +1,6 @@
---
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';
diff --git a/apps/docs/src/content/docs/monitoring/overview.mdx b/apps/docs/src/content/docs/monitoring/overview.mdx
index 7b34b1dec..360d5a0e3 100644
--- a/apps/docs/src/content/docs/monitoring/overview.mdx
+++ b/apps/docs/src/content/docs/monitoring/overview.mdx
@@ -28,11 +28,10 @@ We will make a request to your endpoint and record the results.
<CardGrid>
<LinkCard
title="HTTP Monitor"
- href="/type/http"
+ href="/monitoring/type/http"
/>
<LinkCard
title="TCP Monitor"
- href="/type/tcp"
+ href="/monitoring/type/tcp"
/>
</CardGrid>
-
diff --git a/apps/docs/src/content/docs/monitoring/type/http.mdx b/apps/docs/src/content/docs/monitoring/type/http.mdx
index 4b8b4ff73..f1ba9bddf 100644
--- a/apps/docs/src/content/docs/monitoring/type/http.mdx
+++ b/apps/docs/src/content/docs/monitoring/type/http.mdx
@@ -1,6 +1,6 @@
---
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';
diff --git a/apps/docs/src/content/docs/monitoring/type/tcp.mdx b/apps/docs/src/content/docs/monitoring/type/tcp.mdx
index 5ffeb3f12..4aa15bfcc 100644
--- a/apps/docs/src/content/docs/monitoring/type/tcp.mdx
+++ b/apps/docs/src/content/docs/monitoring/type/tcp.mdx
@@ -1,6 +1,6 @@
---
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';
diff --git a/apps/docs/src/content/docs/status-page/advanced/badge.mdx b/apps/docs/src/content/docs/status-page/advanced/badge.mdx
index fa251ffeb..1e51ab413 100644
--- a/apps/docs/src/content/docs/status-page/advanced/badge.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/badge.mdx
@@ -1,5 +1,6 @@
---
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
diff --git a/apps/docs/src/content/docs/status-page/advanced/custom-domain.mdx b/apps/docs/src/content/docs/status-page/advanced/custom-domain.mdx
index 7b7462bb8..04226b6d7 100644
--- a/apps/docs/src/content/docs/status-page/advanced/custom-domain.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/custom-domain.mdx
@@ -1,5 +1,6 @@
---
title: Custom Domain
+description: "How to connect a custom domain to your status page in OpenStatus"
---
import { Aside } from '@astrojs/starlight/components';
diff --git a/apps/docs/src/content/docs/status-page/advanced/description.mdx b/apps/docs/src/content/docs/status-page/advanced/description.mdx
index 3b40b3300..bea365587 100644
--- a/apps/docs/src/content/docs/status-page/advanced/description.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/description.mdx
@@ -1,5 +1,6 @@
---
title: Description
+description: "How to set a custom description for your status page in OpenStatus"
---
import { Image } from 'astro:assets';
diff --git a/apps/docs/src/content/docs/status-page/advanced/icon.mdx b/apps/docs/src/content/docs/status-page/advanced/icon.mdx
index 87ac6f70a..deb82b0f8 100644
--- a/apps/docs/src/content/docs/status-page/advanced/icon.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/icon.mdx
@@ -1,5 +1,6 @@
---
title: Icon
+description: "How to set a custom icon for your status page in OpenStatus"
---
import { Image } from 'astro:assets';
diff --git a/apps/docs/src/content/docs/status-page/advanced/monitors.mdx b/apps/docs/src/content/docs/status-page/advanced/monitors.mdx
index b01b8a1fd..76b16de16 100644
--- a/apps/docs/src/content/docs/status-page/advanced/monitors.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/monitors.mdx
@@ -1,5 +1,6 @@
---
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.
diff --git a/apps/docs/src/content/docs/status-page/advanced/password.mdx b/apps/docs/src/content/docs/status-page/advanced/password.mdx
index 5b2b98f5c..547ee1d2f 100644
--- a/apps/docs/src/content/docs/status-page/advanced/password.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/password.mdx
@@ -1,5 +1,6 @@
---
title: Password protection
+description: "How to password protect your status page in OpenStatus"
---
import { Aside } from '@astrojs/starlight/components';
diff --git a/apps/docs/src/content/docs/status-page/advanced/widget.mdx b/apps/docs/src/content/docs/status-page/advanced/widget.mdx
index fa1cad9d3..670b5a1e0 100644
--- a/apps/docs/src/content/docs/status-page/advanced/widget.mdx
+++ b/apps/docs/src/content/docs/status-page/advanced/widget.mdx
@@ -1,5 +1,6 @@
---
title: Public Status Widget
+description: "How to embed the public status widget in your React application"
---
import { Aside } from '@astrojs/starlight/components';
@@ -14,7 +15,7 @@ curl https://api.openstatus.dev/public/status/:slug
<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:
diff --git a/apps/docs/src/content/docs/status-page/create-status-page.mdx b/apps/docs/src/content/docs/status-page/create-status-page.mdx
index 0dfe004b2..be8998519 100644
--- a/apps/docs/src/content/docs/status-page/create-status-page.mdx
+++ b/apps/docs/src/content/docs/status-page/create-status-page.mdx
@@ -1,5 +1,6 @@
---
title: How to create a status page?
+description: "How to create a status page in OpenStatus"
---
import { Image } from 'astro:assets';
diff --git a/apps/docs/src/content/docs/status-page/overview.mdx b/apps/docs/src/content/docs/status-page/overview.mdx
index 70ab1ea72..03cbc7f2b 100644
--- a/apps/docs/src/content/docs/status-page/overview.mdx
+++ b/apps/docs/src/content/docs/status-page/overview.mdx
@@ -1,5 +1,6 @@
---
title: Status page
+description: "Discover what is a status page in OpenStatus"
---
import { Image } from 'astro:assets';
@@ -18,7 +19,7 @@ A status page is a public page that displays the status and performance of your
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).
diff --git a/apps/docs/src/content/docs/tools/terraform.mdx b/apps/docs/src/content/docs/tools/terraform.mdx
index 64888cb4d..658f60601 100644
--- a/apps/docs/src/content/docs/tools/terraform.mdx
+++ b/apps/docs/src/content/docs/tools/terraform.mdx
@@ -1,7 +1,7 @@
---
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
diff --git a/apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx b/apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
index 2c4546463..d8da09080 100644
--- a/apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
+++ b/apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
@@ -46,7 +46,7 @@ This initial idea served as the seed from which our entire project would grow.
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.
@@ -72,7 +72,7 @@ However, we weren't power users of these platforms. Our understanding of the eco
### 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.**
@@ -109,7 +109,7 @@ Our status pages served as an excellent marketing tool. Each time a user publish
### 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.
@@ -208,4 +208,4 @@ Stay tuned for more updates as we continue to improve OpenStatus!
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!
\ No newline at end of file
+Or create an account on [Openstatus](https://www.openstatus.dev/app/login) and start monitoring your services today!
diff --git a/apps/web/src/content/posts/secure-api-with-unkey.mdx b/apps/web/src/content/posts/secure-api-with-unkey.mdx
index 778b794d2..c5d51acd4 100644
--- a/apps/web/src/content/posts/secure-api-with-unkey.mdx
+++ b/apps/web/src/content/posts/secure-api-with-unkey.mdx
@@ -66,7 +66,7 @@ export async function revoke(keyId: string) {
```
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.
@@ -203,7 +203,7 @@ Unkey increases our velocity and **helps us focus on what's relevant** to the
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.
diff --git a/apps/web/src/content/posts/the-first-48-hours.mdx b/apps/web/src/content/posts/the-first-48-hours.mdx
index ddde86798..bebf22571 100644
--- a/apps/web/src/content/posts/the-first-48-hours.mdx
+++ b/apps/web/src/content/posts/the-first-48-hours.mdx
@@ -29,7 +29,7 @@ issues and took action.
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