Merge pull request #8098 from lopenchi/DOCSPLAT-3061

Small fixes - Batch 5.4 migration

Author: pwseg

src/_includes/content/papi-ga.html renamed to src/_includes/content/papi-ga.md

@@ -2,7 +2,7 @@
 title: API Design
 ---
 
-{% include content/papi-ga.html %}
+{% include content/papi-ga.md %}
 
 ## API Evolution: Versioning and Compatibility
 
@@ -28,13 +28,13 @@ The Config API is a set of REST APIs for managing Segment resources. The primary
 
 You can manage each resource using standard methods:
 
-| Method | HTTP Mapping          |
-|--------|-----------------------|
-| List   | GET <collection URL>  |
-| Get    | GET <resource URL>    |
-| Create | POST <collection URL> |
-| Update | PATCH <resource URL>  |
-| Delete | DELETE <resource URL> |
+| Method | HTTP Mapping           |
+|--------|------------------------|
+| List   | GET \<collection URL>  |
+| Get    | GET \<resource URL>    |
+| Create | POST \<collection URL> |
+| Update | PATCH \<resource URL>  |
+| Delete | DELETE \<resource URL> |
 
 ## Errors
 

src/api/config-api/api-design.md

@@ -2,7 +2,7 @@
 title: Authentication
 ---
 
-{% include content/papi-ga.html %}
+{% include content/papi-ga.md %}
 
 
 You can access the Config API programmatically using access tokens. When you authenticate with an access token, you have access to any resource and permission assigned to the token.

src/api/config-api/authentication.md

@@ -4,7 +4,7 @@ redirect_from:
   - '/config-api'
 ---
 
-{% include content/papi-ga.html %}
+{% include content/papi-ga.md %}
 
 The Config API lets you programmatically manage Segment workspaces, sources, destinations, and more. 
 

src/api/config-api/index.md

@@ -5,7 +5,7 @@ redirect_from:
   - /api/config-api/fql
 ---
 
-{% include content/papi-ga.html %}
+{% include content/papi-ga.md %}
 
 This reference provides a comprehensive overview of the Segment Destination Filter query language. For information on the Destination Filters API (including information on migrating from the Config API), visit the [Destination Filters API reference](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}.
 

src/api/public-api/fql.md

@@ -29,7 +29,7 @@ This destination is maintained by ABsmartly. For any issues with the destination
 > info ""
 > If you need support setting things up, you can contact the ABsmartly support team on Slack or [via email](mailto:support@absmartly.com).
 
-# Sending exposures to Segment
+## Sending exposures to Segment
 
 It can be useful to send experiment exposures to Segment for visibility from
 other destinations. The Segment Spec includes the [Experiment Viewed semantic event](/docs/connections/spec/ab-testing/)

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

@@ -29,7 +29,7 @@ Braze web-mode (Actions) provides the following benefits over Braze (Classic):
 3. Choose which of your sources to connect the destination to and follow the steps to create your destination.
 > warning "Mapping settings"
 > Some events require specific property names to map correctly into Braze. 
-> For example, purchase events must use a `products` array with `product_id` and `price.
+> For example, purchase events must use a `products` array with `product_id` and `price`.
 > See [Braze-web settings mappings](#braze-web-settings-mapping) for "Device-web" for the full list of requirements before setting up mappings.
 4. In the **Settings** tab, configure the connection settings. **API Key**, **SDK Endpoint**, and **REST Endpoint** are required settings.
 

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

@@ -632,7 +632,3 @@ These examples show key moments in the journey, from entry to conversion milesto
 ```
 {% endcodeexampletab %}
 {% endcodeexample %}
-
-
-
--->