diff --git a/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx b/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
index dec59a1c3..20a883228 100644
--- a/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
+++ b/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
@@ -82,4 +82,3 @@ Now that you have a basic status page, you can:
 
 - **[Status Page Reference](/reference/status-page)** - Complete configuration options
 - **[Understanding Uptime Values](/concept/uptime-calculation-and-values)** - How uptime is calculated
-- **[Status Page Examples](https://www.openstatus.dev/showcase)** - See status pages from other users
diff --git a/apps/server/src/routes/v1/index.ts b/apps/server/src/routes/v1/index.ts
index 602bbed65..b357ae1e4 100644
--- a/apps/server/src/routes/v1/index.ts
+++ b/apps/server/src/routes/v1/index.ts
@@ -48,7 +48,8 @@ if (process.env.NODE_ENV === "production") {
         email: "ping@openstatus.dev",
         url: "https://www.openstatus.dev",
       },
-      description: "This version is deprecated please use v2",
+      description:
+        "This version is deprecated please use v2 API: Read more about the new API in the documentation: https://docs.openstatus.dev/reference/api",
     },
     tags: [
       {
diff --git a/apps/web/src/app/(landing)/(redirect)/cal/page.tsx b/apps/web/src/app/(landing)/(redirect)/cal/page.tsx
index 424f080fa..ea4878a92 100644
--- a/apps/web/src/app/(landing)/(redirect)/cal/page.tsx
+++ b/apps/web/src/app/(landing)/(redirect)/cal/page.tsx
@@ -1,5 +1,5 @@
 import { redirect } from "next/navigation";
 
 export default function CalRedirect() {
-  return redirect("http://cal.com/team/openstatus/30min");
+  return redirect("https://cal.com/team/openstatus/30min");
 }
diff --git a/apps/web/src/content/cmdk.tsx b/apps/web/src/content/cmdk.tsx
index b46fa0419..123537a50 100644
--- a/apps/web/src/content/cmdk.tsx
+++ b/apps/web/src/content/cmdk.tsx
@@ -144,12 +144,12 @@ const CONFIG: ConfigSection[] = [
       {
         type: "item",
         label: "X",
-        href: "/x",
+        href: "/twitter",
       },
       {
         type: "item",
         label: "BlueSky",
-        href: "/bluesky",
+        href: "/bsky",
       },
       {
         type: "item",
diff --git a/apps/web/src/content/pages/blog/data-table-redesign.mdx b/apps/web/src/content/pages/blog/data-table-redesign.mdx
index 15817be3b..64cb42354 100644
--- a/apps/web/src/content/pages/blog/data-table-redesign.mdx
+++ b/apps/web/src/content/pages/blog/data-table-redesign.mdx
@@ -9,7 +9,7 @@ category: "engineering"
 
 We have release our react data-table based on [shadcn/ui](https://ui.shadcn.com/) a couple of months ago. While there's still in development, the PR [#11](https://github.com/openstatusHQ/data-table-filters/pull/11) marks an important second milestone after the initial release a few months ago. We now have a solid foundation to focus on the component API design and data fetching. Though you can create your own data table using only config files (for "sheet," "filters," and "columns"), you end up writing more code than you would like.
 
-If you want to try out the demo right away [logs.run/i](http://logs.run/i) or go to the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) GitHub repository - it's open source.
+If you want to try out the demo right away [logs.run/i](https://logs.run/i) or go to the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) GitHub repository - it's open source.
 
 ### Design improvements
 
@@ -27,7 +27,7 @@ A quick look of the before/after changes:
   alt="after"
 />
 
-We have been inspired by [Vercel](http://vercel.com/?ref=openstatus), [Datadog](http://datadoghq.com/?ref=openstatus) and [Axiom](http://axiom.co/?ref=openstatus) when it comes to design and features.
+We have been inspired by [Vercel](https://vercel.com/?ref=openstatus), [Datadog](https://datadoghq.com/?ref=openstatus) and [Axiom](https://axiom.co/?ref=openstatus) when it comes to design and features.
 
 ### Features
 
@@ -160,4 +160,4 @@ The `<Component />` API designs including the different `config` objects and `/a
 
 Thanks for the read and see you in a while! And don’t forget to [leave a star](https://github.com/openstatusHQ/openstatus) if you enjoyed it!
 
-Try the demo [logs.run/i](http://logs.run/i) or checkout the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) repository.
\ No newline at end of file
+Try the demo [logs.run/i](https://logs.run/i) or checkout the [data-table-filters](https://github.com/openstatusHQ/data-table-filters) repository.
\ No newline at end of file
diff --git a/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx b/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx
index 3c17f4c81..49c7f70fc 100644
--- a/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx
+++ b/apps/web/src/content/pages/blog/reflecting-1-year-building-openstatus.mdx
@@ -70,7 +70,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](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).
+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](https://uninbox.com?ref=openstatus.dev) or [documenso.com](https://documenso.com?ref=openstatus.dev) flourished at the same time and made it into the oss-friends list by [formbricks.com](https://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.**