comitting all in flight [netlify-build]

Author: forstisabella

src/connections/destinations/catalog/actions-sprig-web/index.md

@@ -3,7 +3,6 @@ title: StackAdapt Destination
 hide-boilerplate: true
 hide-dossier: true
 id: 61d8859be4f795335d5c677c
-hidden: true
 redirect_from: '/connections/destinations/catalog/actions-stackadapt/'
 ---
 

src/connections/destinations/catalog/actions-stackadapt-cloud/index.md

@@ -6,10 +6,10 @@ redirect_from:
   - '/reverse-etl/'
 ---
 
-Reverse ETL (Extract, Transform, Load) extracts data from a data warehouse using a query you provide and syncs the data to your third party destinations. 
+Reverse ETL (Extract, Transform, Load) extracts data from a warehouse using a query you provide and syncs this warehouse data to your third party destinations. 
 
 Use Reverse ETL when you want to:
-* **Enable your marketing teams**: Sync audiences and other data built in the warehouse to multi-channel marketing tools, like Braze, Hubspot, or Salesforce Marketing Cloud, to personalize marketing campaigns.
+* **Elevate marketing campaigns**: Sync audiences and other data built in the warehouse to multi-channel marketing tools, like Braze, Hubspot, or Salesforce Marketing Cloud, to personalize marketing campaigns.
 * **Enrich your customer profiles**: Sync enriched data to destinations like Mixpanel for a more complete view of the customer, or enrich Segment Profiles with data from your warehouse.
 * **Activate data in Twilio Engage**: Send data in the warehouse back into Segment as events that can be activated in all supported destinations, including Twilio Engage destinations.
 * **Strengthen your conversion events**: Pass offline or enriched data to conversion APIs like Facebook, Google Ads, TikTok, or Snapchat.
@@ -26,7 +26,7 @@ Use Reverse ETL when you want to:
     href="/docs/connections/reverse-etl/setup"
     icon="getting-started.svg"
     title="Set up Reverse ETL"
-    description="Add a Reverse ETL source, set up a model, add a destination, and create mappings to sync data from your warehouse to your downstream destinations."
+    description="Set up the infrastructure you need to sync data from your warehouse to your downstream destinations."
   %}
 
   {% include components/reference-button.html
@@ -53,7 +53,7 @@ Learn more about the system that powers Reverse ETL, supported destinations, and
     {% include components/reference-button.html
       href="/docs/connections/reverse-etl/reverse-etl-catalog"
       title="Destination catalog"
-      description="View the destinations that support Reverse ETL sources."
+      description="View the destinations that you can connect to your Reverse ETL sources."
     %}
   </div>
 

src/connections/reverse-etl/index.md

@@ -3,28 +3,21 @@ title: Manage Reverse ETL Syncs
 beta: false
 ---
 
-View your sync history, gain insights into sync statuses, and restart or replay failed or partially successful syncs.
+View your sync history, reset your syncs, or subscribe to alerts.
 
 ## Sync overview
-On the Reverse ETL sync overview tab for your destination, you can see information about your recent Reverse ETL syncs at a glance, search for recent syncs, and quickly access the mappings and models that power Reverse ETL.
+The Reverse ETL sync overview tab, located under **Connections > Destinations**, gives you an overview of your latest Reverse ETL syncs. 
 
 ![A screenshot of the sync overview page, which includes one failed sync and three successful syncs.](images/sync-overview.png)
 
 You can view the following information about each sync: 
-- **Latest sync**: The progress of your latest sync: syncs can either be **In progress**, **Successful**, or **Failed**. Also included is the timestamp of the sync start time.
+- **Latest sync**: The status of your latest sync. Syncs can either be **In progress**, **Successful**, or **Failed**.
 - **Mapping**: The named mapping that powered the sync and a hyperlink to the mapping's overview page. 
-- **Model**: The name that you gave the SQL query used to withdraw information from your warehouse, with a hyperlink to the model overview page. Below the model name, you can see the warehouse source that Segment extracts information from.
-- **Action**: The Action that your destination uses to map information from your warehouse to your downstream destination. 
-- **Mapping status**: The status of your mapping: either **Enabled** or **Disabled**. 
-
-You can also filter the sync overview table to return only the syncs that match your criteria. 
-
-You can filter for the following sync attributes: 
-- **Sync status**: The status of your sync: In progress, Successful, Partially successful, or Failed.
-- **Start time**: Select a predefined time period, or create a custom date range. 
-- **Model**: The model connected to your sync. 
-- **Destination**: Select one or more of your connected destinations. 
-- **Mapping status**: The status of your mapping: either **Enabled** or **Disabled**. 
+- **Model**: The model that extracts data from your warehouse.
+- **Action**: The action that your destination uses to map information from your warehouse to your downstream destination. 
+- **Mapping status**: The status of your mapping - either **Enabled** or **Disabled**. 
+
+You can also filter the sync overview table to return only **Enabled** or **Disabled** 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/manage-retl.md

@@ -67,7 +67,7 @@ To edit your model:
 ## Step 3: Add a destination
 Once you’ve added a model, you need to add a destination. In Reverse ETL, destinations are the business tools or apps you use that Segment syncs the data from your warehouse to.
 
-Reverse ETL supports 30+ destinations: see all destinations listed in the [Reverse ETL catalog](/docs/connections/reverse-etl/reverse-etl-catalog/). If the destination you want to send data to is not listed in the Reverse ETL catalog, use the [Segment Connections Destination](/docs/connections/reverse-etl/reverse-etl-catalog/#segment-connections-destination) to send data from your Reverse ETL warehouse to your destination.
+Reverse ETL supports the destinations in the [Reverse ETL catalog](/docs/connections/reverse-etl/reverse-etl-catalog/). If the destination you want to send data to is not listed in the Reverse ETL catalog, use the [Segment Connections Destination](/docs/connections/reverse-etl/reverse-etl-catalog/#segment-connections-destination) to send data from your Reverse ETL warehouse to your destination.
 
 Engage users can use the [Segment Profiles Destination](/docs/connections/destinations/catalog/actions-segment-profiles/) to create and update [Profiles](/docs/unify/) that can then be accessed through [Profile API](/docs/unify/profile-api/) and activated within [Twilio Engage](/docs/engage).