Follow the language recommendation by EKLine in the mobile SDKs

Author: bojan

fern/docs/pages/sdks/mobile/android/features.mdx

@@ -83,7 +83,7 @@ The steps to identify a verified user are as follows:
 3. Pass the user identifier and the exchanged session token to the `DevRev.identifyVerifiedUser(_:sessionToken:)` method.
 
 <Callout intent="warning">
-For security reasons we **strongly recommend** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
+For security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
 </Callout>
 
 #### Generate an AAT
@@ -98,7 +98,7 @@ Ensure that you copy the generated application access token, as you cannot view
 
 #### Exchange your AAT for a session token
 
-In order to proceed with identifying the user, you need to exchange your AAT for a session token. This step will help you identify a user of your own system within the DevRev platform.
+To proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev platform.
 
 Here is a simple example of an API request to the DevRev backend to exchange your AAT for a session token:
 
@@ -119,7 +119,7 @@ curl \
 }'
 ```
 
-The response of the API call will contain a session token that you can use with the verified identification method in your app.
+The response of the API call contains a session token that you can use with the verified identification method in your app.
 
 <Callout intent="warning">
 As a good practice, **your** app should retrieve the exchanged session token from **your** backend at app launch or any relevant app lifecycle event.
@@ -186,7 +186,7 @@ You can perform a logout of the current user by calling the following method:
   </Tab>
 </Tabs>
 
-The user will be logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
+The user is logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
 
 ### Identity model
 
@@ -209,7 +209,7 @@ The `Identity` class contains the following properties:
 The custom fields properties defined as part of the user, organization and account traits, must be configured in the DevRev web app **before** they can be used. See [Object customization](https://devrev.ai/docs/product/object-customization) for more information.
 </Callout>
 
-##### UserTraits
+##### User traits
 
 The `UserTraits` class contains detailed information about the user:
 
@@ -226,7 +226,7 @@ All properties in `UserTraits` are optional.
 | `phoneNumbers` | `[String]?` | Array of the user's phone numbers |
 | `customFields` | `[String: Any]?` | Dictionary of custom fields configured in DevRev |
 
-##### OrganizationTraits
+##### Organization traits
 
 The `OrganizationTraits` class contains detailed information about the organization:
 
@@ -243,7 +243,7 @@ All properties in `OrganizationTraits` are optional.
 | `tier` | `String?` | The organization's tier or plan level |
 | `customFields` | `[String: Any]?` | Dictionary of custom fields configured in DevRev |
 
-##### AccountTraits
+##### Account traits
 
 The `AccountTraits` class contains detailed information about the account:
 

fern/docs/pages/sdks/mobile/android/migration-guide.mdx

@@ -2,7 +2,7 @@
 
 This guide helps transition from the legacy UserExperior SDK to the new DevRev SDK.
 
-## Feature Equivalence Chart
+## Feature equivalence chart
 
 | Feature | UserExperior SDK | DevRev SDK (Kotlin) | DevRev SDK (Java) |
 |-|-|-|-|

fern/docs/pages/sdks/mobile/android/quickstart.mdx

@@ -102,7 +102,7 @@ Use this property to check whether the DevRev SDK has been configured:
 </Tabs>
 
 <Callout intent="tip">
-`prefersDialogMode`, if set to true, enables the SDK to open the screens in the app's main task/activity.
+The property `prefersDialogMode`, when set to `true`, enables the SDK to open the screens in the app's main task/activity.
 </Callout>
 
 4. To configure the SDK, you need to call the following method inside your `Application` class:

fern/docs/pages/sdks/mobile/android/troubleshooting.mdx

@@ -6,7 +6,7 @@
 - **Issue**: How does the DevRev SDK handle errors?
   **Solution**: The DevRev SDK reports all errors using Android's logging utility. Look for error messages in Android Studio's Logcat after applying `DEVREV SDK` filter.
 
-- **Issue**: Support chat doesn't show.
+- **Issue**: Support chat won't show.
   **Solution**: Ensure you have correctly called one of the identification methods: `DevRev.identifyUnverifiedUser(...)`, `DevRev.identifyVerifiedUser(...)`, or `DevRev.identifyAnonymousUser(...)`.
 
 - **Issue**: Not receiving push notifications.
@@ -17,11 +17,10 @@
 - **Issue**: Missing class `com.google.android.play.core.splitcompat.SplitCompatApplication`.
   **Solution**: Add the following line to your `proguard-rules.pro` file: `-dontwarn com.google.android.play.core.**`.
 
-- **Issue**: Missing class issue due to transitive Flutter dependencies. 
+- **Issue**: Missing class issue due to transitive Flutter dependencies.
   **Solution**: Add the following lines to your `proguard-rules.pro` file:
   ```bash
   -keep class io.flutter.** { *; }
   -keep class io.flutter.plugins.** { *; }
   -keep class GeneratedPluginRegistrant { *; }
   ```
-

fern/docs/pages/sdks/mobile/cordova/features.mdx

@@ -42,7 +42,7 @@ The steps to identify a verified user are as follows:
 3. Pass the user identifier and the exchanged session token to the `DevRev.identifyVerifiedUser(_:sessionToken:)` method.
 
 <Callout intent="warning">
-For security reasons we **strongly recommend** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
+For security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
 </Callout>
 
 #### Generate an AAT
@@ -57,7 +57,7 @@ Ensure that you copy the generated application access token, as you cannot view
 
 #### Exchange your AAT for a session token
 
-In order to proceed with identifying the user, you need to exchange your AAT for a session token. This step will help you identify a user of your own system within the DevRev platform.
+To proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev platform.
 
 Here is a simple example of an API request to the DevRev backend to exchange your AAT for a session token:
 
@@ -78,7 +78,7 @@ curl \
 }'
 ```
 
