Merge pull request #3518 from segmentio/DOC-581-gainsight-destination-getting-started-instructions-point-to-broken-link

Fix Broken Gainsight Link [DOC-581]

Author: pwseg

src/_includes/content/sync-frequency-note.md

@@ -2,6 +2,6 @@
   <div class="fa fa-info-circle"></div>
   <div class="content">
     <p class="header">Real-time to batch destination sync frequency</p>
-    <p>Note that real-time audience syncs to {{page.title| replace: "Destination", " "}} may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.</p>
+    <p>Real-time audience syncs to {{page.title| replace: "Destination", " "}} may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.</p>
   </div>
 </div>

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

@@ -3,7 +3,7 @@ title: Gainsight Destination
 rewrite: true
 id: 54521fd625e721e32a72eeb5
 ---
-[Gainsight](https://www.gainsight.com/) is a customer success software that empowers companies to increase revenue, decrease customer churn, and drive advocacy. Gainsight for Analytics Cloud is the first and only solution that runs predictive data science natively using Salesforce sales, service, marketing, and community data.
+[Gainsight](https://www.gainsight.com/){:target="_blank"} is a customer success software that empowers companies to increase revenue, decrease customer churn, and drive advocacy. Gainsight for Analytics Cloud is the first and only solution that runs predictive data science natively using Salesforce sales, service, marketing, and community data.
 
 
 ## Getting Started
@@ -12,8 +12,8 @@ id: 54521fd625e721e32a72eeb5
 
 1. From the Segment web app, click **Catalog**.
 2. Search for Gainsight in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Copy your Gainsight Access Key and paste it into to the Access Key field in your Segment settings for Gainsight. This key can be generated from the integrations page under the `admin` area in Gainsight. It should be 36 characters long, for reference. If you need more information, visit the [relevant documentation provided by Gainsight](https://support.gainsight.com/Connectors/API_Integration/Generate_API_Access_Key).
-4. Start sending events!
+3. Copy your Gainsight Access Key and paste it into to the Access Key field in your Segment settings for Gainsight. This key can be generated from the integrations page under the `admin` area in Gainsight. It should be 36 characters long, for reference. If you need more information, visit the [relevant documentation provided by Gainsight](https://support.gainsight.com/SFDC_Edition/Connectors/Connectors/API_Integrations/Generate_API_Access_Key){:target="_blank"}.
+4. Start sending events.
 
 
 ## Identify
@@ -32,7 +32,7 @@ You can map `identify` calls to Salesforce by including the Salesforce Account I
 
 ## Track
 
-**Important**: You should only send the `track` events you need to Gainsight. You can whitelist the names of the events you need in your Segment UI settings for Gainsight. Once you pre-map your events, we will only send those events to Gainsight for you. However, if you do *not* map any events, we will by default send all your track events to Gainsight.
+**Important**: You should only send the `track` events you need to Gainsight. You can whitelist the names of the events you need in your Segment UI settings for Gainsight. Once you pre-map your events, Segment only sends those events to Gainsight for you. However, if you do *not* map any events, Segment will by default send all your track events to Gainsight.
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like this ([analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)):
 
@@ -44,7 +44,7 @@ analytics.track('Account Created', {
 });
 ```
 
-Mapping your `track` calls to a Salesforce Account is only necessary if the user doing the event is not already identified or grouped. If the user is identified all their events will be picked up automatically.
+Mapping your `track` calls to a Salesforce Account is only necessary if the user doing the event is not already identified or grouped. If the user is identified, all their events will be picked up automatically.
 
 If they haven't been identified, pass the Salesforce Account ID as a property like in the example above.
 
@@ -60,4 +60,4 @@ analytics.group('555', {
 ```
 
 
-To map your `group` calls to a Salesforce Account, pass the Salesforce Account ID as the `groupId`, like what you see in the above example.
+To map your `group` calls to a Salesforce Account, pass the Salesforce Account ID as the `groupId`, like what you see in the previous example.