From cd414c584c767d2b16de808fbdbae9ebd1163c38 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Tue, 19 Nov 2024 10:05:05 -0500
Subject: [PATCH] Update data-tests.md

add clarifying info based on user feedback in training workshop
---
 website/docs/docs/build/data-tests.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/docs/build/data-tests.md b/website/docs/docs/build/data-tests.md
index af48e0af267..2b7c908d6e7 100644
--- a/website/docs/docs/build/data-tests.md
+++ b/website/docs/docs/build/data-tests.md
@@ -45,9 +45,9 @@ Defining data tests is a great way to confirm that your outputs and inputs are a
 If you're new to dbt, we recommend that you check out our [quickstart guide](/guides) to build your first dbt project with models and tests.
 :::
 
-## Singular data tests
+## Singular data tests for me
 
-The simplest way to define a data test is by writing the exact SQL that will return failing records. We call these "singular" data tests, because they're one-off assertions usable for a single purpose.
+The simplest way to define a data test is by writing the exact SQL that will return failing records. We call these "singular" data tests, because they're one-off assertions usable for a single purpose. I can type here and add clarifying info. 
 
 These tests are defined in `.sql` files, typically in your `tests` directory (as defined by your [`test-paths` config](/reference/project-configs/test-paths)). You can use Jinja (including `ref` and `source`) in the test definition, just like you can when creating models. Each `.sql` file contains one `select` statement, and it defines one data test: