diff --git a/website/docs/docs/build/unit-tests.md b/website/docs/docs/build/unit-tests.md
index 0d2f29d0962..8db172f6764 100644
--- a/website/docs/docs/build/unit-tests.md
+++ b/website/docs/docs/build/unit-tests.md
@@ -37,7 +37,6 @@ You should unit test a model:
     - Window functions
     - `case when` statements when there are many `when`s
     - Truncation
-    - Recursion
 - When you're writing custom logic to process input data, similar to creating a function.
 - We don't recommend conducting unit testing for functions like `min()` since these functions are tested extensively by the warehouse. If an unexpected issue arises, it's more likely a result of issues in the underlying data rather than the function itself. Therefore, fixture data in the unit test won't provide valuable information.
 - Logic for which you had bugs reported before.
@@ -287,4 +286,4 @@ There is currently no way to unit test whether the dbt framework inserted/merged
 - [Unit testing versioned models](/reference/resource-properties/unit-testing-versions)
 - [Unit test inputs](/reference/resource-properties/unit-test-input)
 - [Unit test overrides](/reference/resource-properties/unit-test-overrides)
-- [Platform-specific data types](/reference/resource-properties/data-types)
\ No newline at end of file
+- [Platform-specific data types](/reference/resource-properties/data-types)