Merge branch 'current' into mwong-scroll

website/docs/reference/dbt-jinja-functions/builtins.md

@@ -42,9 +42,9 @@ From dbt v1.5 and higher, use the following macro to extract user-provided argum
 -- call builtins.ref based on provided positional arguments
 {% set rel = None %}
 {% if packagename is not none %}
-    {% set rel = return(builtins.ref(packagename, modelname, version=version)) %}
+    {% set rel = builtins.ref(packagename, modelname, version=version) %}
 {% else %}
-    {% set rel = return(builtins.ref(modelname, version=version)) %}
+    {% set rel = builtins.ref(modelname, version=version) %}
 {% endif %}
 
 -- finally, override the database name with "dev"

website/snippets/_cloud-environments-info.md

@@ -46,7 +46,7 @@ For more info, check out this [FAQ page on this topic](/faqs/Environments/custom
 ### 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.
+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 SSH Tunneling which do not rely on `profiles.yml` values.
 :::
 
 Extended Attributes is a feature that allows users to set a flexible [profiles.yml](/docs/core/connect-data-platform/profiles.yml) snippet in their dbt Cloud Environment settings. It provides users with more control over environments (both deployment and development) and extends how dbt Cloud connects to the data platform within a given environment.