From 27a0129f44d8e64b7e12283f2a85a928230b57ed Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Sat, 7 Oct 2023 16:16:49 -0600
Subject: [PATCH] Fix rendering of "Advice" for when to use materialized views

---
 website/docs/docs/build/materializations.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/website/docs/docs/build/materializations.md b/website/docs/docs/build/materializations.md
index 463651ccc77..ae75b575d5f 100644
--- a/website/docs/docs/build/materializations.md
+++ b/website/docs/docs/build/materializations.md
@@ -140,8 +140,7 @@ required with incremental materializations
 less configuration options available, see your database platform's docs for more details
   * Materialized views may not be supported by every database platform
 * **Advice:**
-    * Consider materialized views for use cases where incremental models are sufficient, 
-but you would like the data platform to manage the incremental logic and refresh.
+  * Consider materialized views for use cases where incremental models are sufficient, but you would like the data platform to manage the incremental logic and refresh.
 
 ## Python materializations