From f99d323aa52885f1c77b6c83655b4a37bc200596 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Tue, 17 Dec 2024 11:24:59 +0000
Subject: [PATCH] Update website/docs/docs/deploy/job-scheduler.md

---
 website/docs/docs/deploy/job-scheduler.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/deploy/job-scheduler.md b/website/docs/docs/deploy/job-scheduler.md
index 38a98d2f92e..f3f5706e93f 100644
--- a/website/docs/docs/deploy/job-scheduler.md
+++ b/website/docs/docs/deploy/job-scheduler.md
@@ -11,7 +11,7 @@ The job scheduler is the backbone of running jobs in dbt Cloud, bringing power a
 The scheduler enables both cron-based and event-driven execution of dbt commands in the user’s data platform. Specifically, it handles:
 
 - Cron-based execution of dbt Cloud jobs that run on a predetermined cadence
-- Event-driven execution of dbt Cloud jobs that [run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion))
+- Event-driven execution of dbt Cloud jobs that run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion))
 - Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo ([merge jobs](/docs/deploy/merge-jobs))
 - Event-driven execution of dbt Cloud jobs triggered by API
 - Event-driven execution of dbt Cloud jobs manually triggered by a user to "Run Now"