From 9556d3a189c1d897c0b4f06f6a7bec4bc27b19d5 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Wed, 17 Jan 2024 17:15:02 +0000
Subject: [PATCH] Update website/docs/docs/build/sql-models.md

---
 website/docs/docs/build/sql-models.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/build/sql-models.md b/website/docs/docs/build/sql-models.md
index b2d4c26462e..88e8442efc9 100644
--- a/website/docs/docs/build/sql-models.md
+++ b/website/docs/docs/build/sql-models.md
@@ -29,7 +29,7 @@ dbt's Python capabilities are an extension of its capabilities with SQL models.
 A SQL model is a `select` statement. Models are defined in `.sql` files (typically in your `models` directory):
 - Each `.sql` file contains one model / `select` statement
 - The model name is inherited from the filename.
-- Use underscores for model names for better compatibility and clarity (such as `model_without_dots`); avoid using dots to prevent potential issues with database interpretations (`model.with.dots`). 
+- Use underscores for model names for better compatibility and clarity (such as `model_without_dots`); avoid using dots to prevent issues with the dbt Cloud parser and database interpretations (`model.with.dots`). 
 - Models can be nested in subdirectories within the `models` directory.
 
 Refer to [How we style our dbt models](/best-practices/how-we-style/1-how-we-style-our-dbt-models) for details on how we recommend you name your models.