Merge pull request #8015 from segmentio/DOCSPLAT-2981

DOCSPLAT 2981 Changes to simplify migration

Author: pwseg

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

@@ -14,7 +14,7 @@ To configure CommandBar as an Event Source to get data into your warehouse or ot
 1. From the Segment web app, navigate to **Connections > Catalog**, then select the **Destinations** tab at the top of the catalog.
 2. Search for *CommandBar* and select it.
 3. Click **Configure CommandBar**.
-4. Sign in to [CommandBar](app.commandbar.com/login){:target="_blank"}, click on your organization name in the top right, and copy the `Org ID` into **Organization ID** field.
+4. Sign in to [CommandBar](https://app.commandbar.com/login){:target="_blank"}, click on your organization name in the top right, and copy the `Org ID` into **Organization ID** field.
 5. If you want to deploy CommandBar to your users through Segment, check **Deploy via Segment**.
 6. Select an existing Source to connect to CommandBar.
 7. Once connected, remove the CommandBar snippet or `init` call from your code (if you have one).

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

@@ -12,7 +12,7 @@ This destination is maintained by Plotline. For any issues with the destination,
 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Plotline".
 2. Select and click **Add Destination**.
 3. Select an existing source to connect to.
-4. Go to [Plotline's dashboard](app.plotline.so){:target="_blank”}, navigate to "Credentials" and copy the API key.
+4. Go to [Plotline's dashboard](https://app.plotline.so){:target="_blank”}, navigate to "Credentials" and copy the API key.
 5. Enter the API Key in the destination settings in Segment.
 
 ## Supported methods

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

@@ -33,7 +33,7 @@ It takes only three steps to set everything up and start surveying your audience
 ### 3. Map survey campaign with Segment events
 
 1. In the Retently destination settings in the Segment app, go to the **Map Retently campaigns with Segment events** section.
-2. In the left input field, enter the ID of the survey campaign. [Learn how to configure the survey campaign.](hhttps://help.retently.com/en/articles/8217913-trigger-transactional-surveys-via-segment-events){:target="_blank"}
+2. In the left input field, enter the ID of the survey campaign. [Learn how to configure the survey campaign.](https://help.retently.com/en/articles/8217913-trigger-transactional-surveys-via-segment-events){:target="_blank"}
 3. In the right field, list the name of one or more Segment Track events that should trigger the survey in the specified campaign.
    Write the name of the event exactly as it's written in the `analytics.track` method (more details in the section below). You can enter multiple Track events by separating them with a comma symbol (for example Order Placed, Dashboard Visited).
 

src/connections/sources/catalog/cloud-apps/gwen-webhooks/index.md

@@ -5,7 +5,7 @@ id: vMEJCURfHh
 
 [GWEN Webhooks](https://gwenplatform.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="blank"} offers powerful gamification tools and insights to convert, engage, and retain users. With GWEN it has never been easier to understand your users behavior patterns and build better performing products with both speed and accuracy.
 
-This is an [Event Cloud Source](=/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.
+This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.
 
 This source is maintained by Insert Coin AB. For any issues with the source, [contact their Support team](mailto:[email protected]).
 
@@ -20,11 +20,11 @@ This source is maintained by Insert Coin AB. For any issues with the source, [co
    - The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, SourceName_Prod, SourceName_Staging, or SourceName_Dev).
 4. Click **Add Source** to save your settings.
 5. Copy the Write key from the Segment UI and log in to your GWEN account.
-6. Navigate to [Setup Management > Webhooks](http://app.gwenplatform/setup-management/webhooks){:target="blank"} and click the **Set credentials** button next to **Segment Source webhooks**. Paste the key to connect.
+6. Navigate to [Setup Management > Webhooks](https://app.gwenplatform.com/setup-management/webhooks){:target="blank"} and click the **Set credentials** button next to **Segment Source webhooks**. Paste the key to connect.
 
 ## Stream
 
-GWEN Webhooks uses a stream Source component to send Segment event data. It uses a server-side (select from `track`, `identify`, `page`, `group`) method(s) to send GWEN user data to Segment (Read more about GWEN webhook data [in the GWEN documentation](app.gwenplatform.com/docs/webhooks/segment)). These events are then available in any destination that accepts server-side events, and also available in a schema in your data warehouse, so you can query using SQL.
+GWEN Webhooks uses a stream Source component to send Segment event data. It uses a server-side (select from `track`, `identify`, `page`, `group`) method(s) to send GWEN user data to Segment (Read more about GWEN webhook data [in the GWEN documentation](https://app.gwenplatform.com/docs/webhooks/segment)). These events are then available in any destination that accepts server-side events, and also available in a schema in your data warehouse, so you can query using SQL.
 
 The default behavior is for GWEN Webhooks to pass the userId associated with the user who triggered the given update. This may or may not be a userId that you are keeping track of, depending on under what circumstances the user has been created within GWEN.
 For example, users created anonymously by using the [GWEN Analytics script](https://app.gwenplatform.com/docs/gwen-analytics){:target="blank"} will likely have a userId unknown to you.

src/connections/sources/catalog/cloud-apps/one-creation/index.md

@@ -45,6 +45,7 @@ The following table lists events that One Creation sends to Segment. These event
 
 All One Creation events contain the associated One Creation campaign name, campaign ID, user ID of the individual who responded to the campaign, and the list of traits or properties that the user provided through this campaign. Here's a sample payload:
 
+```json
     {
         "properties": {
             "fav_color": "blue",
@@ -68,6 +69,7 @@ All One Creation events contain the associated One Creation campaign name, campa
         "userId": "75720996-3c82-4cc4-b0e5-67bd441fa9f3",
         "type": "track"
     }
+```
 
 ## Adding destinations