Lint fixed part 1

src/pages/documentation/adobe-journey-optimizer/public-classes-and-enum/message.md

@@ -27,7 +27,6 @@ Identifier of the `Message`. This value matches the Message Execution ID assigne
 public var id: String
 ```
 
-
 ### autoTrack
 
 If set to `true` (default), Experience Edge events will automatically be generated when this `Message` is triggered, displayed, and dismissed.
@@ -70,7 +69,6 @@ iOS
 
 <Tabs query="platform=ios&function=dismiss"/>
 
-
 ### track(_:withEdgeEventType:)
 
 Generates and dispatches an Edge Event for the provided `interaction` and `eventType`.
@@ -190,4 +188,3 @@ Returns a reference to the message's  `WebView`  instance, if it exists.
 ```java
 WebView getWebView()
 ```
-

src/pages/documentation/adobe-journey-optimizer/public-classes-and-enum/messaging-edge-event-type.md

@@ -34,4 +34,4 @@ Android
 
 iOS
 
-<Tabs query="platform=ios&function=string-values"/>
+<Tabs query="platform=ios&function=string-values"/>

src/pages/documentation/adobe-journey-optimizer/public-classes-and-enum/push-tracking-status.md

@@ -38,4 +38,4 @@ Android
 
 iOS
 
-<Tabs query="platform=ios&function=string-values"/>
+<Tabs query="platform=ios&function=string-values"/>

src/pages/documentation/adobe-journey-optimizer/push-notification/android/automatic-display-and-tracking.md

@@ -24,7 +24,6 @@ This document describes how to automatically display and track push notification
 
 To retrieve the push token from Firebase Messaging Service, please follow the tutorial within the [Firebase documentation](https://firebase.google.com/docs/cloud-messaging/android/client#retrieve-the-current-registration-token). Then use `setPushIdentifier` API to sync the device's push token with profile in Adobe Experience Platform.
 
-
 <InlineAlert variant="info" slots="text"/>
 
 Although this API is provided in Mobile Core, the use of this API is required and leveraged by the Adobe Journey Optimizer extension to sync provided push tokens with Adobe Experience Platform services.
@@ -92,6 +91,7 @@ Notification channel was introduced in Android Oreo (API level 26). It allows yo
 
 You must create at least one notification channel to display push notifications on devices running Android Oreo or higher. Follow the [android documentation](https://developer.android.com/develop/ui/views/notifications/channels) to create and manage notification channels. Once a notification channel is created, you can use the channel id while [designing the push notification](https://experienceleague.adobe.com/docs/journey-optimizer/using/push/design-push.html) in Adobe Journey Optimizer.
 
+
 **Default Channel**: If you do not create a notification channel, or if the notification channel specified while designing the push notification does not match with any of the created channels, the Messaging extension will present the push notification through its predefined fallback notification channel, which is named "General Notifications."
 
 ## Configuring Small Icon
@@ -101,7 +101,8 @@ Use MobileCore's API to set the small icon resource id. This icon will be used a
 ```java
 MobileCore.setSmallIconResourceId(R.drawable.ic_notification);
 ```
+
 When no custom small icon is specified, the Messaging extension will automatically utilize the application's launcher icon as the default small icon.
 
 ## Notification Actions
-Messaging extension will automatically handle any click behaviour that is configured while [designing the push notification in Adobe Journey Optimizer](https://experienceleague.adobe.com/docs/journey-optimizer/using/push/design-push.html) or Assurance.
+Messaging extension will automatically handle any click behaviour that is configured while [designing the push notification in Adobe Journey Optimizer](https://experienceleague.adobe.com/docs/journey-optimizer/using/push/design-push.html) or Assurance.

src/pages/documentation/adobe-journey-optimizer/push-notification/android/manual-display-and-tracking.md

@@ -21,7 +21,6 @@ This document describes how to manually build, display and track push notificati
 
 To retrieve the push token from Firebase Messaging Service, please follow the tutorial within the [Firebase documentation](https://firebase.google.com/docs/cloud-messaging/android/client#retrieve-the-current-registration-token). Then use `setPushIdentifier` API to sync the device's push token with profile in Adobe Experience Platform.
 
-
 <InlineAlert variant="info" slots="text"/>
 
 Although this API is provided in Mobile Core, the use of this API is required and leveraged by the Adobe Journey Optimizer extension to sync provided push tokens with Adobe Experience Platform services.
@@ -79,6 +78,7 @@ public class YourApp extends Application {
 4. Use NotificationManager to create and display the built notification.
 
 Here is a sample code for creating a notification channel and building the notification.
+
 ```java
 public class YourAppFirebaseMessagingService extends FirebaseMessagingService {
 
@@ -124,21 +124,24 @@ After the application is opened by the user by clicking on the push notification
         final String actionId) // actionId of the element which performed the custom action.
 ```
 
-##### Sending push notification interaction feedback when application is opened without any custom action. 
+##### Sending push notification interaction feedback when application is opened without any custom action
+
 Add the following code where you have access to `intent` after the user has interacted with the push notification:
 
 ```java
 Messaging.handleNotificationResponse(intent, true, null);
 ```
 
-##### Sending feedback when application is opened with a custom action. 
+##### Sending feedback when application is opened with a custom action
+
 Similar to the example above, call the `handleNotificationResponse` API but this time with a custom action:
 
 ```java
 Messaging.handleNotificationResponse(intent, true, <actionId>);
 ```
 
-##### Sending feedback when application is not opened but a custom action is performed by the user. 
+##### Sending feedback when application is not opened but a custom action is performed by the user
+
 Add the following code where you have access to `intent` after the user has interacted with the push notification:
 
 ```java
@@ -165,4 +168,4 @@ public class MainActivity extends AppCompatActivity {
         }
     }
 }
-```
+```

src/pages/documentation/adobe-journey-optimizer/push-notification/index.md

@@ -22,4 +22,4 @@ keywords:
 * [Enum - PushTrackingStatus](../public-classes-and-enum/push-tracking-status.md)
 
 ## More Information
-* [Push Notification Payload Keys](./push-payload.md)
+* [Push Notification Payload Keys](./push-payload.md)

src/pages/documentation/adobe-journey-optimizer/push-notification/push-payload.md

@@ -21,4 +21,4 @@ Android
 
 iOS
 
-<Tabs query="platform=ios&api=payload-keys"/>
+<Tabs query="platform=ios&api=payload-keys"/>

src/pages/documentation/adobe-journey-optimizer/push-notification/tabs/push-payload.md

@@ -91,4 +91,4 @@ noIndex: true
 | `adb_act` | Array | An array that contains the action object(s). |
 | `adb_act.aid` | String | The ID for the action object. |
 | `adb_act.label` | String | The name for the action object |
-| `adb_act.type` | String | The type for the action object. It can be one of the following string values: `DEEPLINK`, `WEBURL`, `DISMISS` |
+| `adb_act.type` | String | The type for the action object. It can be one of the following string values: `DEEPLINK`, `WEBURL`, `DISMISS` |

src/pages/documentation/adobe-journey-optimizer/tabs/api-reference.md

@@ -62,4 +62,5 @@ public static void registerExtension();
 
 ```java
 Messaging.registerExtension();
-```
+```
+