Merge pull request #8038 from elemhunt/develop

Batch 6.4 Migration Adjustments Part 3

Author: forstisabella

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

@@ -7,7 +7,7 @@ id: 5f354f1a928763feb8caf724
 
 This destination is maintained by Stonly. For any issues with the destination, [contact their support team](mailto:support@stonly.com).
 
-> "Note:"
+> info ""
 > Stonly Destination is currently in beta, which means that they are still actively developing the destination. To join their beta program, or if you have any feedback to help improve Stonly Destination and its documentation, [contact Stonly support team](mailto:support@stonly.com)!
 
 ## Getting Started
@@ -61,8 +61,6 @@ Segment sends Track calls to Stonly as a `track` event.
 
 If one of your properties is of the date property type, it should be sent as an ISO string.
 
----
-
 ## Troubleshooting
 
 ### Nested Objects and Arrays

src/connections/destinations/catalog/tag-injector/index.md

@@ -15,14 +15,14 @@ _**NOTE:** Tag Injector is only available for select customers at this time._
 
 1. Once you have access, with the link provided confirm the Source you'd like to connect to.
 2. You have the following configuration options which will manipulate the page at runtime:
-  - **URL**: A URL to the JavaScript code to load on the page as the `src` attribute of the `<script>` tag.
-  - **Merge Variable**: A global variable that can be modified or created at runtime.
+    - **URL**: A URL to the JavaScript code to load on the page as the `src` attribute of the `<script>` tag.
+    - **Merge Variable**: A global variable that can be modified or created at runtime.
 3. You can also configure global variables, which the Tag Injector can manipulate in a user-specified way using Merge Variable tags. These Merge Variable tags support two fields:
-  - Variable Name indicates what global variable to operate on.
-  - Tag Value specifies what values should be merged into the global variable.
+    - Variable Name indicates what global variable to operate on.
+    - Tag Value specifies what values should be merged into the global variable.
 4. For each Merge Variable tag, the Tag Injector will inject code which will have the behavior as follows. For this example, let us call the global variable with the name specified in Variable Name _the global variable to modify_.
-  - If the global variable to modify does not yet exist, it is created and initialized to the value described in Tag Value.
-  - If the global variable to modify already exists, its value is merged with the value described in Tag Value. This merging process will be implemented using a custom function.
+    - If the global variable to modify does not yet exist, it is created and initialized to the value described in Tag Value.
+    - If the global variable to modify already exists, its value is merged with the value described in Tag Value. This merging process will be implemented using a custom function.
 
 
 ## Best Practices

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

@@ -16,8 +16,6 @@ For our client-side Javascript library (Analytics.js) that means you need to cal
 
 For server-side and mobile libraries you must include `context.groupId` in every call you want to be sent through to Totango so they can connect the dots between a call made to Segment and an account in their system.
 
-- - -
-
 ## Group
 
 Totango also needs to know what "account" the user belongs to. To record this, you'd use our [`group`](/docs/connections/spec/group/) method. Group also takes a unique ID (for the group this time!) and a dictionary of properties about the group. It looks like this:
@@ -104,8 +102,6 @@ To learn more about how [`track`](/docs/connections/spec/track/) works check out
 
 **If you're sending data using the server-side or mobile libraries**, you'll need to include `context.groupId`. Check out the [troubleshooting](#troubleshooting) section to see how.
 
-- - -
-
 
 ## Troubleshooting
 

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

@@ -68,4 +68,3 @@ The following `track` calls will be sent to TrafficGuard as events.
 
 All other calls will be recorded as `pageview` events until TrafficGuard supports ad hoc event types.
 
----