diff --git a/website/docs/docs/build/data-tests.md b/website/docs/docs/build/data-tests.md
index 4e56042b3f2..38a2c74b646 100644
--- a/website/docs/docs/build/data-tests.md
+++ b/website/docs/docs/build/data-tests.md
@@ -70,6 +70,8 @@ The name of this test is the name of the file: `assert_total_payment_amount_is_p
 
 Singular data tests are easy to write—so easy that you may find yourself writing the same basic structure over and over, only changing the name of a column or model. By that point, the test isn't so singular! In that case, we recommend...
 
+
+
 ## Generic data tests
 Certain data tests are generic: they can be reused over and over again. A generic data test is defined in a `test` block, which contains a parametrized query and accepts arguments. It might look like:
 
@@ -308,6 +310,7 @@ data_tests:
 
 ## FAQs
 
+<FAQ path="/Tests/available-tests" />
 <FAQ path="Tests/test-one-model" />
 <FAQ path="Runs/failed-tests" />
 <FAQ path="Tests/recommended-tests" />
diff --git a/website/docs/faqs/Tests/available-tests.md b/website/docs/faqs/Tests/available-tests.md
index 2b5fd3ff55c..86c4cd8e3d3 100644
--- a/website/docs/faqs/Tests/available-tests.md
+++ b/website/docs/faqs/Tests/available-tests.md
@@ -15,3 +15,5 @@ Out of the box, dbt ships with the following tests:
 You can also write your own [custom schema data tests](/docs/build/data-tests).
 
 Some additional custom schema tests have been open-sourced in the [dbt-utils package](https://github.com/dbt-labs/dbt-utils/tree/0.2.4/#schema-tests), check out the docs on [packages](/docs/build/packages) to learn how to make these tests available in your project.
+
+Note that although you can't document data tests as of yet, we recommend checking out [this dbt Core discussion](https://github.com/dbt-labs/dbt-core/issues/2578) where the dbt community shares ideas.