Tidy up commit

Author: franrob-projects

src/pages/docs/platform/account/app/notifications.mdx

@@ -57,10 +57,10 @@ Important considerations:
 - Device tokens are environment-specific and cannot be used interchangeably.
 
 How to configure the sandbox endpoint:
-1. In your Ably [dashboard](https://ably.com/accounts), navigate to the **Notifications** tab under your app settings.
+1. In the Ably [dashboard](https://ably.com/accounts), navigate to the **Notifications** tab under app settings.
 2. Go to **push notifications setup** and click **configure push**.
 3. In the **Apple push notification service** section, look for the **sandbox endpoint** option.
-4. Enable the sandbox endpoint checkbox if you want to use Apple's testing environment.
+4. Enable the sandbox endpoint checkbox to use Apple's testing environment.
 5. Click **save** to apply the changes.
 
 This separation between sandbox and production environments ensures that test notifications don't reach real users and provides a safe environment for development and testing.
@@ -79,26 +79,26 @@ Define the content of your push notification using the fields below:
 
 | Field | Purpose | How to Use |
 | ----- | ------- | ---------- |
-| **Notification title** | A title for the push notification, which will appear as the headline on the user's device. | Enter a short, clear title that captures the essence of the notification. |
-| **Notification body** | The main content of the notification to be displayed below the title. | Write the key information or message that you want the user to read. |
-| **Notification data** | Optional JSON data that the app can use for specific actions upon receiving the notification.  | Include any extra data needed for app functionality, such as custom metadata or instructions. |
+| Notification title | A title for the push notification, which will appear as the headline on the user's device. | Enter a short, clear title that captures the essence of the notification. |
+| Notification body | The main content of the notification to be displayed below the title. | Write the key information or message that you want the user to read. |
+| Notification data | Optional JSON data that the app can use for specific actions upon receiving the notification.  | Include any extra data needed for app functionality, such as custom metadata or instructions. |
 
 ### Push notification target
 
 Direct your push notifications to specific targets within the Ably platform. Select the appropriate target according to your notification strategy:
 
 | Target | Purpose | How to Use |
 | ------ | ------- | ---------- |
-| **Channel name** | Push notifications to all subscribers of a specific channel. | Enter the channel name and click **push to channel** to notify all devices subscribed to that channel. |
-| **Device ID** | Send a notification directly to a specific device. | Enter the Device ID and click **push to device** to target a single device with the notification. |
-| **Client ID** | Notify a specific client registered with Ably. | Enter the Client ID and click **push to client** to send the notification to the chosen client. |
+| Channel name | Push notifications to all subscribers of a specific channel. | Enter the channel name and click push to channel to notify all devices subscribed to that channel. |
+| Device ID | Send a notification directly to a specific device. | Enter the Device ID and click push to device to target a single device with the notification. |
+| Client ID | Notify a specific client registered with Ably. | Enter the Client ID and click push to client to send the notification to the chosen client. |
 
 ## Push inspector widget
 
 The Push Inspector widget allows you to monitor and manage your push notification infrastructure directly from the Ably dashboard. It provides insights into channel subscriptions, device registrations, and client registrations, making it easier to debug and optimize your notification setup.
 
 | Section | Purpose | How to Use |
 | ------- | ------- | ---------- |
-| **Channel subscriptions** | View and inspect all channels currently subscribed to push notifications. | Click **inspect channel** to see detailed information about a specific channel, including the number of subscribers and recent activity. |
-| **Device registrations**  | Access a list of all devices registered to receive push notifications. | Click **inspect device** to view detailed information about a specific device, such as its registration status, platform, and recent notifications. |
-| **Client registrations**  | Get an overview of all clients registered for push notifications within your Ably account. | Click **inspect client ID** to see detailed information about a specific client, including its subscriptions and recent activity. |
+| Channel subscriptions | View and inspect all channels currently subscribed to push notifications. | Click inspect channel to see detailed information about a specific channel, including the number of subscribers and recent activity. |
+| Device registrations  | Access a list of all devices registered to receive push notifications. | Click inspect device to view detailed information about a specific device, such as its registration status, platform, and recent notifications. |
+| Client registrations  | Get an overview of all clients registered for push notifications within the Ably account. | Click inspect client ID to see detailed information about a specific client, including its subscriptions and recent activity. |

src/pages/docs/push/configure/device.mdx

@@ -470,7 +470,7 @@ private ClientOptions GetAblyOptions(string clientId)
 
 #### Manual device registration with cross-platform push services <a id="cross-platform"/>
 
-In some scenarios, you may want to use FCM for iOS devices instead of APNs, or manually register devices with custom platform configurations. This is useful when you want to use Firebase's unified messaging system across both Android and iOS platforms.
+In some scenarios, you may want to use FCM for iOS devices instead of APNs, or manually register devices with custom platform configurations. This is useful when using Firebase's unified messaging system across both Android and iOS platforms.
 
 <Aside data-type='important'>
 When using manual device registration, be aware that the local device will default to APNs for iOS. You must explicitly set the platform and transport type to override this behavior.
@@ -534,11 +534,11 @@ deviceDetails.push.recipient = @{
 ```
 </Code>
 
-This approach allows you to:
-- Use FCM for both Android and iOS devices for unified push messaging.
-- Override the default platform-specific push service assignments.
-- Maintain full control over device registration parameters.
-- Integrate with Firebase's analytics and other services across platforms.
+This approach allows:
+- Using FCM for both Android and iOS devices for unified push messaging.
+- Overriding the default platform-specific push service assignments.
+- Maintaining full control over device registration parameters.
+- Integration with Firebase's analytics and other services across platforms.
 
 #### Test your push notification activation <a id="test-push"/>
 

src/pages/docs/push/index.mdx

@@ -19,9 +19,9 @@ Push notifications notify user devices or browsers regardless of whether an appl
 
 You can publish push notifications to user devices or browsers [directly](/docs/push/publish/#direct-publishing) or [via channels](#via-channels).
 
-**Publishing directly** sends push notifications to specific devices or browsers identified by unique identifiers, such as a `deviceId` or a `clientId`. This approach is akin to sending a personal message or alerts directly to an individual user's device or browser, bypassing the need for channel subscriptions. It excels in targeted and personalized communications, such as alerts specific to a user's actions, account notifications, or customized updates.
+Publishing directly sends push notifications to specific devices or browsers identified by unique identifiers, such as a `deviceId` or a `clientId`. This approach is akin to sending a personal message or alerts directly to an individual user's device or browser, bypassing the need for channel subscriptions. It excels in targeted and personalized communications, such as alerts specific to a user's actions, account notifications, or customized updates.
 
-**Publishing via channels** uses a [Pub/Sub](/docs/channels/messages) model. Messages are sent to channels to which multiple devices or browsers can subscribe. When a message is published to a channel, all devices or browsers subscribed to that channel receive the notification. This approach is particularly powerful for simultaneously publishing messages to multiple users.
+Publishing via channels uses a [Pub/Sub](/docs/channels/messages) model. Messages are sent to channels to which multiple devices or browsers can subscribe. When a message is published to a channel, all devices or browsers subscribed to that channel receive the notification. This approach is particularly powerful for simultaneously publishing messages to multiple users.
 
 ## Push notification process
 
@@ -110,20 +110,20 @@ channel.subscribe(msg => console.log(msg));
 
 ## Troubleshooting push notifications <a id="troubleshooting"/>
 
-If you're not receiving expected push notifications, follow these debugging steps:
+If not receiving expected push notifications, follow these debugging steps:
 
 ### Verify device registration
 
-Check if your device is registered in the Ably dashboard:
+Check if the device is registered in the Ably dashboard:
 1. Go to Notifications tab → Device inspector
-2. Search for your device using `deviceId` or `clientId`
+2. Search for the device using `deviceId` or `clientId`
 3. Verify device state:
    - ACTIVE: Ready to receive notifications
    - FAILED: Check error details (common: registration expired, invalid token)
 
 ### Test delivery
 
-Use the [push inspector](/docs/platform/account/app/notifications#push-inspector) in your dashboard to send test notifications directly to your device.
+Use the [push inspector](/docs/platform/account/app/notifications#push-inspector) in the dashboard to send test notifications directly to the device.
 
 ### Check for errors
 
@@ -143,7 +143,7 @@ Web Push:
 
 ### Duplicate notifications
 
-If you're receiving duplicate push notifications for the same device, this typically occurs when a device has both a `deviceId` and `clientId` subscription to the same channel:
+If receiving duplicate push notifications for the same device, this typically occurs when a device has both a `deviceId` and `clientId` subscription to the same channel:
 
 - `deviceId` subscriptions deliver notifications to a single specific device.
 - `clientId` subscriptions deliver notifications to all devices sharing that client ID.

src/pages/docs/push/publish.mdx

@@ -1348,21 +1348,21 @@ channel.publish(message);
 
 ## Handling push notifications on devices <a id="handling-push-notifications"/>
 
-After Ably delivers push notifications to devices, your mobile application needs to handle them appropriately. This includes processing the notification content, navigating users to relevant sections of your app, and implementing deep linking functionality.
+After Ably delivers push notifications to devices, mobile applications need to handle them appropriately. This includes processing the notification content, navigating users to relevant sections of the app, and implementing deep linking functionality.
 
 ### Deep links and app navigation <a id="deep-links"/>
 
-Deep links allow push notifications to navigate users directly to specific screens or content within your mobile application. While Ably handles the delivery of push notifications, creating and handling deep links is implemented within your mobile app code.
+Deep links allow push notifications to navigate users directly to specific screens or content within mobile applications. While Ably handles the delivery of push notifications, creating and handling deep links is implemented within mobile app code.
 
-You don't create deep links using Ably itself. Instead, you handle deep links in your app's push notification receivers and use the notification data to determine where to navigate users.
+Deep links are not created using Ably itself. Instead, handle deep links in app push notification receivers and use the notification data to determine where to navigate users.
 
 #### Android deep linking with push notifications
 
-On Android, you can implement deep links and app navigation in several ways.
+On Android, implement deep links and app navigation in several ways.
 
 Using `onMessageReceived` (recommended):
 
-Handle push notifications in your `FirebaseMessagingService` and create deep links programmatically:
+Handle push notifications in `FirebaseMessagingService` and create deep links programmatically:
 
 ```java
 @Override
@@ -1388,9 +1388,9 @@ private Intent createDeepLinkIntent(String screen, Map<String, String> data) {
 
 Using `click_action` with intent filters:
 
-Specify a `click_action` in your push notification payload and handle it with intent filters:
+Specify a `click_action` in the push notification payload and handle it with intent filters:
 
-1. Add `click_action` to your notification payload when publishing via Ably:
+1. Add `click_action` to the notification payload when publishing via Ably:
 
 ```json
 {
@@ -1408,7 +1408,7 @@ Specify a `click_action` in your push notification payload and handle it with in
 }
 ```
 
-2. Configure intent filters in your `AndroidManifest.xml`:
+2. Configure intent filters in `AndroidManifest.xml`:
 ```xml
 <activity android:name=".ChatActivity">
     <intent-filter>
@@ -1420,7 +1420,7 @@ Specify a `click_action` in your push notification payload and handle it with in
 
 #### iOS deep linking with push notifications
 
-On iOS, handle deep links in your app delegate or scene delegate:
+On iOS, handle deep links in the app delegate or scene delegate:
 
 Using URL schemes:
 ```swift
@@ -1449,7 +1449,7 @@ private func navigateToScreen(_ screen: String, with data: [AnyHashable: Any]) {
 ```
 
 Using Universal Links:
-Configure universal links in your app and handle them when users tap on push notifications:
+Configure universal links in the app and handle them when users tap on push notifications:
 
 ```swift
 func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {