Fix tab headings

_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/implementation_guide.md

@@ -460,7 +460,7 @@ Content Cards can be used in a message center format where each message is its o
 For the following message types, the key-value pair `class_type` should be added to your dashboard configuration. The values assigned here are arbitrary but should be distinguishable between class types. These key-value pairs are the key identifiers that the application looks at when deciding where to go when the user clicks on an abridged inbox message.
 
 {% tabs local %}
-{% tab Arbitrary custom view message (full page) %}
+{% tab Arbitrary custom view message - full page %}
 
 The key-value pairs for this use case include:
 
@@ -470,7 +470,7 @@ The key-value pairs for this use case include:
 ![]({% image_buster /assets/img/cc_implementation/full_page.png %}){: style="max-width:60%;"}
 
 {% endtab %}
-{% tab Webview message (HTML) %}
+{% tab Webview message - HTML %}
 
 The key-value pairs for this use case include:
 

_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md

@@ -35,7 +35,7 @@ The following steps help you build a `BrazeManager` helper file that your produc
 ### Create BrazeManager.swift
 
 {% tabs local %}
-{% tab Create BrazeManager.swift %}
+{% tab Create BrazeManager swift %}
 
 ##### Create BrazeManager.swift
 To build out your `BrazeManager.swift` file, create a new Swift file named _BrazeManager_ to add to your project at your desired location. Next, Replace `import Foundation` with `import AppboyUI` for SPM (`import Appboy_iOS_SDK` for CocoaPods) and then create a `BrazeManager` class that will be used to host all Braze-related methods and variables. `Appboy_iOS_SDK`
