From cea0849d348f9c9cd4bea8fadc978c528083309a Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Fri, 6 Dec 2024 11:06:42 -0700
Subject: [PATCH] Remove link to customizing the name of a model's database
 identifier

---
 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 69d89ad30e6..a81fc088de7 100644
--- a/website/docs/docs/build/unit-tests.md
+++ b/website/docs/docs/build/unit-tests.md
@@ -26,7 +26,7 @@ Starting in dbt Core v1.8, we have introduced an additional type of test to dbt
 - We currently _don't_ support unit testing models that use recursive SQL.
 - If your model has multiple versions, by default the unit test will run on *all* versions of your model. Read [unit testing versioned models](/reference/resource-properties/unit-testing-versions) for more information.
 - Unit tests must be defined in a YML file in your [`models/` directory](/reference/project-configs/model-paths).
-- Table names must be [aliased](/docs/build/custom-aliases) in order to unit test `join` logic.
+- Table names must be aliased in order to unit test `join` logic.
 - Include all [`ref`](/reference/dbt-jinja-functions/ref) or [`source`](/reference/dbt-jinja-functions/source) model references in the unit test configuration as `input`s to avoid "node not found" errors during compilation.
 
 #### Adapter-specific caveats