From 1275b30ebc5fc1f033e92858db7fd7f889fbb9bd Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Mon, 13 Jan 2025 17:14:36 +0000
Subject: [PATCH] Update website/docs/docs/build/unit-tests.md

Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
---
 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 020f780dd8..4a92a5792c 100644
--- a/website/docs/docs/build/unit-tests.md
+++ b/website/docs/docs/build/unit-tests.md
@@ -220,7 +220,7 @@ Your model is now ready for production! Adding this unit test helped catch an is
 
 When configuring your unit test, you can override the output of macros, vars, or environment variables. This enables you to unit test your incremental models in "full refresh" and "incremental" modes.
 
-:::tip
+:::note
 Incremental models need to exist in the database first before running unit tests or doing a `dbt build`. Use the [`--empty` flag](/reference/commands/build#the---empty-flag) to build an empty version of the models to save warehouse spend. You can also optionally select only your incremental models using the [`--select` flag](/reference/node-selection/syntax#shorthand).
 
   ```shell