@@ -100,7 +100,7 @@ class BrazeManager: NSObject {
 ### Initialize the SDK
 
 {% tabs local %}
-{% tab Step 1: Initialize SDK from BrazeManager.swift %}
+{% tab Step 1: Initialize SDK from BrazeManager swift %}
 
 ##### Initialize SDK from BrazeManager.swift
 Next, you must initialize the SDK. This guide assumes you have already [added the SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/overview/) into your Xcode project. You must also have your [workspace SDK endpoint]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/completing_integration/#step-2-specify-your-data-cluster) and [`LogLevel`]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#braze-log-level) set in your `Info.plist` file or in `appboyOptions`.

_docs/_developer_guide/platform_integration_guides/roku/analytics/setting_custom_attributes.md

@@ -50,7 +50,7 @@ m.Braze.setCustomAttribute("boolAttribute", true)
 m.Braze.setCustomAttribute("intAttribute", 5)
 ```
 {% endtab %}
-{% tab Float/Double %}
+{% tab Float or Double %}
 ```brightscript
 m.Braze.setCustomAttribute("floatAttribute", 3.5)
 ```

_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/delayed_initialization.md

@@ -26,7 +26,7 @@ The Swift SDK does not capture non-Braze push notifications—these will con
 {% endalert %}
 
 {% tabs %}
-{% tab Swift (UIKit) %}
+{% tab Swift - UIKit %}
 ```swift
 func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
   // Prepare the SDK for delayed initialization
@@ -39,7 +39,7 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 ```
 {% endtab %}
 
-{% tab Swift (SwiftUI) %}
+{% tab Swift - SwiftUI %}
 SwiftUI applications require implementing the [@UIApplicationDelegateAdaptor](https://developer.apple.com/documentation/swiftui/uiapplicationdelegateadaptor) property wrapper to call the `prepareForDelayedInitialization()` method.
 
 ```swift

_docs/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md

@@ -52,7 +52,7 @@ bool SetCustomAttribute(STRING_KEY, BOOL_VALUE);
 bool SetCustomAttribute(STRING_KEY, INT_VALUE);
 ```
 {% endtab %}
-{% tab Double/Float %}
+{% tab Double or Float %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, DOUBLE_VALUE);
 ```

_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md

@@ -144,7 +144,7 @@ Not all fields offered are required.
 {% endalert %}
 
 {% tabs local %}
-{% tab Track User (Batch and Non-Batch) %}
+{% tab Track User - Batch and Non-Batch %}
 
 This action allows you to track user, event, and purchase attributes all in one action. Although the Track User action is the same for both AudienceStream and EventStream, Tealium recommends setting user attribute mappings with AudienceStream actions and the event and purchase mappings with EventStream actions.
 
@@ -164,7 +164,7 @@ This action allows you to track user, event, and purchase attributes all in one
 ![]({% image_buster /assets/img/tealium/track_user_example2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab Delete User (Non-Batch) %}
+{% tab Delete User - Non-Batch %}
 
 This action allows you to delete users from the Braze dashboard.
 
@@ -176,7 +176,7 @@ This action allows you to delete users from the Braze dashboard.
 ![]({% image_buster /assets/img/tealium/track_user_delete2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab Update User Subscription Group Status (Non-Batch) %}
+{% tab Update User Subscription Group Status - Non-Batch %}
 This action allows you to add or remove users from Braze SMS or email subscription groups.
 
 | Parameters | Description |

_docs/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md

@@ -280,7 +280,7 @@ In addition to creating and updating passes, you can also retrieve your users' p
 **Liquid example responses**
 
 {% tabs local %}
-{% tab passes.redemptionDetails %}
+{% tab passes redemptionDetails %}
 
 ```json
 {
@@ -297,7 +297,7 @@ In addition to creating and updating passes, you can also retrieve your users' p
 ```
 
 {% endtab %}
-{% tab passes.status %}
+{% tab passes status %}
 ```
 UNREDEEMED 
 ```

_docs/_partners/message_personalization/dynamic_content/future_anthem.md

@@ -97,7 +97,7 @@ These are the available Braze custom attributes. For more detailed information,
 {: .reset-td-br-1 .reset-td-br-2}
 {% endtab %}
 
-{% tab Player Sustain (Player potential risk) %}
+{% tab Player Sustain - Player potential risk %}
 
 | Subcategory | Example | Datatype |
 | ------- | ----------- |----------- |

_docs/_partners/message_personalization/dynamic_content/komo.md

@@ -31,14 +31,14 @@ The Braze and Komo integration allows you to gather first and zero-party data th
 ## Use cases
 
 {% tabs local %}
-{% tab Data Capture (Form Submission) %}
+{% tab Data Capture - Form Submission %}
 
 When a user submits a customizable data capture form in Komo, the Komo fields mapped in the Braze integration will be passed to Braze via the `/users/track/` API call.
 
 Data capture forms exist either at the start or end of Cards.
 
 {% endtab %}
-{% tab Market Research (Coming soon) %}
+{% tab Market Research - Coming soon %}
 
 Coming soon, Komo will be adding the ability to pass through market research data captured when a user answers a quiz question, poll, personality test, swiper, etc. This data will enable you to enhance a user's profile beyond data captured in form submissions.
 

_docs/_user_guide/data_and_analytics/reporting/data_by_segments.md

@@ -134,7 +134,7 @@ Your results will show purchase metrics by segment for the variants or steps you
 - **Columns:** Purchase metrics
 
 {% endtab %}
-{% tab Top/bottom messaging for email engagement %}
+{% tab Top or bottom messaging for email engagement %}
 
 ### Viewing metrics for the top or bottom performers
 
@@ -168,7 +168,7 @@ To view this report, you must specify the following variables in the **Variables
 Your results will show the top (or bottom) campaigns, Canvases, or Canvas steps that you selected. For example, if you selected the top 10 campaigns for click rate, your results will show the top 10 campaigns ordered from highest to lowest click rate. Your columns will display all of the email engagement metrics for each row (campaigns, Canvases, or Message steps).
 
 {% endtab %}
-{% tab Top/bottom messaging for purchases %}
+{% tab Top or bottom messaging for purchases %}
 
 ### Viewing metrics for the top or bottom performers
 
@@ -207,7 +207,7 @@ Your results will show the top (or bottom) campaigns, Canvases, or Canvas steps
 {% endtab %}
 {% tab Push performance by segment %}
 
-## Viewing push metrics for segments
+### Viewing push metrics for segments
 
 This report in the [Variables](#variables) tab displays push metrics broken down by segments. 
 

_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc.md

@@ -104,9 +104,9 @@ A declared use case means you have chosen one specific non-marketing use case (f
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 {% endtab %}
-{% tab Mixed/Marketing Use Case %}
+{% tab Mixed Marketing Use Case %}
 
-Mixed/Marketing use cases can be registered for customers who want to send messages for multiple use cases from the same set of numbers or for marketing.
+Mixed marketing use cases can be registered for customers who want to send messages for multiple use cases from the same set of numbers or for marketing.
 
 | Trust Score | Total throughput toward major US networks | AT&T | T-Mobile  | Verizon |
 | --- | ----------- | ---- | -------- | ------- |