From 5f6afa30502643c14e4ec53f32d17f6d9b1c7e3b Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Mon, 9 Oct 2023 13:26:59 -0700 Subject: [PATCH] Another nit --- website/docs/docs/deploy/retry-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/retry-jobs.md b/website/docs/docs/deploy/retry-jobs.md index 31e1c147d7d..f1774cd4e24 100644 --- a/website/docs/docs/deploy/retry-jobs.md +++ b/website/docs/docs/deploy/retry-jobs.md @@ -10,7 +10,7 @@ If your dbt job run completed with a status of `result:error` , you can rerun it - You have a [dbt Cloud account](https://www.getdbt.com/signup). - You must be using [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.6 or newer. -- The more recent run of the job hasn't completed successfully. The latest status of the run is `error`. +- The most recent run of the job hasn't completed successfully. The latest status of the run is `error`. - The job command that failed in the run must be one that supports the [retry command](/reference/commands/retry). ## Rerun an errored job