-The response of the API call will contain a session token that you can use with the verified identification method in your app.
+The response of the API call contains a session token that you can use with the verified identification method in your app.
 
 <Callout intent="warning">
 As a good practice, **your** app should retrieve the exchanged session token from **your** backend at app launch or any relevant app lifecycle event.
@@ -149,7 +149,7 @@ All properties in `UserTraits` are optional.
 | `description` | `string OR null` | A description of the user |
 | `customFields` | `{ [key: string]: any }` | Dictionary of custom fields configured in DevRev |
 
-##### OrganizationTraits
+##### Organization traits
 
 The `OrganizationTraits` class contains detailed information about the organization:
 
@@ -166,7 +166,7 @@ All properties in `OrganizationTraits` are optional.
 | `tier` | `string OR null` | The organization's tier or plan level |
 | `customFields` | `{ [key: string]: any }` | Dictionary of custom fields configured in DevRev |
 
-##### AccountTraits
+##### Account traits
 
 The `AccountTraits` class contains detailed information about the account:
 
@@ -184,7 +184,7 @@ All properties in `AccountTraits` are optional.
 | `tier` | `string OR null` | The account's tier or plan level |
 | `customFields` | `{ [key: string]: any }` | Dictionary of custom fields configured in DevRev |
 
-The user will be logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
+The user is logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
 
 ## PLuG support chat
 

fern/docs/pages/sdks/mobile/cordova/migration-guide.mdx

@@ -2,7 +2,7 @@
 
 This guide and chart should help facilitate the transition from the legacy UserExperior SDK to the new DevRev SDK in your Cordova application, providing insights into feature equivalents and method changes.
 
-## Feature Equivalence Chart
+## Feature equivalence chart
 
 | Feature | UserExperior SDK | DevRev SDK |
 |-|-|-|

fern/docs/pages/sdks/mobile/flutter/features.mdx

@@ -43,7 +43,7 @@ The steps to identify a verified user are as follows:
 3. Pass the user identifier and the exchanged session token to the `DevRev.identifyVerifiedUser(userID, sessionToken)` method.
 
 <Callout intent="warning">
-For security reasons we **strongly recommend** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
+For security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
 </Callout>
 
 #### Generate an AAT
@@ -58,7 +58,7 @@ Ensure that you copy the generated application access token, as you cannot view
 
 #### Exchange your AAT for a session token
 
-In order to proceed with identifying the user, you need to exchange your AAT for a session token. This step will help you identify a user of your own system within the DevRev platform.
+To proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev platform.
 
 Here is a simple example of an API request to the DevRev backend to exchange your AAT for a session token:
 
