Merge branch 'current' into joellabes-patch-4

website/docs/docs/build/semantic-models.md

@@ -43,7 +43,7 @@ semantic_models:
   - name: the_name_of_the_semantic_model      ## Required
     description: same as always               ## Optional
     model: ref('some_model')                  ## Required
-    default:                                  ## Required
+    defaults:                                 ## Required
       agg_time_dimension: dimension_name    ## Required if the model contains dimensions
     entities:                                 ## Required
        - see more information in entities

website/docs/docs/cloud/secure/about-privatelink.md

@@ -23,3 +23,4 @@ dbt Cloud supports the following data platforms for use with the PrivateLink fea
 - [Databricks](/docs/cloud/secure/databricks-privatelink)
 - [Redshift](/docs/cloud/secure/redshift-privatelink)
 - [Postgres](/docs/cloud/secure/postgres-privatelink)
+- [VCS](/docs/cloud/secure/vcs-privatelink)

website/docs/docs/collaborate/explore-projects.md

@@ -36,7 +36,7 @@ For a richer experience with dbt Explorer, you must:
 - Run [dbt source freshness](/reference/commands/source#dbt-source-freshness) within a job in the environment to view source freshness data.
 - Run [dbt snapshot](/reference/commands/snapshot) or [dbt build](/reference/commands/build) within a job in the environment to view snapshot details.
 
-Richer and more timely metadata will become available as dbt, the Discovery API, and the underlying dbt Cloud platform evolves.
+Richer and more timely metadata will become available as dbt Core, the Discovery API, and the underlying dbt Cloud platform evolves.
 
 ## Explore your project's lineage graph {#project-lineage}
 
@@ -46,6 +46,8 @@ If you don't see the project lineage graph immediately, click **Render Lineage**
 
 The nodes in the lineage graph represent the project’s resources and the edges represent the relationships between the nodes. Nodes are color-coded and include iconography according to their resource type.
 
+By default, dbt Explorer shows the project's [applied state](/docs/dbt-cloud-apis/project-state#definition-logical-vs-applied-state-of-dbt-nodes) lineage. That is, it shows models that have been successfully built and are available to query, not just the models defined in the project.
+
 To explore the lineage graphs of tests and macros, view [their resource details pages](#view-resource-details). By default, dbt Explorer excludes these resources from the full lineage graph unless a search query returns them as results.
 
 To interact with the full lineage graph, you can:

website/docs/docs/collaborate/model-performance.md

@@ -8,9 +8,9 @@ dbt Explorer provides metadata on dbt Cloud runs for in-depth model performance
 
 <LoomVideo id='98f33b3b7a374df0b7c04747eae6ef44' />
 
-:::tip Public preview 
+:::tip Beta 
 
-The model performance feature is now available in dbt Explorer! Check it out! 
+The model performance beta feature is now available in dbt Explorer! Check it out! 
 :::
 
 ## The Performance overview page 

website/docs/docs/collaborate/project-recommendations.md

@@ -4,9 +4,9 @@ sidebar_label: "Project recommendations"
 description: "dbt Explorer provides recommendations that you can take to improve the quality of your dbt project."
 ---
 
-:::tip Public preview 
+:::tip Beta 
 
-The project recommendations feature is now available in dbt Explorer! Check it out!
+The project recommendations beta feature is now available in dbt Explorer! Check it out!
 
 :::
 

website/snippets/_cloud-environments-info.md

@@ -62,7 +62,7 @@ By default, all environments will use the default branch in your repository (usu
 For more info, check out this [FAQ page on this topic](/faqs/Environments/custom-branch-settings)!
 
 
-### Extended attributes <Lifecycle status='beta'/>
+### Extended attributes
 
 :::note 
 Extended attributes are retrieved and applied only at runtime when `profiles.yml` is requested for a specific Cloud run. Extended attributes are currently _not_ taken into consideration for Cloud-specific features such as PrivateLink or SSH Tunneling that do not rely on `profiles.yml` values.