From ca9395ff2b53ad151944fcca664c1cc2b909c81f Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Thu, 7 Dec 2023 11:28:56 -0500
Subject: [PATCH] Update website/docs/terms/surrogate-key.md

Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
---
 website/docs/terms/surrogate-key.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/terms/surrogate-key.md b/website/docs/terms/surrogate-key.md
index 9b8c932ee5a..1c4d7f21d57 100644
--- a/website/docs/terms/surrogate-key.md
+++ b/website/docs/terms/surrogate-key.md
@@ -177,7 +177,7 @@ After executing this, the table would now have the `unique_id` field now uniquel
 
 Amazing, you just made a surrogate key! You can just move on to the next data model, right? No!! It’s  critically important to test your surrogate keys for uniqueness and non-null values to ensure that the correct fields were chosen to create the surrogate key.
 
-In order to test for null and unique values you can utilize code-based tests like [dbt tests](/docs/build/data-tests), that can check fields for nullness and uniqueness. You can additionally utilize simple SQL queries or unit tests to check if surrogate key count and non-nullness is correct.
+In order to test for null and unique values you can utilize code-based data tests like [dbt tests](/docs/build/data-tests), that can check fields for nullness and uniqueness. You can additionally utilize simple SQL queries or unit tests to check if surrogate key count and non-nullness is correct.
 
 ## A note on hashing algorithms