Merge branch 'current' into wlsdbt-patch-2

website/docs/docs/build/data-tests.md

@@ -43,13 +43,13 @@ These tests are defined in `.sql` files, typically in your `tests` directory (as
 
 ```sql
 -- Refunds have a negative amount, so the total amount should always be >= 0.
--- Therefore return records where this isn't true to make the test fail
+-- Therefore return records where total_amount < 0 to make the test fail.
 select
     order_id,
     sum(amount) as total_amount
 from {{ ref('fct_payments' )}}
 group by 1
-having not(total_amount >= 0)
+having total_amount < 0
 ```
 
 </File>
@@ -247,7 +247,7 @@ This workflow allows you to query and examine failing records much more quickly
 
 <Lightbox src="/img/docs/building-a-dbt-project/test-store-failures.gif" title="Store test failures in the database for faster development-time debugging."/>
 
-Note that, if you elect to store test failures:
+Note that, if you select to store test failures:
 * Test result tables are created in a schema suffixed or named `dbt_test__audit`, by default. It is possible to change this value by setting a `schema` config. (For more details on schema naming, see [using custom schemas](/docs/build/custom-schemas).)
 - A test's results will always **replace** previous failures for the same test.
 

website/docs/docs/build/metricflow-commands.md

@@ -75,7 +75,7 @@ You can use the `dbt sl` prefix before the command name to execute them in the d
 - [`list dimensions`](#list) — Lists unique dimensions for metrics.
 - [`list dimension-values`](#list-dimension-values) — List dimensions with metrics.
 - [`list entities`](#list-entities) — Lists all unique entities.
-- [`list saved queries`)(#list-saved-queries) — Lists available saved queries. Use the `--show-exports` flag to display each export listed under a saved query.
+- [`list saved queries`](#list-saved-queries) — Lists available saved queries. Use the `--show-exports` flag to display each export listed under a saved query.
 - [`query`](#query) — Query metrics, saved queries, and dimensions you want to see in the command line interface. Refer to [query examples](#query-examples) to help you get started.
 
 <!--below commands aren't supported in dbt cloud yet

website/docs/docs/build/saved-queries.md

@@ -51,7 +51,7 @@ To define a saved query, refer to the following parameters:
 | `query_params`       | Structure   | Required     | Contains the query parameters. |
 | `query_params::metrics`   | List or String   | Optional    | A list of the metrics to be used in the query as specified in the command line interface. |
 | `query_params::group_bys`    | List or String          | Optional    | A list of the Entities and Dimensions to be used in the query, which include the `Dimension` or `TimeDimension`. |
-| `query_params::where`        | LList or String  or String | Optional  | A list of string which may include the `Dimension` or `TimeDimension` objects. |
+| `query_params::where`        | List or String | Optional  | A list of string which may include the `Dimension` or `TimeDimension` objects. |
 | `exports`     | List or Structure | Optional    | A list of exports to be specified with the exports structure.     |
 | `exports::name`       | String               | Required     | Name of the export object.      |
 | `exports::config`     | List or Structure     | Required     | A config section for any parameters specifying the export.  |

website/docs/docs/core/connect-data-platform/fabric-setup.md

@@ -15,7 +15,7 @@ meta:
 
 :::info
 
-Below is a guide for use with [Synapse Data Warehouse](https://learn.microsoft.com/en-us/fabric/data-warehouse/data-warehousing#synapse-data-warehouse), a new product within Microsoft Fabric.
+Below is a guide for use with [Synapse Data Warehouse](https://learn.microsoft.com/en-us/fabric/data-warehouse/data-warehousing#synapse-data-warehouse), a new product within Microsoft Fabric. The adapter currently only supports connecting to a warehouse and not a lakehouse endpoint. You can access data in your lakehouse via the warehouse if you are in the same workspace. 
 
 To learn how to set up dbt with Azure Synapse Dedicated Pools, refer to [Microsoft Azure Synapse DWH setup](/docs/core/connect-data-platform/azuresynapse-setup).
 

website/docs/docs/dbt-cloud-apis/project-state.md

@@ -81,5 +81,5 @@ Here are some limitations of the state representation in the Discovery API:
 - Users must access the default production environment to know the latest state of a project.
 - The API gets the definition from the latest manifest generated in a given deployment environment, but that often won’t reflect the latest project code state.
 - Compiled code results may be outdated depending on dbt Cloud run step order and failures.
-- Catalog info can be outdated, or incomplete (in the applied state), based on if/when docs were last generated.
+- Catalog info can be outdated, or incomplete (in the applied state), based on if/when `docs generate` was last run.
 - Source freshness checks can be out of date (in the applied state) depending on when the command was last run, and it’s not included in `build`.