diff --git a/src/engage/user-subscriptions/subscription-sql.md b/src/engage/user-subscriptions/subscription-sql.md
index 220c59a38d..1c92c1ef83 100644
--- a/src/engage/user-subscriptions/subscription-sql.md
+++ b/src/engage/user-subscriptions/subscription-sql.md
@@ -23,7 +23,7 @@ To use Subscriptions with SQL Traits, you need the following:
 
 ## Sync subscription data with SQL
 
-You can sync with SQL from two locations in the Segment app. Navigate to **Profiles > Profile explorer** or **Engage > Audiences > Profile explorer**, then:
+You can sync with SQL from two locations in the Segment app. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer**, then:
 
 1. Click **Manage subscription statuses**, and select **Update subscription statuses**.
 2. Select **Sync with SQL**, and click **Configure**.
@@ -64,7 +64,7 @@ You can schedule sync intervals to import subscription data from your warehouse
 
 Use the Update History page to view all SQL jobs.
 
-1. Navigate to **Profiles > Profile explorer** or **Engage > Audiences > Profile explorer.**
+1. Navigate to **Unify > Profile explorer** or **Engage > Audiences > Profile explorer.**
 2. Click **Manage subscription statuses**.
 3. Select **View update history**, then select the **SQL Jobs** tab.
 
@@ -76,7 +76,7 @@ When you build your SQL query, keep the following requirements in mind for the d
 
 **Your query must:**
 
-- Return at least one column with `user_id`, `anonymous_id`, `email`, `phone` (or `group_id` for account traits if Profiles for B2B is enabled).
+- Return at least one column with `user_id`, `anonymous_id`, `email`, `phone` (or `group_id` for account traits if Unify for B2B is enabled).
 - Return records less than 16KB in size.
 
 **Your query must not:**
diff --git a/src/unify/profiles-sync/index.md b/src/unify/profiles-sync/index.md
index 8905102ad7..d976a3da4e 100644
--- a/src/unify/profiles-sync/index.md
+++ b/src/unify/profiles-sync/index.md
@@ -103,6 +103,9 @@ To start seeing unified profiles in your warehouse and build attribution models,
 
 Please visit [Tables you materialize](/docs/unify/profiles-sync/tables/#tables-you-materialize) for more on how to materialize these views either on your own, or with [Segment's open source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="blank"}.
 
+> warning ""
+> Please note that dbt models are in beta and need modifications to run efficiently on BigQuery, Synapse, and Postgres warehouses. Segment is actively working on this feature. 
+
 ## Profiles Sync limits
 
 As you use Profiles Sync, please keep the following limits in mind:
diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md
index 4113fc658a..30fa6f568c 100644
--- a/src/unify/profiles-sync/tables.md
+++ b/src/unify/profiles-sync/tables.md
@@ -171,7 +171,7 @@ Profiles Sync uses the following schema: `<profiles_space_name>.<tableName>`.
 
 If your space has the same name as a source connected to your Segment Warehouse destination, Segment overwrites data to the Event tables.
 
-{% comment %} (commenting out ERD draft for now) 
+{% comment %} (commenting out ERD draft for now)
 
 > success ""
 > For more on Profiles Sync logic, table mappings, and data types, download this [Profiles Sync ERD](/docs/unify/files/ERD.png) or visit [schema evolution and compatibility](/docs/connections/storage/warehouses/schema/#schema-evolution-and-compatibility).
@@ -190,6 +190,9 @@ Follow the steps below to change your schema name:
 > info "dbt model definitions package"
 > To get started with your table materializations, try Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}, or materialize views with your own tools.
 
+> warning ""
+> Please note that dbt models are in beta and need modifications to run efficiently on BigQuery, Synapse, and Postgres warehouses. Segment is actively working on this feature. 
+
 Every customer profile (or `canonical_segment_id`) will be represented in each of the following tables.
 
 ### `id_graph` table