diff --git a/website/docs/reference/resource-configs/meta.md b/website/docs/reference/resource-configs/meta.md
index 65c8b5f908e..9ccf2cc60dc 100644
--- a/website/docs/reference/resource-configs/meta.md
+++ b/website/docs/reference/resource-configs/meta.md
@@ -184,20 +184,20 @@ Support for grouping semantic models was added in dbt Core v1.7
 
 <VersionBlock firstVersion="1.7"> 
 
-<File name='semantic_models.yml'>
+<File name='models/semantic_models.yml'>
 
 ```yml
 semantic_models:
-  - name: semantic_people
-    model: ref('people')
+  - name: semantic_model_name
     config:
       meta: {<dictionary>}
 
 ```
-The `meta` configuration can be nusted under the `config` key. 
 
 </File>
 
+The `meta` config can also be defined under the `semantic-models` config block in `dbt_project.yml`. See [configs and properties](/reference/configs-and-properties) for details.
+
 </VersionBlock>
 
 </TabItem>
@@ -207,7 +207,7 @@ The `meta` configuration can be nusted under the `config` key.
 ## 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