Merge branch 'master' into impact-partnership-cloud

Author: pauljaeinyoo

src/connections/destinations/catalog/adobe-analytics/mobile.md

@@ -12,20 +12,36 @@ To learn more about Segment's mobile libraries, see the [iOS](/docs/connections/
 
 Before you start sending data from your mobile application to Adobe Analytics, you must first finish the following set up steps:
 
-- First, enable the Segment-Adobe Analytics destination from in your Segment workspace
+- First, enable the Segment-Adobe Analytics destination from in your Segment workspace.
 - From your Adobe Mobile Services dashboard, check and customize the settings on the "Manage App Settings" tab.
-- Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's documentation, [here for iOS](https://marketing.adobe.com/resources/help/en_US/mobile/ios/dev_qs.html), and [here for Android](https://marketing.adobe.com/resources/help/en_US/mobile/android/dev_qs.html)
+- Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's documentation [here for iOS](https://marketing.adobe.com/resources/help/en_US/mobile/ios/dev_qs.html) and [here for Android](https://marketing.adobe.com/resources/help/en_US/mobile/android/dev_qs.html).
 - Finally, follow the instructions below for each mobile environment to bundle Segment's Adobe Analytics SDK in your project.
 
 > success ""
 > **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
 
 #### For Android
+
+```java
+compile 'com.segment.analytics.android.integrations:adobeanalytics:+'
+```
+
+After you add the dependency, register the integration with the Segment SDK. To do this, import the Amplitude integration:
+
 ```java
-compile 'com.segment.analytics.android.integrations:adobe-analytics:1.0.0'
+import com.segment.analytics.android.integrations.adobeanalytics.AdobeIntegration;
 ```
 
-**Note** If you're working on Android, you'll also need to add these permissions to your `AndroidManifest.xml`:
+Then add the following line:
+
+```java
+analytics = new Analytics.Builder(this, "write_key")
+                .use(AdobeIntegration.FACTORY)
+                .build();
+```
+
+> info ""
+> **Note:** If you're working on Android, be sure to add these permissions to your `AndroidManifest.xml`:
 
 ```xml
 <uses-permission android:name="android.permission.INTERNET" />
@@ -35,11 +51,9 @@ compile 'com.segment.analytics.android.integrations:adobe-analytics:1.0.0'
 You can see the [Android SDK changelog](https://github.com/segment-integrations/analytics-android-integration-adobe-analytics/blob/master/CHANGELOG.md) in the open-source repository for information about specific versions of the Android Adobe Analytics SDK.
 
 #### For iOS
+
 ```objc
 pod 'Segment-Adobe-Analytics'
-iOS:
-```objc
-pod 'Segment-Adobe-Analytics', '1.1.0-beta'
 ```
 
 You can see the [iOS SDK changelog](https://github.com/segment-integrations/analytics-ios-integration-adobe-analytics/blob/master/Changelog.md) in the open-source repository for information about specific versions of the iOS Adobe Analytics SDK.

src/connections/storage/warehouses/schema.md

@@ -25,7 +25,7 @@ The table below describes the schema in Segment Warehouses:
   </tr>
   <tr>
     <td>`<source>.users`</td>
-    <td>A table with unique `identify` calls. `identify` calls are upserted on `user_id` into this table (updated if an existing entry exists, appended otherwise). This table holds the latest state of a user. The `id` column in the users table is the same as the `user_id` column in the identifies table. Also note that this table won't have an `anonymous_id` column since a user can have multiple anonymousIds. To get at a user's anonymousIds, you'll need to query the identifies table. *If you observe any duplicates in the users table, [contact us](https://segment.com/help/contact/).*</td>
+    <td>A table with unique `identify` calls. `identify` calls are upserted on `user_id` into this table (updated if an existing entry exists, appended otherwise). This table holds the latest state of a user. The `id` column in the users table is the same as the `user_id` column in the identifies table. Also note that this table won't have an `anonymous_id` column since a user can have multiple anonymousIds. To get at a user's anonymousIds, you'll need to query the identifies table. *If you observe any duplicates in the users table [contact us](https://segment.com/help/contact/) (unless you are using Bigquery, where [this is expected](/docs/connections/storage/catalog/bigquery/#schema)).*</td>
   </tr>
   <tr>
     <td>`<source>.pages`</td>