Merge pull request #607 from segmentio/repo-sync

repo sync

Author: bot-docsteam

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

@@ -1,5 +1,5 @@
 ---
-title: 'Sprig (Actions) Destination'
+title: 'Sprig Actions'
 hidden: false
 hide-boilerplate: true
 hide-dossier: true
@@ -15,36 +15,37 @@ versions:
 
 {% include content/plan-grid.md name="actions" %}
 
-[Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through microsurveys, concept tests, and video questions.
+[Sprig](https://sprig.com/?&utm_source=segmentio&utm_medium=docs_actions&utm_campaign=integration){:target="_blank"} is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real-time, through In-Product Surveys, Concept and Usability tests.
 
-Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment-web) or contact [[email protected]](mailto:[email protected]).
+Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment){:target="_blank"} or contact [[email protected]](mailto:[email protected]).
 
 
-## Benefits of Sprig (Actions) vs Sprig Classic
+## Benefits of Sprig Actions versus Sprig Classic
 
-Sprig (Actions) provides the following benefits over the classic Sprig destination:
+Sprig Actions provides the following benefits over the Sprig Classic destination:
 
-- **Trigger microsurveys**. Because Sprig (Actions) hooks into your browser-based, JavaScript Segment source, it can be used to trigger Sprig microsurveys.
-- **Code-free Sprig installation**. The Sprig (Actions) destination can install the Sprig SDK onto your website, without you having to update any code.
+- **Trigger studies**. Sprig Actions integrate into your browser-based Analytics.js source, so you can use them to trigger Sprig studies.
+- **Code-free Sprig installation**. You can intall Sprig Actions on your website, without you having to update any code. 
 
 <!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
 
-## Getting started
+## Getting started 
 
-1. From the Segment web app, click **Catalog**, then click **Destinations**.
-2. Use the navigation on the left to locate and select Sprig (Actions).
-3. Click **Configure Sprig (Actions)**.
-4. Select an existing JavaScript website source to connect to Sprig (Actions).
-5. Find your Environment ID on [Sprig Dashboard > Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. Use the Development Environment ID for a testing environment, and the Production Environment ID for your live website environment. When you configure the destination, input the appropriate Environment ID.  
-6. Select **Quick Setup** to start with pre-populated subscriptions, or **Customized Setup** to configure each action from scratch. Click **Configure Actions** to complete setup.
+1. In the Segment web app, click **Catalog**, then click **Destinations**.
+2. Type Sprig in the **Filter Destinations** field.
+3. Click **Sprig**, then click **Configure Sprig**.
+4. Select an existing JavaScript website source to connect to Sprig and click **Next**.
+5. Type in a **Destination name**, Select **Actions**, and click **Save**.
+6. Type in the Environment ID and click Save Changes. Your Environment ID can be found in [Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. For for information, click [here](https://docs.sprig.com/docs/products-and-environments#environments){:target="_blank"}.
+7. Select **Enable Destinations** and click **Save Changes**.
 
 <!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
 
 {% include components/actions-fields.html %}
 <!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
 
-## Migration from the classic Sprig destination
+## Migration from Sprig Classic
 
-To prevent duplicate events being created in Sprig, ensure that for each Segment source, this destination and the Sprig Cloud destination are not both enabled at the same time.
+Segment placed the Classic destination framework in maintenance mode. Sprig encourages all customers to move to the Actions destination framework. To prevent the generation of duplicate events in Sprig, don't enable the Sprig Web destination and the Sprig Cloud destination on the same source.