From 000445f046543d152af7ea21a4b03f2e73c9a9c5 Mon Sep 17 00:00:00 2001 From: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> Date: Mon, 7 Oct 2024 08:45:41 -0700 Subject: [PATCH] Update website/docs/guides/qs-cloud-cli.md --- website/docs/guides/qs-cloud-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/qs-cloud-cli.md b/website/docs/guides/qs-cloud-cli.md index 8fa670b0902..341a10f25aa 100644 --- a/website/docs/guides/qs-cloud-cli.md +++ b/website/docs/guides/qs-cloud-cli.md @@ -145,7 +145,7 @@ Now let's dive into some more advanced components of dbt Cloud CLI. ### Deferral -Deferral is a powerful functionality that lets users leverage upstream assets that exist outside of a user's personal development environment. As a result user's can speed up their development workflows and save on warehouse compute. Let's run a few commands using deferral: +Deferral is a powerful functionality, allowing you to leverage upstream assets that exist outside of your personal development environment. As a result, you can speed up your development workflows and save on warehouse compute costs. Let's run a few commands using deferral: * `dbt compile -s stg_campaigns` — Notice how we are able to resolve dependencies in the compiled SQL without seeding campaigns.csv