@@ -79,7 +79,7 @@ curl \
 }'
 ```
 
-The response of the API call will contain a session token that you can use with the verified identification method in your app.
+The response of the API call contains a session token that you can use with the verified identification method in your app.
 
 <Callout intent="warning">
 As a good practice, **your** app should retrieve the exchanged session token from **your** backend at app launch or any relevant app lifecycle event.
@@ -123,7 +123,7 @@ You can perform a logout of the current user by calling the following method:
 DevRev.logout(deviceID);
 ```
 
-The user will be logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
+The user is logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
 
 For example:
 
@@ -165,7 +165,7 @@ The `Identity` class contains the following properties:
 The custom fields properties defined as part of the user, organization and account traits, must be configured in the DevRev web app **before** they can be used. See [Object customization](https://devrev.ai/docs/product/object-customization) for more information.
 </Callout>
 
-#### UserTraits
+#### User traits
 
 The `UserTraits` class contains detailed information about the user:
 

fern/docs/pages/sdks/mobile/flutter/migration-guide.mdx

@@ -2,7 +2,7 @@
 
 This guide helps you transition from the legacy UserExperior SDK to the new DevRev SDK in your Flutter application. Below is a feature equivalence chart and detailed instructions for migrating.
 
-## Feature equivalence Chart
+## Feature equivalence chart
 
 | Feature | UserExperior SDK | DevRev SDK |
 |-|-|-|

fern/docs/pages/sdks/mobile/flutter/quickstart.mdx

@@ -50,7 +50,7 @@ DevRev.configure(appID: "abcdefg12345")
 
 A sample app with use cases for the DevRev SDK for Flutter has been provided as a part of our [public repository](https://github.com/devrev/devrev-sdk-flutter). To set up and run the sample app:
 
-1. Navigate to the `sample` directory:
+1. Go to the `sample` directory:
    ```sh
    cd sample
    flutter clean

fern/docs/pages/sdks/mobile/ios/features.mdx

@@ -44,7 +44,7 @@ The steps to identify a verified user are as follows:
 3. Pass the user identifier and the exchanged session token to the `DevRev.identifyVerifiedUser(_:sessionToken:)` method.
 
 <Callout intent="warning">
-For security reasons we **strongly recommend** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
+For security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).
 </Callout>
 
 #### Generate an AAT
@@ -59,7 +59,7 @@ Ensure that you copy the generated application access token, as you cannot view
 
 #### Exchange your AAT for a session token
 
-In order to proceed with identifying the user, you need to exchange your AAT for a session token. This step will help you identify a user of your own system within the DevRev platform.
+To proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev platform.
 
 Here is a simple example of an API request to the DevRev backend to exchange your AAT for a session token:
 
@@ -80,7 +80,7 @@ curl \
 }'
 ```
 
-The response of the API call will contain a session token that you can use with the verified identification method in your app.
+The response of the API call contains a session token that you can use with the verified identification method in your app.
 
 <Callout intent="warning">
 As a good practice, **your** app should retrieve the exchanged session token from **your** backend at app launch or any relevant app lifecycle event.
@@ -128,7 +128,7 @@ You can perform a logout of the current user by calling the following method:
 DevRev.logout(deviceID:)
 ```
 
-The user will be logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
+The user is logged out by clearing their credentials, as well as unregistering the device from receiving push notifications, and stopping the session recording.
 
 For example:
 
@@ -170,7 +170,7 @@ The `Identity` class contains the following properties:
 The custom fields properties defined as part of the user, organization and account traits, must be configured in the DevRev web app **before** they can be used. See [Object customization](https://devrev.ai/docs/product/object-customization) for more information.
 </Callout>
 
-##### UserTraits
+##### User traits
 
 The `UserTraits` class contains detailed information about the user:
 
@@ -187,7 +187,7 @@ All properties in `UserTraits` are optional.
 | `phoneNumbers` | `[String]?` | Array of the user's phone numbers |
 | `customFields` | `[String: Any]?` | Dictionary of custom fields configured in DevRev |
 
-##### OrganizationTraits
+##### Organization traits
 
 The `OrganizationTraits` class contains detailed information about the organization:
 
@@ -204,7 +204,7 @@ All properties in `OrganizationTraits` are optional.
 | `tier` | `String?` | The organization's tier or plan level |
 | `customFields` | `[String: Any]?` | Dictionary of custom fields configured in DevRev |
 
-##### AccountTraits
+##### Account traits
 
 The `AccountTraits` class contains detailed information about the account: