From b0834086da23fc088c41f5430379cca73588b793 Mon Sep 17 00:00:00 2001
From: Owen <74567580+owenprough-sift@users.noreply.github.com>
Date: Wed, 10 Jan 2024 09:18:20 -0500
Subject: [PATCH] Update materializations.md

Trivial grammar fix
---
 website/docs/docs/build/materializations.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/build/materializations.md b/website/docs/docs/build/materializations.md
index 67796afdbdb..9ae6021cc71 100644
--- a/website/docs/docs/build/materializations.md
+++ b/website/docs/docs/build/materializations.md
@@ -120,7 +120,7 @@ required with incremental materializations
   * `dbt run` on materialized views corresponds to a code deployment, just like views
 * **Cons:**
   * Due to the fact that materialized views are more complex database objects, database platforms tend to have
-less configuration options available, see your database platform's docs for more details
+fewer 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.