From ab338425bb2e9f8d5e0b38960c4d4f96417e4ce9 Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Fri, 8 Nov 2024 10:41:58 -0500
Subject: [PATCH] New commit to next

---
 website/docs/reference/global-configs/cache.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/website/docs/reference/global-configs/cache.md b/website/docs/reference/global-configs/cache.md
index 1a74fef8d30..349bdcd9d6f 100644
--- a/website/docs/reference/global-configs/cache.md
+++ b/website/docs/reference/global-configs/cache.md
@@ -13,6 +13,7 @@ There are two ways to optionally modify this behavior:
 - `CACHE_SELECTED_ONLY` (default `False`): Whether to limit cache population to just the resources selected in the current run. This can offer significant speed improvements when running a small subset of a large project, while still providing the benefit of caching upfront.
 
 For example, to quickly compile a model that requires no database metadata or introspective queries:
+
 ```text
 
 dbt --no-populate-cache compile --select my_model_name