finish intros to some of the ref pages

Author: forstisabella

src/connections/reverse-etl/faq.md

@@ -3,12 +3,12 @@ title: Reverse ETL FAQ
 beta: false
 ---
 
-## Troubleshooting
+Get answers to some frequently asked Reverse ETL questions. 
 
-### Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping? 
+## Why do my sync results show *No records extracted* when I select *Updated records* after I enable the mapping? 
 It's expected that when you select **Updated records** the records do not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the `_segment_reverse_etl` schema. All the records are considered as *Added records* instead of *Updated records* at this time. The records can only meet the *Updated records* condition when the underlying values change after the first sync completes.
 
-### Can I be notified when Reverse ETL syncs fail?
+## Can I be notified when Reverse ETL syncs fail?
 Yes, you can sign up for Reverse ETL sync notifications.
 
 To receive Reverse ETL sync notifications: 

src/connections/reverse-etl/index.md

@@ -44,24 +44,24 @@ Learn more about the the system that powers Reverse ETL, the mappings that power
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
       href="/docs/connections/reverse-etl/observability"
-      title="Observability"
-      description="View the state of your Reverse ETL syncs and get alerts when things go wrong"
+      title="Reverse ETL Observability"
+      description="View the state of your Reverse ETL syncs and get alerted when things go wrong"
     %}
   </div>
 
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
       href="/docs/connections/reverse-etl/mappings"
-      title="Mappings"
-      description="Supported objects/arrays and ways to manage your syncs"
+      title="Reverse ETL Mappings"
+      description="Supported objects and arrays along with ways to manage your syncs"
     %}
   </div>
 
   <div class="flex__column flex__column--12 flex__column--4@medium">
     {% include components/reference-button.html
       href="/docs/connections/reverse-etl/system"
-      title="System"
-      description="Technical details about how Reverse ETL works"
+      title="Reverse ETL System"
+      description="Reference material about system limits and how Segment detects data changes"
     %}
   </div>
 </div>

src/connections/reverse-etl/mappings.md

@@ -1,9 +1,9 @@
 ---
-title: Mappings
+title: Reverse ETL Mappings
 beta: false 
 ---
 
-Learn more about supported object and array values in your mappings and how to reset or replay your syncs. 
+Learn which mapping fields support object and array values in your mappings and how you can reset or replay your syncs. 
 
 ## Supported object and arrays 
 
@@ -79,7 +79,5 @@ To reset a sync:
 3. Select the checkbox that you understand what happens when a sync is reset.
 4. Click **Reset sync**.
 
-### Automatic retry handling
-
 ## Replays
 You can choose to replay syncs. To replay a specific sync, contact [[email protected]](mailto:[email protected]). Keep in mind that triggering a replay resyncs all records for a given sync.

src/connections/reverse-etl/observability.md

@@ -3,7 +3,7 @@ title: Reverse ETL Observability
 beta: false 
 ---
 
-With the Sync history tab, you can view the status of your data extractions and see details about syncs with your warehouse. 
+Use Segment's sync history and email alert features to get better insights about the status of your Reverse ETL syncs. 
 
 ## Sync history
 Check the status of your data extractions and see details of your syncs. Click into failed records to view additional details on the error, sample payloads to help you debug the issue, and recommended actions.

src/connections/reverse-etl/reverse-etl-catalog.md

@@ -3,7 +3,7 @@ title: Reverse ETL Catalog
 beta: false
 ---
 
-Reverse ETL supports the entire Segment destination catalog - 30+ Actions destinations are natively supported, Segment Classic destinations are supported through the [Segment Connections](#segment-connections-destination) destination, and Twilio Engage Premier Subscriptions users can use the Segment Profiles destination to sync subscription data from warehouses to destinations. 
+Reverse ETL supports most of the Segment destination catalog - 30+ Actions destinations are natively supported, Segment Classic destinations are supported through the [Segment Connections](#segment-connections-destination) destination, and Twilio Engage Premier Subscriptions users can use the Segment Profiles destination to sync subscription data from warehouses to destinations. 
 
 These destinations support [Reverse ETL](/docs/connections/reverse-etl/). If you don’t see your destination listed in the Reverse ETL catalog, use the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/) to send data from your Reverse ETL warehouse to other destinations listed in the [catalog](/docs/connections/destinations/catalog/).  
 

src/connections/reverse-etl/system.md

@@ -3,7 +3,7 @@ title: Reverse ETL System
 beta: false 
 ---
 
-<!--- TODO: write an intro for this page--->
+View reference information about how Segment detects data changes in your warehouse and the rate and usage limits associated with Reverse ETL. 
 
 ## Record diffing
 Reverse ETL computes the incremental changes to your data directly within your data warehouse. The Unique Identifier column is used to detect the data changes, such as new, updated, and deleted records.