Minor edits

rchinn1 · rchinn1 · commit a38fb16f9324 · 2022-03-25T17:44:47.000-07:00
diff --git a/src/connections/destinations/catalog/moengage/index.md b/src/connections/destinations/catalog/moengage/index.md
@@ -11,7 +11,7 @@ The Segment-MoEngage Integration is a bundled integration, meaning it requires t
 ## Setup MoEngage in your Segment Workspace:
 
 To setup MoEngage do the following :
-  1. First get your key(AppID) from the MoEngage dashboard, `Dashboard --> Settings --> App --> General`.
+  1. First get your key(AppID) from the MoEngage dashboard. Navigate to `Dashboard --> Settings --> App --> General`.
   2. Go to your **Segment workspace**, go to **Destinations** and select **MoEngage**.
   3. Enable the MoEngage Destination.
   4. Go to the MoEngage Settings and enter the MoEngage AppID, obtained in **Step1**.
@@ -27,27 +27,27 @@ users it’ll be instantaneous! Segment-MoEngage Integration is a bundled integr
 ## iOS
 
 
-To get started with MoEngage on iOS, first integrate your app with the [MoEngage-Segment-iOS](https://github.com/moengage/MoEngage-Segment-iOS) library. You can integrate MoEngage and Segment with [CocoaPods](http://cocoapods.org) or with Swift Package Manager.
+To get started with MoEngage on iOS, first integrate your app with the [MoEngage-Segment-iOS](https://github.com/moengage/MoEngage-Segment-iOS){:target="_blank"} library. You can integrate MoEngage and Segment with [CocoaPods](http://cocoapods.org){:target="_blank"} or with Swift Package Manager.
 
   * Initialize pod with pod init command, this will create a podfile for your project.
   * Update your podfile by adding pod '**Segment-MoEngage**' as shown below:
 
   ```ruby
   use_frameworks!
-  pod 'Segment-MoEngage’
+  pod 'Segment-MoEngage'
   ```
 
    * Update the pod.
 
     pod update
-    
-    
+
+
  To install with SPM use the https://github.com/moengage/MoEngage-Segment-iOS.git and set the branch as master or version as 7.0.0 and above.
 
 ### Configure the Segment SDK:
 
-Now head to the App Delegate file, and setup the Segment SDK by
-1. Importing `SEGMoEngageIntegrationFactory.h` and `SEGMoEngageInitializer.h`.
+Navigate to the App Delegate file, and setup the Segment SDK:
+1. Import `SEGMoEngageIntegrationFactory.h` and `SEGMoEngageInitializer.h`.
 2. Initialize `MOSDKConfig` object and call `initializeDefaultInstance:` method of `SEGMoEngageInitializer`.
 3. Initialize `SEGMoEngageIntegrationFactory` instance to the `SEGAnalyticsConfiguration` as shown below:
 
@@ -61,7 +61,7 @@ Now head to the App Delegate file, and setup the Segment SDK by
     //Initialize SDKConfig object and call initializeDefaultInstance: method of SEGMoEngageInitializer
     MOSDKConfig* sdkConfig = [[MOSDKConfig alloc] initWithAppID:@"YOUR APP ID"];
     [SEGMoEngageInitializer initializeDefaultInstance:sdkConfig];
-    
+
     // Add your configuration key from Segment
     SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:@"configuration key"];
 
@@ -117,11 +117,11 @@ To differentiate between those, use one of the method below:
  [[MoEngage sharedInstance] appStatus:AppStatusUpdate];
  ```
 
-Read more on [install/update differentiation](https://developers.moengage.com/hc/en-us/articles/4403910297620).
+Read more on [install/update differentiation](https://developers.moengage.com/hc/en-us/articles/4403910297620){:target="_blank"}.
 
 ### Set the data center
 
-By default, the data center setting in the SDK is set to `data_center_01`. Follow the steps in the [MoEngage - Data Redirection](https://developers.moengage.com/hc/en-us/articles/4403910162452-Data-Center) to update the data center value. If not set correctly, several features of the MoEngage SDK will not function.
+By default, the data center setting in the SDK is set to `data_center_01`. Follow the steps in the [MoEngage - Data Redirection](https://developers.moengage.com/hc/en-us/articles/4403910162452-Data-Center){:target="_blank"} to update the data center value. If not set correctly, several features of the MoEngage SDK will not function.
 
 ### Using features provided in the MoEngage SDK
 
@@ -150,19 +150,19 @@ Push Notifications are a great way to keep your users engaged and informed about
   ```
 
 **MoEngage Push Implementation:**
-For information about the MoEngage push implementation, see [**Push Notifications**](https://developers.moengage.com/hc/en-us/articles/4403943988756) in the MoEngage documentation.
+For information about the MoEngage push implementation, see [**Push Notifications**](https://developers.moengage.com/hc/en-us/articles/4403943988756){:target="_blank"} in the MoEngage documentation.
 
 
 #### In-app messaging
-In-App Messages are custom views which you can send to a set of users to show custom messages,  give new offers, or direct to a specific page. For more information about In-app messaging, see [MoEngage - In-App NATIV](https://developers.moengage.com/hc/en-us/articles/4404155127828-In-App-Nativ)
+In-App Messages are custom views which you can send to a set of users to show custom messages, give new offers, or direct to a specific page. For more information about In-app messaging, see [MoEngage - In-App NATIV](https://developers.moengage.com/hc/en-us/articles/4404155127828-In-App-Nativ){:target="_blank"}.
 
 
 #### Cards
-Create targeted or automated App Inbox/NewsFeed messages that can be grouped into various categories, and target your users with different updates or offers that can stay in the Inbox/Feed over a designated period of time. For more information about cards, see [MoEngage - Cards](https://developers.moengage.com/hc/en-us/articles/4404058438676-Cards-in-iOS).
+Create targeted or automated App Inbox/NewsFeed messages that can be grouped into various categories, and target your users with different updates or offers that can stay in the Inbox/Feed over a designated period of time. For more information about cards, see [MoEngage - Cards](https://developers.moengage.com/hc/en-us/articles/4404058438676-Cards-in-iOS){:target="_blank"}.
 
 
 #### Compliance
-To make the App compliant with policies i.e,GDPR while using our SDK, follow the doc in this [link](https://developers.moengage.com/hc/en-us/articles/4403905438228-SDK-initialisation).
+To make the App compliant with policies i.e,GDPR while using our SDK, follow the doc in this [link](https://developers.moengage.com/hc/en-us/articles/4403905438228-SDK-initialisation){:target="_blank"}.
 
 ### Segment Docs
 For more info on using **Segment for iOS** refer to [**Developer Docs**](/docs/connections/sources/catalog/libraries/mobile/ios/) provided by Segment.
@@ -195,7 +195,7 @@ The MoEngage SDK depends on the below Jetpack libraries provided by Google for i
     implementation("androidx.appcompat:appcompat:1.3.1")
     implementation("androidx.lifecycle:lifecycle-process:2.4.0")
 ```
-Refer to the [SDK Configuration](https://developers.moengage.com/hc/en-us/articles/4401984733972-Android-SDK-Configuration) documentation to know more about the build config and other libraries used by the SDK.
+Refer to the [SDK Configuration](https://developers.moengage.com/hc/en-us/articles/4401984733972-Android-SDK-Configuration){:target="_blank"} documentation to know more about the build config and other libraries used by the SDK.
 
 ### Register MoEngage with Segment SDK
 
@@ -232,14 +232,14 @@ MoEngage.initialiseDefaultInstance(moEngage);
 ### Exclude MoEngage Storage File from Auto-Backup
 Auto backup service of Andriod periodically backs up the Shared Preference file, Database files, and so on.
 
-For more information, refer to [Auto Backup](https://developer.android.com/guide/topics/data/autobackup).
+For more information, refer to [Auto Backup](https://developer.android.com/guide/topics/data/autobackup){:target="_blank"}.
 
-The backup results in MoEngage SDK identifiers to be backed up and restored after re-install.
+As a result of the backup, MoEngage SDK identifiers are backed up and restored after re-install.
 The restoration of the identifier results in your data being corrupted and the user not being reachable using push notifications.
 
-To ensure data is not corrupted after a backup is restored, opt-out of MoEngage SDK storage files.
+To ensure data isn't corrupted after a backup is restored, opt-out of MoEngage SDK storage files.
 
-Refer to the [documentation](https://developers.moengage.com/hc/en-us/articles/4401999257236-Exclude-MoEngage-Storage-File-from-Auto-Backup) for further details. 
+Refer to the [documentation](https://developers.moengage.com/hc/en-us/articles/4401999257236-Exclude-MoEngage-Storage-File-from-Auto-Backup){:target="_blank"} for further details.
 
 ### Install or update differentiation
 This is required for migrations to the MoEngage Platform so the SDK can determine whether the user is a new user on your app, or an existing user who updated to the latest version.
@@ -265,7 +265,7 @@ Copy the Server Key from the FCM console and add it to the MoEngage Dashboard. T
 
 To display push notifications, some metadata regarding the notification is required. For example, the small icon and large icon drawables are mandatory.
 
-Refer to the [MoEngage - NotificationConfig](https://moengage.github.io/android-api-reference/core/com.moengage.core.config/-notification-config/index.html) API reference for all the possible options.
+Refer to the [MoEngage - NotificationConfig](https://moengage.github.io/android-api-reference/core/com.moengage.core.config/-notification-config/index.html){:target="_blank"} API reference for all the possible options.
 
 Use the `configureNotificationMetaData()` to pass on the configuration to the SDK.
 
@@ -341,26 +341,26 @@ When the MoEngage SDK handles push registration, it optionally provides a callba
 
 An application can get this callback by implementing `FirebaseEventListener` and registering for a callback in the Application class `onCreate()` using `MoEFireBaseHelper.getInstance().addEventListener()`
 
-Refer to the [MoEngage - API reference](https://moengage.github.io/android-api-reference/moe-push-firebase/moe-push-firebase/com.moengage.firebase.listener/-firebase-event-listener/index.html) for more details on the listener.
+Refer to the [MoEngage - API reference](https://moengage.github.io/android-api-reference/moe-push-firebase/moe-push-firebase/com.moengage.firebase.listener/-firebase-event-listener/index.html){:target="_blank"} for more details on the listener.
 
 ##### Callbacks
 
 We recommend you to add the callbacks in the onCreate() of the Application class since these callbacks can be triggered even when the application is in the background.
 
 ###### Token Callback
 
-When MoEngage SDK handles push registration it optionally provides a callback to the application whenever a new token is registered or the token is refreshed. To get the token callback implement the [TokenAvailableListener](https://moengage.github.io/android-api-reference/pushbase/com.moengage.pushbase.listener/-token-available-listener/index.html) and register for the callback using [MoEFireBaseHelper.getInstance().addTokenListener()](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase/-mo-e-fire-base-helper/add-token-listener.html).
+When MoEngage SDK handles push registration, it optionally provides a callback to the application whenever a new token is registered or the token is refreshed. To get the token callback implement the [TokenAvailableListener](https://moengage.github.io/android-api-reference/pushbase/com.moengage.pushbase.listener/-token-available-listener/index.html){:target="_blank"} and register for the callback using [MoEFireBaseHelper.getInstance().addTokenListener()](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase/-mo-e-fire-base-helper/add-token-listener.html){:target="_blank"}.
 
 ###### Non-MoEngage Payload
 
-If you are using the receiver provided by the SDK in your application's manifest file, SDK provides a callback in case a push payload is received for any other server apart from MoEngage Platform. To get a callback implement the [NonMoEngagePushListener](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase.listener/-non-mo-engage-push-listener/index.html) and register for the callback using [MoEFireBaseHelper.getInstance().addNonMoEngagePushListener()](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase/-mo-e-fire-base-helper/add-non-mo-engage-push-listener.html).
+If you're using the receiver provided by the SDK in your application's manifest file, SDK provides a callback in case a push payload is received for any other server apart from MoEngage Platform. To get a callback implement the [NonMoEngagePushListener](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase.listener/-non-mo-engage-push-listener/index.html){:target="_blank"} and register for the callback using [MoEFireBaseHelper.getInstance().addNonMoEngagePushListener()](https://moengage.github.io/android-api-reference/moe-push-firebase/com.moengage.firebase/-mo-e-fire-base-helper/add-non-mo-engage-push-listener.html){:target="_blank"}.
 
 
 #### Declare and configure Rich Landing Activity:
 
 A rich landing page can be used to open a web URL inside the app via a push campaign.
 
-The below configuration is only required if you want to add a parent activity to the Rich landing page, if not you can move to the next section.
+The configuration below is only required if you want to add a parent activity to the Rich landing page. If not, you can move to the next section.
 To use a rich landing page you need to add the below code in the AndroidManifest.xml
 
 Add the following snippet and replace `[PARENT_ACTIVITY_NAME]` with the name of the parent
@@ -376,23 +376,23 @@ Add the following snippet and replace `[PARENT_ACTIVITY_NAME]` with the name of
 
 You are now all set up to receive push notifications from MoEngage. For more information on features provided in MoEngage Android SDK refer to the following links:
 
-* [Push Notifications](https://developers.moengage.com/hc/en-us/sections/360013606771-Push)
+* [Push Notifications](https://developers.moengage.com/hc/en-us/sections/360013606771-Push){:target="_blank"}
 
-* [Location Triggered](https://developers.moengage.com/hc/en-us/articles/4403443036564-Location-Triggered)
+* [Location Triggered](https://developers.moengage.com/hc/en-us/articles/4403443036564-Location-Triggered){:target="_blank"}
 
-* [In-App messaging](https://developers.moengage.com/hc/en-us/sections/360013831431-In-App-Messages)
+* [In-App messaging](https://developers.moengage.com/hc/en-us/sections/360013831431-In-App-Messages){:target="_blank"}
 
-* [Notification Center](https://developers.moengage.com/hc/en-us/articles/4403878923284-Notification-Center)
+* [Notification Center](https://developers.moengage.com/hc/en-us/articles/4403878923284-Notification-Center){:target="_blank"}
 
-* [API Reference](https://moengage.github.io/android-api-reference/index.html)
+* [API Reference](https://moengage.github.io/android-api-reference/index.html){:target="_blank"}
 
-* [Compliance](https://developers.moengage.com/hc/en-us/sections/4403894212116-Compliance)
+* [Compliance](https://developers.moengage.com/hc/en-us/sections/4403894212116-Compliance){:target="_blank"}
 
-* [Release Notes](https://developers.moengage.com/hc/en-us/articles/4403896795540-Changelog)
+* [Release Notes](https://developers.moengage.com/hc/en-us/articles/4403896795540-Changelog){:target="_blank"}
 
 
 ### Identify
-Use [Identify](/docs/connections/sources/catalog/libraries/mobile/android/#identify) to track user-specific attributes. This is the same as tracking [user attributes](http://docs.moengage.com/docs/identifying-user) on MoEngage. MoEngage supports traits supported by Segment as well as custom traits. If you set traits.id, MoEngage sets that as the Unique ID for that user.
+Use [Identify](/docs/connections/sources/catalog/libraries/mobile/android/#identify) to track user-specific attributes. This is the same as tracking [user attributes](http://docs.moengage.com/docs/identifying-user){:target="_blank"} on MoEngage. MoEngage supports traits supported by Segment as well as custom traits. If you set traits.id, MoEngage sets that as the Unique ID for that user.
 
 ### Track
 Use [track](/docs/connections/sources/catalog/libraries/mobile/android/#track) to track events and user behavior in your app.
@@ -403,7 +403,7 @@ If your app supports the ability for a user to logout and login with a new ident
 
 ### Sample Implementation
 
-Refer to [this](https://github.com/moengage/moengage-segment-integration) Github repository for sample implementation
+Refer to [this](https://github.com/moengage/moengage-segment-integration){:target="_blank"} Github repository for sample implementation
 
 ## Web
 
@@ -413,14 +413,14 @@ The MoEngage WebSDK offers the ability to send push notifications to Google Chro
 ### Integration
 
 #### 1. Setup your MoEngage Web SDK settings at MoEngage Dashboard
-Configure the [web settings](https://app.moengage.com/v3/#/settings/push/web) on the MoEngage dashboard to start using MoEngage <> Segment integration.
+Configure the [web settings](https://app.moengage.com/v3/#/settings/push/web){:target="_blank"} on the MoEngage dashboard to start using MoEngage <> Segment integration.
 
 If you have selected `HTTPS` mode of integration in the settings, complete the following steps:
 
 #### 2 Set up for HTTPS websites
 
 #### 2.a Download the required files (HTTPS)
-For HTTPS Web Push to work, you need to host two files in the `root` directory of your web server. These two files will be available for you to download at the [web settings page](https://app.moengage.com/v3/#/settings/push/web).
+For HTTPS Web Push to work, you need to host two files in the `root` directory of your web server. These two files will be available for you to download at the [web settings page](https://app.moengage.com/v3/#/settings/push/web){:target="_blank"}.
 * manifest.json
 * serviceworker.js
 
@@ -457,7 +457,7 @@ If you already have these files,
   ```
 
 ### Identify
-Use [Identify](/docs/sources/website/analytics.js/#identify) to track user specific attributes. This is equal to [tracking user attributes](https://docs.moengage.com/docs/tracking-web-user-attributes) on MoEngage. MoEngage supports traits supported by Segment as well as custom traits.
+Use [Identify](/docs/sources/website/analytics.js/#identify) to track user specific attributes. This is equal to [tracking user attributes](https://docs.moengage.com/docs/tracking-web-user-attributes){:target="_blank"} on MoEngage. MoEngage supports traits supported by Segment as well as custom traits.
 
 ### Track
 Use [track](/docs/sources/website/analytics.js/#track) to track events and user behavior in your app. This will send the event to MoEngage with the associated properties. Tracking events is essential and will help you create segments for engaging users.
@@ -467,9 +467,9 @@ If your website supports the ability for a user to logout and login with a new i
 
 ### Optional
 For information about optional feature, see the documentation below:
-* [Configure opt in type](https://docs.moengage.com/docs/configuring-notification-opt-in)
-* [Self-handled opt-ins](https://docs.moengage.com/docs/self-handled-opt-ins)
-* [SDK callbacks](https://docs.moengage.com/docs/tracking-opt-ins-on-your-own)
+* [Configure opt in type](https://docs.moengage.com/docs/configuring-notification-opt-in){:target="_blank"}
+* [Self-handled opt-ins](https://docs.moengage.com/docs/self-handled-opt-ins){:target="_blank"}
+* [SDK callbacks](https://docs.moengage.com/docs/tracking-opt-ins-on-your-own){:target="_blank"}
 
 ### Test Mode and Debugging
 While updating the MoEngage settings on the Segment Dashboard, you can enable the logging functionality of the MoEngage SDK to see the SDK logs on the browser console. Just set `Enable Debug Logging` to `On` and the SDK loads in debug mode.
