From 7b49355b9b7c0a29f9176d126bae500a16e29977 Mon Sep 17 00:00:00 2001
From: Himanshu <141146043+Mckesson-Himanshu@users.noreply.github.com>
Date: Fri, 23 Feb 2024 12:27:47 +0530
Subject: [PATCH] Update unit-tests.md

Grammar correction
---
 website/docs/docs/build/unit-tests.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/build/unit-tests.md b/website/docs/docs/build/unit-tests.md
index d91cbed73a0..9828788dd67 100644
--- a/website/docs/docs/build/unit-tests.md
+++ b/website/docs/docs/build/unit-tests.md
@@ -15,7 +15,7 @@ For dbt Core, unit tests will be available in v1.8, planned for late April 2024.
 
 :::
 
-Historically, dbt's test coverage was confined to [“data” tests](/docs/build/data-tests), assessing the quality of input data or resulting datasets' structure. However, these tests could only be executed _after_ a building a model. 
+Historically, dbt's test coverage was confined to [“data” tests](/docs/build/data-tests), assessing the quality of input data or resulting datasets' structure. However, these tests could only be executed _after_ building a model. 
 
 Now, we are introducing a new type of test to dbt - unit tests. In software programming, unit tests validate small portions of your functional code, and they work much the same way here. Unit tests allow you to validate your SQL modeling logic on a small set of static inputs _before_ you materialize your full model in production. Unit tests enable test-driven development, benefiting developer efficiency and code reliability.