From f104df6e0f456a59c6934a5fa873a8dbc92da068 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Wed, 23 Oct 2024 17:35:24 +0100
Subject: [PATCH] Update website/docs/docs/deploy/job-commands.md

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

diff --git a/website/docs/docs/deploy/job-commands.md b/website/docs/docs/deploy/job-commands.md
index ccb6648a748..cb5ba5ab2e4 100644
--- a/website/docs/docs/deploy/job-commands.md
+++ b/website/docs/docs/deploy/job-commands.md
@@ -55,7 +55,7 @@ Here are some examples of how you can customize the comparison command:
 
 - To exclude the large `fct_orders` model from the comparison, use the `--select state:modified --exclude fct_orders` syntax.
 - To exclude models based on tags, use `--select state modified --exclude tag:tagname_a tag:tagname_b`.
-- To include models that were directly modified and also those one step downstream, use  `--select state:modified+1`.
+- To include models that were directly modified and also those one step downstream, use  `--select state:modified+`.
 
 #### Job outcome
 During a job run, the commands are "chained" together and executed as run steps. If one of the run steps in the chain fails, then the subsequent steps aren't executed, and the job will fail.