From 821663abfc674c9f54683b07214cd97ac1881693 Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Mon, 28 Jul 2025 17:29:03 +0200
Subject: [PATCH] docs: fix small error in cron.mdx (#37176)

---
 apps/docs/content/guides/cron.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/guides/cron.mdx b/apps/docs/content/guides/cron.mdx
index 9d4d1a1b29e..45ff736f526 100644
--- a/apps/docs/content/guides/cron.mdx
+++ b/apps/docs/content/guides/cron.mdx
@@ -29,7 +29,7 @@ Under the hood, Supabase Cron uses the [`pg_cron`](https://github.com/citusdata/
 
 The extension creates a `cron` schema in your database and all Jobs are stored on the `cron.job` table. Every Job's run and its status is recorded on the `cron.job_run_details` table.
 
-The Supabase Dashboard provides and interface for you to schedule Jobs and monitor Job runs. You can also do the same with SQL.
+The Supabase Dashboard provides an interface for you to schedule Jobs and monitor Job runs. You can also do the same with SQL.
 
 ## Resources