Merge branch 'current' into er/compatible-2025-01

dbt-labs · Jan 13, 2025 · ab9181c · ab9181c
2 parents 01346b8 + 202381a
commit ab9181c
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/website/blog/2023-11-14-specify-prod-environment.md b/website/blog/2023-11-14-specify-prod-environment.md
@@ -14,8 +14,8 @@ is_featured: false
 
 ---
 
-:::note You can now use a Staging environment!
-This blog post was written before Staging environments. You can now use dbt Cloud can to support the patterns discussed here. Read more about [Staging environments](/docs/deploy/deploy-environments#staging-environment).
+:::note You can now specify a Staging environment too!
+This blog post was written before dbt Cloud added full support for Staging environments. Now that they exist, you should mark your CI environment as Staging as well. Read more about [Staging environments](/docs/deploy/deploy-environments#staging-environment).
 :::
 
 :::tip The Bottom Line:

diff --git a/website/docs/docs/build/sources.md b/website/docs/docs/build/sources.md
@@ -14,7 +14,7 @@ search_weight: "heavy"
 
 ## Using sources
 Sources make it possible to name and describe the data loaded into your warehouse by your Extract and Load tools. By declaring these tables as sources in dbt, you can then
-- select from source tables in your models using the `{{ source() }}` function, helping define the lineage of your data
+- select from source tables in your models using the [`{{ source() }}` function,](/reference/dbt-jinja-functions/source) helping define the lineage of your data
 - test your assumptions about your source data
 - calculate the freshness of your source data