move ajs 2 upgrade blurbs

Author: markzegarelli

src/connections/destinations/actions.md

@@ -79,6 +79,9 @@ To set up a new Actions-framework destination for the first time:
 
 ## Migrate a classic destination to an actions-based destination
 
+{% include content/ajs-upgrade.md %}
+
+
 Moving from a classic destination to an actions-based destination is a manual process. Segment recommends that you follow the procedure below:
 
 1. Create the actions-based destination with your development or test source.

src/connections/destinations/catalog/actions-amplitude/index.md

@@ -27,8 +27,6 @@ Amplitude (Actions) provides the following benefits over the classic Amplitude d
 - **Session tracking in cloud-mode**. Amplitude (Actions) supports sending session details from cloud-mode sources.
 
 ## Getting started
-{% include content/ajs-upgrade.md %}
-
 
 1. Before you start, go to your [Amplitude workspace](https://analytics.amplitude.com){:target="_blank"}. Click **Settings** in the bottom left, then click **Projects** in the left menu. Select your **Project**. Copy the Amplitude API Key and Secret Key for the project.
 2. From the Segment web app, click **Catalog**, then click **Destinations**.
@@ -305,6 +303,8 @@ To use Amplitude's groups with Segment, you must enable the following Action set
 
 ## Migration from Amplitude Classic
 
+{% include content/ajs-upgrade.md %}
+
 Keep the following in mind if you plan to move to Amplitude (Actions) from a classic Amplitude destination.
 
 ### Amplitude (Actions) uses Amplitude's HTTP API v2

src/connections/destinations/catalog/actions-braze-cloud/index.md

@@ -23,7 +23,6 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
 - **E-commerce mappings**. Segment implementations that don't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can use Event Triggers to log purchases in Braze Cloud Mode (Actions).
 
 ## Getting Started
-{% include content/ajs-upgrade.md %}
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Braze" in the Catalog, select **Braze Cloud Mode (Actions)**, and choose which of your sources to connect the destination to.
@@ -54,6 +53,9 @@ Build your own subscription. Combine the supported [triggers](/docs/connections/
 {% include components/actions-fields.html name="braze-cloud" %}
 
 ## Migration from Braze Classic
+
+{% include content/ajs-upgrade.md %}
+
 Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
 {% include components/actions-map-table.html name="braze-cloud" %}
 

src/connections/destinations/catalog/actions-braze-web/index.md

@@ -23,8 +23,6 @@ Braze Web Mode (Actions) provides the following benefits over Braze Classic:
 - **E-commerce mappings**. Users who can't follow the e-commerce spec due to incompatible event names (for example, Trip Booked vs Order Completed) can log purchases in Braze Web Mode (Actions).
 
 ## Getting Started
-{% include content/ajs-upgrade.md %}
-
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Braze" in the Catalog, select **Braze Web Mode (Actions)**, and choose which of your sources to connect the destination to.
@@ -184,6 +182,9 @@ Build your own subscription. Combine the supported [triggers](/docs/connections/
 {% include components/actions-fields.html name="braze-web" %}
 
 ## Migration from Braze Classic
+
+{% include content/ajs-upgrade.md %}
+
 Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
 {% include components/actions-map-table.html name="braze-web" %}
 

src/connections/destinations/catalog/actions-customer-io/index.md

@@ -23,8 +23,6 @@ redirect_from:
 - **Track an anonymous event**. Track events from users who are not yet known to Customer.io. If you have the Customer.io *event merging* feature enabled, Customer.io associates all incoming events that share an `anonymous_id` received in the last 30 days.
 
 ## Getting started
-{% include content/ajs-upgrade.md %}
-
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**.
 2. Find the Destinations Actions item in the left navigation, and click it.
@@ -56,5 +54,8 @@ Build your own subscription. Combine the supported [triggers](/docs/connections/
 
 ## Migration from Customer.io classic
 
+{% include content/ajs-upgrade.md %}
+
+
 Keep the following in mind if you plan to move to Customer.io (Actions) from the classic Customer.io destination.
 {% include components/actions-map-table.html name="customer-io" %}

src/connections/destinations/catalog/actions-fullstory/index.md

@@ -17,8 +17,6 @@ hide-dossier: true
 
 
 ## Getting started
-{% include content/ajs-upgrade.md %}
-
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**.
 2. Find the Destinations Actions item in the left navigation, and click it.
@@ -51,6 +49,9 @@ Combine the supported [triggers](/docs/connections/destinations/actions/#compone
 {% include components/actions-fields.html name="fullstory" %}
 
 ## Migration from the classic FullStory destination
+{% include content/ajs-upgrade.md %}
+
+
 
 Follow the table below to map your existing FullStory destination configuration to FullStory (Actions).
 

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

@@ -46,6 +46,9 @@ Combine the supported [triggers](/docs/connections/destinations/actions/#compone
 
 ## Migration from the classic Slack destination
 
+{% include content/ajs-upgrade.md %}
+
+
 Follow the table below to map your existing Slack destination configuration to Slack (Actions).
 
 > warning ""