From bee4a9bcd2d0d419b18e099947553ab74cac4960 Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Sat, 7 Oct 2023 15:26:06 -0600
Subject: [PATCH] Clarify that `meta` is no longer "always" available as a
 top-level key

---
 website/docs/reference/resource-configs/meta.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/reference/resource-configs/meta.md b/website/docs/reference/resource-configs/meta.md
index 5f63323bed2..e5ea037c331 100644
--- a/website/docs/reference/resource-configs/meta.md
+++ b/website/docs/reference/resource-configs/meta.md
@@ -207,7 +207,7 @@ semantic_models:
 ## Definition
 The `meta` field can be used to set metadata for a resource. This metadata is compiled into the `manifest.json` file generated by dbt, and is viewable in the auto-generated documentation.
 
-Depending on the resource you're configuring, `meta` may be available within the `config` property, or as a top-level key. (For backwards compatibility, `meta` is always supported as a top-level key, though without the capabilities of config inheritance.)
+Depending on the resource you're configuring, `meta` may be available within the config property, and/or as a top-level key. (For backwards compatibility, `meta` is often (but not always) supported as a top-level key, though without the capabilities of `config` inheritance.)
 
 
 ## Examples