PM/EM feedback

Author: rchinn1

src/unify/profiles-sync/tables.md

@@ -137,10 +137,7 @@ Segment updates this table:
 
 In the event that two profiles merge, Segment only updates the `profile_traits_updates` table for the `canonical_segment_id`, or the fully merged id.
 
-From the `profile_traits_updates` table, Segment materializes the [`profile_traits`](#the-profile_traits-table) table with all profiles and associated profile traits in your data warehouse. 
-
-> warning ""
-> The `profile_traits_updates` table doesn't backfill by default. [Contact Segment support](https://app.segment.com/workspaces?contact=1){:target="blank"} to request historical data backfill for this table. 
+From the `profile_traits_updates` table, use Segment's [open-source dbt models](https://github.com/segmentio/profiles-sync-dbt){:target="_blank"}, or your own tools to materialize the [`profile_traits`](#the-profile-traits-table) table with all profiles and associated profile traits in your data warehouse. 
 
 
 ### The identifies, page, screens, and track tables
@@ -178,8 +175,6 @@ And two entries in the `identifies` table:
 
 All these events were performed by the same person. If you use these tables to assemble your data models, though, always join them against `id_graph` to resolve each event’s `canonical_segment_id`.
 
-> warning ""
-> Beginning August 1, 2023, new Profiles Sync users will not see the `identifies` table sync by default. To sync this table, [contact Segment support](https://app.segment.com/workspaces?contact=1){:target="blank"}.
 
 ### Profiles Sync schema