diff --git a/website/docs/best-practices/custom-generic-tests.md b/website/docs/best-practices/custom-generic-tests.md
index 4be3caeef5a..e96fc864ee6 100644
--- a/website/docs/best-practices/custom-generic-tests.md
+++ b/website/docs/best-practices/custom-generic-tests.md
@@ -1,9 +1,9 @@
 ---
-title: "Writing custom generic tests"
+title: "Writing custom generic data tests"
 id: "writing-custom-generic-tests"
-description: Learn how to define your own custom generic tests.
-displayText: Writing custom generic tests
-hoverSnippet: Learn how to write your own custom generic tests.
+description: Learn how to define your own custom generic data tests.
+displayText: Writing custom generic data tests
+hoverSnippet: Learn how to write your own custom generic data tests.
 ---
 
 dbt ships with [Not Null](/reference/resource-properties/data-tests#not-null), [Unique](/reference/resource-properties/data-tests#unique), [Relationships](/reference/resource-properties/data-tests#relationships), and [Accepted Values](/reference/resource-properties/data-tests#accepted-values) generic data tests. (These used to be called "schema tests," and you'll still see that name in some places.) Under the hood, these generic data tests are defined as `test` blocks (like macros) in a globally accessible dbt project. You can find the source code for these tests in the [global project](https://github.com/dbt-labs/dbt-core/tree/main/core/dbt/include/global_project/macros/generic_test_sql).