Merge pull request #505 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/destinations/catalog/actions-facebook-conversions-api/index.md

@@ -66,23 +66,7 @@ Set up your Pixel to work with the Facebook Conversions API (Actions) destinatio
 
 ## Configuration options
 
-The Facebook Conversions API (Actions) destination gives you several ways to implement your conversion tracking. You can use it with [Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/), or as a stand-alone alternative. You can read more about implementation options below and in [Facebook documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/guides/end-to-end-implementation#pick-your-integration-type){:target="_blank"}.
-
-### Action Source
-
-`action_source` is set to "website" as a default value.
-
-You can set `action_source` manually by passing it as a property of a Track event. You can use either snake case or camel case to include `action_source` as a property in Track events.
-
-| Action Source Values | Description                                                                                               |
-| -------------------- | --------------------------------------------------------------------------------------------------------- |
-| `chat`               | Conversion was made through a messaging app, SMS, or online messaging feature.                                |
-| `email`              | Conversion happened over email.                                                                           |
-| `other`              | Conversion happened in a way that is not listed.                                                          |
-| `phone_call`         | Conversion was made over the phone.                                                                       |
-| `physical_store`     | Conversion was made in person at your physical store.                                                     |
-| `system_generated`   | Conversion happened automatically, for example, a subscription renewal that's set on auto-pay each month. |
-| `website`            | Conversion was made on your website.                                                                      |
+The Facebook Conversions API (Actions) destination gives you several ways to implement your conversion tracking. You can use it with [Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/), or as a stand-alone alternative. You can read more about implementation options below and in [Facebook documentation](https://developers.facebook.com/docs/marketing-api/conversions-api/guides/end-to-end-implementation#pick-your-integration-type){:target="_blank"}.                                                               |
 
 ### Send events from both the browser and the server
 

src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md

@@ -446,21 +446,21 @@ If Segment doesn't support your Kotlin destination, you can build your own with
 
 To build your own Kotlin destination using a plugin template:
 
-1. Go to the [Kotlin Destination Plugin Template](https://github.com/segmentio/kotlin-destination-templates){:target="_blank"}.
+1. Go to the [Kotlin Destination Plugin Template](https://github.com/segment-integrations/analytics-kotlin-destination-template){:target="_blank"}.
 2. Click **Use this template**.
 3. Enter a name for the repository.
 4. Click **Create repository from template**.
-5. Go to **destination > src > main > java/dmn/your/pkg/destination** in your repository.
-6. Click the **ExampleDestination.kt**.
+5. Go to **lib > src > main > java/dmn/your/pkg/destination** in your repository.
+6. Click the **MyDestination.kt**.
 7. Complete the `TODO` sections in the sample code with the appropriate information for your destination. Segment recommends you to change the package name before you finalize your build.
 8. Commit your changes.
 
 You can unit test your destination to make sure it works. Segment recommends you to use the testing template as a starter and to build upon it to get test coverage of most scenarios.
 
 To test your destination:
 
-1. Go to **destination > src > test > java/dmn/your/pkg/destination**.
-2. Click **ExampleDestinationTests.kt**.
+1. Go to **lib > src > test > java/dmn/your/pkg/destination**.
+2. Click **MyDestinationTests.kt**.
 3. Complete the `TODO` sections in the sample code with the appropriate information for your destination.
 4. Commit your changes.