Update table organization

Author: rchinn1

src/unify/profiles-sync/tables.md

@@ -75,9 +75,15 @@ Initially, Segment generates two profiles for the first three calls. In the fina
 
 Profiles Sync tracks and provides information about these events through a set of tables, which you’ll learn about in the next section.
 
-## Tables Segment lands
 
-Using the events from the profile merge case study, Segment would land the following tables as part of Profiles Sync.
+## Profile raw tables 
+
+Profile raw tables contain records of changes to your Segment profiles and Identity Graph over time. 
+
+With raw tables, you have full control over the materialization of Profiles in your warehouse, as well as increased observibility.
+
+Raw tables contain complete historical data when using historical backfill.
+
 
 ### The id_graph_updates table
 
@@ -88,7 +94,7 @@ The `id_graph_updates` table maps between the following:
 
 As a result, this table contains information about the creation and merging of profiles, as well as the specific events that triggered those changes.
 
-Using the profile merge scenario, Segment would generate three new entries to this table:
+Using the events from the profile merge case study, Segment would generate three new entries to this table:
 
 <div style="overflow-x:auto;" markdown=1>
 
@@ -159,9 +165,24 @@ In the event that two profiles merge, Segment only updates the `profile_traits_u
 
 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
+## Event type tables 
+
+Event type tables provide a complete history for each type of event. Segment syncs events based on the event sources you've connected to Unify.
+
+Identity Resolution processes these events, and includes a `segment_id`, enabling the data to be joined into a single Profile record. 
+
+> success ""
+> Event type tables will have 2 months of historical data on backfill.
+
+Event type tables includes the following tables:
+
+- `Identify`
+- `Page`
+- `Group`
+- `Screen`
+- `Alias`
+- `Track`
 
-These tables show the instrumented events themselves. Entries in these tables reflect payloads that you instrument according to the Segment spec.
 
 These event tables are similar to the tables landed by Segment warehouse integrations, with the following exceptions:
 
@@ -220,13 +241,31 @@ If your space has the same name as a source connected to your Segment Warehouse
 Follow the steps below to change your schema name:
 {% endcomment %}
 
+## Track event tables
+
+Track event tables provide a complete event history, with one table for each unique named Track event. Segment syncs events based on the event sources you've connected to Unify. 
+
+These tables include a full set of Track event properties, with one column for each property.
+
+Segment's Identity Resolution has processed these events, which contain a `segment_id`, enabling the data to be joined into a single profile record. 
+
+> success ""
+> These tables will have two months of historical data on backfill.
+
+> info ""
+> To view and select individual track tables, edit your sync settings after you enable Profiles Sync, and wait for the initial sync to complete.
+
+
+
 ## Tables Segment materializes
 
 With Profiles Sync, you can access the following three tables that Segment materializes for a more complete view of your profile:
 - [`user_traits`](#the-user_traits-table)
 - [`user_identifiers`](#the-user_identifiers-table)
 - [`profile_merges`](#the-profile_merges-table)
 
+These materialized tables provide a snapshot of your Segment profiles, batch updated according to your sync schedule. 
+
 Visit the [selective sync](/docs/unify/profiles-sync/#using-selective-sync) setup page to enable the following materialized tables, which Segment disables by default.
 
 You can also use [historical backfill](/docs/unify/profiles-sync/#using-historical-backfill) with tables Segment materializes.
@@ -312,6 +351,10 @@ This table has the following columns:
 | `timestamp`                         | The UTC-converted timestamp set by the Segment library.                            |
 
 
+<!--
+To do: add some info here about when customers might want to materialize tables themselves 
+
+-->
 ## Tables you materialize
 
 > info "dbt model definitions package"