From 4b12768585dd6215ccdb74fc72509f06f94382d7 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 6 Oct 2023 11:19:40 +0100
Subject: [PATCH 1/2] sql in caps

change sql to caps
---
 website/docs/docs/build/analyses.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/build/analyses.md b/website/docs/docs/build/analyses.md
index cd74c2e052d..c3f3611092b 100644
--- a/website/docs/docs/build/analyses.md
+++ b/website/docs/docs/build/analyses.md
@@ -6,7 +6,7 @@ id: "analyses"
 
 ## Overview
 
-dbt's notion of `models` makes it easy for data teams to version control and collaborate on data transformations. Sometimes though, a certain sql statement doesn't quite fit into the mold of a dbt model. These more "analytical" sql files can be versioned inside of your dbt project using the `analysis` functionality of dbt.
+dbt's notion of `models` makes it easy for data teams to version control and collaborate on data transformations. Sometimes though, a certain sql statement doesn't quite fit into the mold of a dbt model. These more "analytical" SQL files can be versioned inside of your dbt project using the `analysis` functionality of dbt.
 
 Any `.sql` files found in the `analyses/` directory of a dbt project will be compiled, but not executed. This means that analysts can use dbt functionality like `{{ ref(...) }}` to select from models in an environment-agnostic way.
 

From 18268d3b767cd5d7887b2bf9c4a5372b5be71ca3 Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Wed, 25 Oct 2023 15:51:45 -0400
Subject: [PATCH 2/2] Update website/docs/docs/build/analyses.md

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

diff --git a/website/docs/docs/build/analyses.md b/website/docs/docs/build/analyses.md
index 3d7ee59d1c8..af6fb0320f0 100644
--- a/website/docs/docs/build/analyses.md
+++ b/website/docs/docs/build/analyses.md
@@ -7,7 +7,7 @@ pagination_next: null
 
 ## Overview
 
-dbt's notion of `models` makes it easy for data teams to version control and collaborate on data transformations. Sometimes though, a certain sql statement doesn't quite fit into the mold of a dbt model. These more "analytical" SQL files can be versioned inside of your dbt project using the `analysis` functionality of dbt.
+dbt's notion of `models` makes it easy for data teams to version control and collaborate on data transformations. Sometimes though, a certain SQL statement doesn't quite fit into the mold of a dbt model. These more "analytical" SQL files can be versioned inside of your dbt project using the `analysis` functionality of dbt.
 
 Any `.sql` files found in the `analyses/` directory of a dbt project will be compiled, but not executed. This means that analysts can use dbt functionality like `{{ ref(...) }}` to select from models in an environment-agnostic way.