batch 2 the future

Author: forstisabella

src/connections/destinations/catalog/parsely/index.md

@@ -19,11 +19,11 @@ When you enable Parse.ly from the Segment web app, your changes appear in the Se
 
 Remember to remove the Parse.ly native snippet from your page.
 
-Parsely is more useful when you implement JSON-LD metadata across your website as described [here](https://www.parse.ly/help/integration/basic){:target="_blank"}.
+Parsely is more useful when you implement JSON-LD metadata across your website as described in Parse.ly's [Metadata: Setup and configuration](https://docs.parse.ly/metadata/){:target="_blank"} documentation.
 
 ## Page
 
-By default, unless you are using [Dynamic Tracking](https://www.parse.ly/help/integration/dynamic/){:target="_blank"}, Parse.ly automatically tracks pageviews in the background, so you do not need to track them separately with Segment's Page method.
+By default, unless you are using [Dynamic Tracking](https://docs.parse.ly/gtm-dynamic-tracking/){:target="_blank"}, Parse.ly automatically tracks pageviews in the background, so you do not need to track them separately with Segment's Page method.
 
 If you are using dynamic tracking, you must explicitly let us know in your [integration settings](#enable-dynamic-tracking). If this setting is enabled, we will disable Parse.ly's autotracking functionality and begin sending their API pageview events only in response to `analytics.page()` events.
 
@@ -80,11 +80,11 @@ analytics.alias("507f191e81");
 ```
 
 
-### Mapping custom properties to semantic Parsely properties
+### Mapping custom properties to semantic Parse.ly properties
 
-If you'd like to map certain semantic Parse.ly properties to your own custom properties (ones that do not abide by our [page spec](/docs/connections/spec/page), you can define your mappings in your Segment destination settings! You can put the name of your Segment property on the left and the Parse.ly property on the right hand side.
+If you'd like to map certain semantic Parse.ly properties to your own custom properties (ones that do not abide by Segment's [Page spec](/docs/connections/spec/page)), you can define your mappings in your Segment destination settings. You can put the name of your Segment property on the left and the Parse.ly property on the right hand side.
 
-We currently support mapping the following Parse.ly properties (make sure you spell these correctly on the right hand side of this setting!):
+Segment supports mapping the following Parse.ly properties (make sure you spell these correctly on the right hand side of this setting.):
 
 * `articleSection`
 * `thumbnailUrl`
@@ -99,11 +99,11 @@ We currently support mapping the following Parse.ly properties (make sure you sp
 
 ### Video Content Started
 
-When a user starts playback of a video, you should use our [Video Content Started](/docs/connections/spec/video/#content-events) event. We will map the properties from the Video Content Started event to the following Parse.ly video metadata fields:
+When a user starts playback of a video, you should use Segment's [Video Content Started](/docs/connections/spec/video/#content-events) event. Segment maps the properties from the Video Content Started event to the following Parse.ly video metadata fields:
 
 <table>
     <tr>
-      <td>**Parsely Parameter**</td>
+      <td>**Parse.ly Parameter**</td>
       <td>**Segment Property**</td>
       <td>**Data Type**</td>
     </tr>
@@ -176,7 +176,7 @@ When a user pauses playback of a video, you should use our [Video Playback Pause
 
 ### Video Playback Interrupted
 
-When a playback of a video is interrupted, you should use our [Video Playback Interrupted](/docs/connections/spec/video/#playback-events) event. This event just takes an `assetId` and maps to Parse.ly's `reset` method (documentation [here](https://www.parse.ly/help/integration/video_v2/){:target="_blank"}).
+When a playback of a video is interrupted, you should use our [Video Playback Interrupted](/docs/connections/spec/video/#playback-events) event. This event just takes an `assetId` and maps to Parse.ly's `reset` method (documented in the Parse.ly [Video Tracking](https://docs.parse.ly/parse-ly-video-tracking/){:target="_blank"} documentation).
 
 **Note:** this event is only relevant for web tracking. Our server side integration does not support this event.
 

src/connections/destinations/catalog/pinterest-tag/index.md

@@ -12,7 +12,7 @@ Here's how you can get started with using the Pinterest Tag!
 
 ### **1. Log into the Pinterest business account.**
 
-In order to access the Pinterest Tag, you will need to have a Pinterest business account. If you don't yet have one, sign up for one [here](https://ads.pinterest.com/){:target="_blank"}.
+In order to access the Pinterest Tag, you will need to have a Pinterest business account. If you don't yet have one, sign up for one [on Pinterest's website](https://ads.pinterest.com/){:target="_blank"}.
 
 
 ### **2. From the Ads menu, select Conversions.**

src/connections/destinations/catalog/quora-conversion-pixel/index.md

@@ -3,7 +3,7 @@ rewrite: true
 title: Quora Conversion Pixel Destination
 id: 5952698570a3e552b9575519
 ---
-[Quora Conversion Pixel](https://www.quora.com/business){:target="_blank"} enables you to attribute downstream user actions on your website to your ad campaigns running on Quora.com. Our client-side Destination code is open source. You can browse the code in GitHub [here](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/quora-conversion-pixel){:target="_blank"}.
+[Quora Conversion Pixel](https://www.quora.com/business){:target="_blank"} enables you to attribute downstream user actions on your website to your ad campaigns running on Quora.com. Our client-side Destination code is open source. You can browse the code in the [@segmentio/analytics.js-integrations](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/quora-conversion-pixel){:target="_blank"} GitHub repository.
 
 ## Getting Started
 

src/connections/destinations/catalog/responsys/index.md

@@ -42,7 +42,7 @@ _NOTE_: You can find your account's endpoint by simply going to your Oracle Resp
 
 3. Enter the name of the default **Folder** you'd like to send your Segment data to. Don't worry, you can override the default folder name on a per-call basis using destination specific options for [`.identify()`](#overriding-default-folder-and-list-names).
 
-4. Enter the name of your default **Profile List** where you would like to store your `.identify()` calls. Again, this can be overriden using destination specific options on a per-call basis as seen [here](#overriding-default-folder-and-list-names).
+4. Enter the name of your default **Profile List** where you would like to store your `.identify()` calls. Again, this can be overriden using destination specific options on a per-call basis as seen in the [Overriding default folder and list names](#overriding-default-folder-and-list-names) section.
 
 5. Choose whether you'd like to set your **Default Permission Status** to be `OPTIN` or `OPTOUT`. Unless configured otherwise, the default will be `OPTOUT`.
 

src/connections/destinations/catalog/salesforce-dmp/index.md

@@ -51,8 +51,8 @@ If you don't provide a `namespace` Segment can't pass events downstream to SFDMP
 ### Setting up for a Server-Side Implementation
 
 6. To set up SFDMP for a server-side connection, enter your SFDMP `Server-side
-   Publisher UUID`. To locate this, we recommend that you contact your SFDMP representative. Helpful documentation can be found
-   [here](https://konsole.zendesk.com/hc/en-us/articles/219493027-Mobile-HTTP-API){:target="_blank"}.
+   Publisher UUID`. To locate this, Segment recommends that you contact your SFDMP representative. Helpful documentation can be found
+   [in the Salesforce Audience Studio Help Center](https://konsole.zendesk.com/hc/en-us/articles/219493027-Mobile-HTTP-API){:target="_blank"}.
 7. Once you've retrieved your `Server-side Publisher UUID`, follow the
    instructions in the Segment SFDMP settings to enter your `Pixel.gif Domain`,
    `Pixel.gif Site` and, optionally, your `Pixel.gif Section` in the correct

src/connections/destinations/catalog/salesforce-live-agent/index.md

@@ -34,7 +34,7 @@ In short, **our integration cannot proactively initialize the Live Agent SDK on
 ## Initialization
 In order to begin using the Salesforce Live Agent using Segment, follow these implementation guidelines.
 
-1. On any page where you are not collecting user information, but do want to interact with the Salesforce Live Agent API (to achieve some of the functionality outlined [here](https://developer.salesforce.com/docs/atlas.en-us.live_agent_dev.meta/live_agent_dev/live_agent_chat_buttons_API.htm){:target="_blank"} for example), you must implement all the Live Agent SDK functionality natively **except** the actual loading of their `deployment.js` JavaScript library (the first line of the sample deployment code shown earlier). This will always be handled by Segment anywhere you are loading our JavaScript SDK.
+1. On any page where you are not collecting user information, but do want to interact with the Salesforce Live Agent API (to achieve some of the functionality outlined in Salesforce's [Customize Chat Buttons with the Deployment APIs](https://developer.salesforce.com/docs/atlas.en-us.live_agent_dev.meta/live_agent_dev/live_agent_chat_buttons_API.htm){:target="_blank"} documentation, for example), you must implement all the Live Agent SDK functionality natively **except** the actual loading of their `deployment.js` JavaScript library (the first line of the sample deployment code shown earlier). This will always be handled by Segment anywhere you are loading our JavaScript SDK.
 2. On any page where you *are* collecting user information (using some kind of pre-chat form for example) that you would like to pass to Salesforce and/or your chat agent after the user completes the form, you must ensure you **do not** call `liveagent.init` natively **anywhere on the page** and ensure that you do invoke a properly formatted Identify event, Group event (this is optional), and finally a Live Chat Conversation Started event **in that order**.
 
 ## Identify

src/connections/destinations/catalog/slack/index.md

@@ -121,8 +121,6 @@ In addition to exact event names, you can also enter regex patterns for channels
 /[a-zA-Z]+ing$/g
 ```
 
-More information on regex can be found [here](http://www.zytrax.com/tech/web/regex.htm){:target="_blank"}.
-
 
 ## Troubleshooting
 

src/connections/destinations/catalog/snapengage/index.md

@@ -3,7 +3,7 @@ rewrite: true
 title: SnapEngage Destination
 id: 54521fdb25e721e32a72eef6
 ---
-SnapEngage is an enterprise chat software for businesses. It allows you to capture more leads, drive conversions, reduce response times, and increase customer satisfaction. Our SnapEngage destination code is open source - you can check it out [here](https://github.com/segment-integrations/analytics.js-integration-snapengage){:target="_blank"}.
+SnapEngage is an enterprise chat software for businesses. It allows you to capture more leads, drive conversions, reduce response times, and increase customer satisfaction. Segment's SnapEngage destination code is open source - you can check it out in the [@segment-integrations/analytics.js-integration-snapengage](https://github.com/segment-integrations/analytics.js-integration-snapengage){:target="_blank"} GitHub repository.
 
 ## Getting Started
 

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

@@ -24,5 +24,5 @@ Segment placed the Classic destination framework in maintenance mode. Sprig enco
 3. Click **Sprig**, then click **Configure Sprig**.
 4. Select an existing JavaScript website source to connect to Sprig and click **Next**.
 5. Enter a **Destination name**, select **Classic**, and click **Save**.
-6. Type in the Environment ID and click Save Changes. You 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"}.
+6. Type in the Environment ID and click Save Changes. You your Environment ID can be found in [Connect > JavaScript](https://app.sprig.com/connect){:target="_blank"}. For for information, see Sprig's [Environments](https://docs.sprig.com/docs/products-and-environments#environments){:target="_blank"} documentation.
 7. Select **Enable Destinations** and click **Save Changes**.

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

@@ -36,7 +36,7 @@ Sprig Actions provides the following benefits over the Sprig Classic destination
 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"}.
+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, see Sprig's [Environments](https://docs.sprig.com/docs/products-and-environments#environments){:target="_blank"} documentation.
 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. -->