Tidy up commit

Author: franrob-projects

src/pages/docs/auth/capabilities.mdx

@@ -7,7 +7,7 @@ API keys and Ably-compatible tokens, have a set of capabilities assigned to them
 
 API keys are long-lived, secret and typically not shared with clients. API key capabilities are configured using the [dashboard](https://ably.com/dashboard), or using the [Control API](/docs/platform/account/control-api).
 
-Ably-compatible tokens are designed to be shared with untrusted clients, are short-lived, and can be configured and issued programmatically. **For restricting client access to channels, tokens provide far more flexibility and security than API key capabilities.** See [selecting an authentication mechanism](/docs/auth#selecting-auth) to understand why token authentication is the preferred option in most scenarios.
+Ably-compatible tokens are designed to be shared with untrusted clients, are short-lived, and can be configured and issued programmatically. For restricting client access to channels, tokens provide far more flexibility and security than API key capabilities. See [selecting an authentication mechanism](/docs/auth#selecting-auth) to understand why token authentication is the preferred option in most scenarios.
 
 ### Capability changes and existing connections
 

src/pages/docs/metadata-stats/stats.mdx

@@ -43,7 +43,7 @@ curl --request GET \
 This endpoint returns a [statistics response type](#payload) including [account-only metrics](#account-only).
 
 <Aside data-type='note'>
-  To obtain your `ACCOUNT_ID`, you can use `/me` Control API endpoint to find your `ACCOUNT_ID`, or alternatively find it in the [**Settings**](https://ably.com/accounts/any/edit) page of your account dashboard:
+  To obtain your `ACCOUNT_ID`, you can use `/me` Control API endpoint to find your `ACCOUNT_ID`, or alternatively find it in the [Settings](https://ably.com/accounts/any/edit) page of your account dashboard:
 </Aside>
 
 <Code>
@@ -85,7 +85,7 @@ curl 'https://control.ably.net/v1/apps/${APP_ID}/stats' \
 This endpoint returns a [statistics response type](#payload).
 
 <Aside data-type='note'>
-    The `APP_ID` can be found in the [**Settings**](https://ably.com/accounts/any/apps/any/edit) tab of an application within your dashboard.
+    The `APP_ID` can be found in the [Settings](https://ably.com/accounts/any/apps/any/edit) tab of an application within your dashboard.
 </Aside>
 
 ### App statistics via SDK <a id="app-sdk"/>
@@ -360,45 +360,45 @@ The following metadata is returned for each entry:
 
 | Property | Description |
 | --- | --- |
-| **appId** | The ID of the Ably application the statistics are for. Only present when querying app statistics. |
-| **accountId** | The ID of the Ably account the statistics are for. Only present when querying account statistics. |
-| **intervalId** | Start time for the stats entry. Format is `yyyy-mm-dd:hh:mm` for `unit=minute`, and `yyyy-mm-dd:hh` for `unit=hour,day,month`. |
-| **unit** | Unit of time that the stats entry covers. One of `minute`, `hour`, `day` or `month`. |
-| **schema** | URI of the stats schema. |
-| **inProgress** | The last sub-interval included in this entry in the format `yyyy-mm-dd:hh:mm:ss`, else undefined. For entries that are still in progress, such as the current month. |
+| appId | The ID of the Ably application the statistics are for. Only present when querying app statistics. |
+| accountId | The ID of the Ably account the statistics are for. Only present when querying account statistics. |
+| intervalId | Start time for the stats entry. Format is `yyyy-mm-dd:hh:mm` for `unit=minute`, and `yyyy-mm-dd:hh` for `unit=hour,day,month`. |
+| unit | Unit of time that the stats entry covers. One of `minute`, `hour`, `day` or `month`. |
+| schema | URI of the stats schema. |
+| inProgress | The last sub-interval included in this entry in the format `yyyy-mm-dd:hh:mm:ss`, else undefined. For entries that are still in progress, such as the current month. |
 
 ### All messages <a id="messages"/>
 
 All messages metrics include all messages types, such as those sent and received by Ably and clients, messages delivered via integrations and push notifications delivered to devices.
 
 Failed vs. Refused messages:
-- **Failed** messages are those that did not succeed for reasons other than Ably actively rejecting them, such as external integration target rejections or Ably service issues.
-- **Refused** messages are those that Ably actively chose to reject, typically due to rate limiting, malformed messages, or insufficient client permissions.
+- Failed messages are those that did not succeed for reasons other than Ably actively rejecting them, such as external integration target rejections or Ably service issues.
+- Refused messages are those that Ably actively chose to reject, typically due to rate limiting, malformed messages, or insufficient client permissions.
 
 | Metric | Description |
 | --- | --- |
-| **messages.all.all.count** | Total number of messages that were successfully received and sent by Ably, summed over all message types and transports. |
-| **messages.all.all.billableCount** | Total number of billable messages that were successfully received and sent by Ably, summed over all message types and transports. |
-| **messages.all.all.data** | Total data in messages successfully received and sent by Ably, summed over all message types and transports. |
-| **messages.all.all.uncompressedData** | Total data in messages successfully received and sent by Ably, excluding savings provided by delta compression. |
-| **messages.all.all.failed** | Total number of messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
-| **messages.all.all.refused** | Total number of messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions.|
-| **messages.all.messages.count** | Total message count, excluding presence and object messages. |
-| **messages.all.messages.billableCount** | Total billable message count, excluding presence and object messages. |
-| **messages.all.messages.data** | Total message size, excluding presence and object messages. |
-| **messages.all.messages.uncompressedData** | Total number of messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
-| **messages.all.messages.failed** | Total number of messages excluding presence and object messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
-| **messages.all.messages.refused** | Total number of messages excluding presence and object messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions. |
-| **messages.all.presence.count** | Total presence message count. |
-| **messages.all.presence.billableCount** | Total billable presence message count. |
-| **messages.all.presence.data** | Total presence message size. |
-| **messages.all.presence.uncompressedData** | Total uncompressed presence message size, excluding delta compression. |
-| **messages.all.objects.count** | Total objects message count. |
-| **messages.all.objects.billableCount** | Total billable objects message count. |
-| **messages.all.objects.data** | Total objects message size. |
-| **messages.all.objects.uncompressedData** | Total uncompressed objects message size, excluding delta compression. |
-| **messages.all.messages.failed** | Total number of presence messages excluding presence and object messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
-| **messages.all.messages.refused** | Total number of presence messages excluding presence and object messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions. |
+| `messages.all.all.count` | Total number of messages that were successfully received and sent by Ably, summed over all message types and transports. |
+| `messages.all.all.billableCount` | Total number of billable messages that were successfully received and sent by Ably, summed over all message types and transports. |
+| `messages.all.all.data` | Total data in messages successfully received and sent by Ably, summed over all message types and transports. |
+| `messages.all.all.uncompressedData` | Total data in messages successfully received and sent by Ably, excluding savings provided by delta compression. |
+| `messages.all.all.failed` | Total number of messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
+| `messages.all.all.refused` | Total number of messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions.|
+| `messages.all.messages.count` | Total message count, excluding presence and object messages. |
+| `messages.all.messages.billableCount` | Total billable message count, excluding presence and object messages. |
+| `messages.all.messages.data` | Total message size, excluding presence and object messages. |
+| `messages.all.messages.uncompressedData` | Total number of messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
+| `messages.all.messages.failed` | Total number of messages excluding presence and object messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
+| `messages.all.messages.refused` | Total number of messages excluding presence and object messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions. |
+| `messages.all.presence.count` | Total presence message count. |
+| `messages.all.presence.billableCount` | Total billable presence message count. |
+| `messages.all.presence.data` | Total presence message size. |
+| `messages.all.presence.uncompressedData` | Total uncompressed presence message size, excluding delta compression. |
+| `messages.all.objects.count` | Total objects message count. |
+| `messages.all.objects.billableCount` | Total billable objects message count. |
+| `messages.all.objects.data` | Total objects message size. |
+| `messages.all.objects.uncompressedData` | Total uncompressed objects message size, excluding delta compression. |
+| `messages.all.messages.failed` | Total number of presence messages excluding presence and object messages that failed. These are messages which did not succeed for some reason other than Ably explicitly refusing them, such as they were rejected by an external integration target, or a service issue on Ably's side. |
+| `messages.all.messages.refused` | Total number of presence messages excluding presence and object messages that were refused by Ably. For example, due to [rate limiting](/docs/platform/pricing/limits), malformed messages, or incorrect client permissions. |
 
 ### Inbound messages <a id="inbound"/>
 

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

@@ -43,10 +43,10 @@ Set resource restrictions to control access to channels and queues, ranging from
 
 | Restriction | Description |
 | ----------- | ----------- |
-| **None** | No restrictions; access any channel or queue. |
-| **Only channels** | Access any channel but not queues. |
-| **Only queues** | Access any queue but not channels. |
-| **Selected channels and queues** | Specify explicit rules for access. |
+| None | No restrictions; access any channel or queue. |
+| Only channels | Access any channel but not queues. |
+| Only queues | Access any queue but not channels. |
+| Selected channels and queues | Specify explicit rules for access. |
 
 When specifying selected channels and queues, you can provide a comma-separated list of resources. Each resource can match a single channel (e.g., `channel-name`) or multiple channels using wildcards (e.g., `namespace:*`). Queues use the prefix `[queue]` and meta channels use `[meta]`. See [capabilities documentation](/docs/auth/capabilities#wildcards) for detailed wildcard syntax.
 
@@ -60,7 +60,7 @@ A single API key cannot support complex permission combinations, such as publish
 
 | Option | Description |
 | ------ | ----------- |
-| **Revocable tokens** | Implement security measures by setting shorter token lifetimes and enabling the ability to revoke tokens issued by the API key. |
+| Revocable tokens | Implement security measures by setting shorter token lifetimes and enabling the ability to revoke tokens issued by the API key. |
 
 ### Change your API key settings
 

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

@@ -17,33 +17,33 @@ The following provides an overview of your application settings.
 | **App ID** | This ID is automatically generated by Ably when you create an application. It is a critical part of your application's identity and is included in every API key and token issued for your application. |
 | **Name** | This is the user-defined name that you assigned when creating your application. It is helpful for quickly identifying the application among others in your dashboard, especially if you manage multiple applications. |
 | **Security** | Enabled by default, this option enforces Transport Layer Security (TLS) for all connections to your application. TLS protocol ensures data encryption and secure communication between clients and servers. |
-| **Enabled** | When an application is **disabled**, it no longer accepts new connections and deactivates all associated services. Clients cannot connect, send or receive messages, or use other Ably services. When **enabled**, the application allows new connections and activates all related services. |
+| **Enabled** | When an application is disabled, it no longer accepts new connections and deactivates all associated services. Clients cannot connect, send or receive messages, or use other Ably services. When enabled, the application allows new connections and activates all related services. |
 
 ### Channel rule configuration
 
 The following explains the configuration rules for specific [namespaces](/docs/channels#namespaces) or [channels](/docs/channels):
 
 | Section | Description |
 | ------- | ----------- |
-| **Namespace or channel ID** | Identify the specific namespace or channel to which this rule will apply. |
-| **Persist last message** | Stores the last message published on a channel for 365 days, accessible via the rewind mechanism. |
-| **Persist all messages** | Ably stores all messages for two minutes by default. Depending on your account package, this can be increased to 24 or 72 hours. It is also possible to persist the last message sent to a channel for a year. |
-| **Identified** | Requires clients to authenticate with a client ID to interact with channels in this namespace. |
-| **TLS only** | Restricts access to channels within this namespace to clients connected using TLS. |
-| **Push notifications enabled** | Enables publishing messages with a push payload, triggering native push notifications to registered devices. |
-| **Message interactions enabled** | Enables unique time serial fields in messages, enabling typed references between messages (e.g., implementing 'Likes' in a chat). |
-| **Server-side batching enabled** | Batches inbound messages on the server side before sending them to subscribers based on the configured policy. |
-| **Cancel** | Discards changes and closes the dialog without saving the new rule.|
+| Namespace or channel ID | Identify the specific namespace or channel to which this rule will apply. |
+| Persist last message | Stores the last message published on a channel for 365 days, accessible via the rewind mechanism. |
+| Persist all messages | Ably stores all messages for two minutes by default. Depending on your account package, this can be increased to 24 or 72 hours. It is also possible to persist the last message sent to a channel for a year. |
+| Identified | Requires clients to authenticate with a client ID to interact with channels in this namespace. |
+| TLS only | Restricts access to channels within this namespace to clients connected using TLS. |
+| Push notifications enabled | Enables publishing messages with a push payload, triggering native push notifications to registered devices. |
+| Message interactions enabled | Enables unique time serial fields in messages, enabling typed references between messages (e.g., implementing 'Likes' in a chat). |
+| Server-side batching enabled | Batches inbound messages on the server side before sending them to subscribers based on the configured policy. |
+| Cancel | Discards changes and closes the dialog without saving the new rule.|
 
 ### Protocol adapter settings
 
 The following explains the configuration support for various communication protocols ([Pusher](/docs/protocols/pusher), [PubNub](/docs/protocols/pubnub), [MQTT](/docs/protocols/mqtt)), enabling different client libraries to interact with Ably.
 
 | Settings  | Description |
 | --------- | ----------- |
-| **Pusher protocol support** | Provides compatibility with the Pusher protocol. |
-| **PubNub protocol support** | Provides compatibility with the PubNub protocol. |
-| **MQTT protocol support** | Provides compatibility with the MQTT protocol. |
+| Pusher protocol support | Provides compatibility with the Pusher protocol. |
+| PubNub protocol support | Provides compatibility with the PubNub protocol. |
+| MQTT protocol support | Provides compatibility with the MQTT protocol. |
 
 ### Actions