Group operations tables by feature with section-header rows

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: umair-ably

src/pages/docs/chat/pricing.mdx

@@ -13,28 +13,36 @@ The following table shows how Chat operations contribute to your message count:
 
 | Operation | Messages counted |
 | --- | --- |
-| [Send message](/docs/chat/rooms/messages) | 1 inbound message |
+| [Messages](/docs/chat/rooms/messages) ||
+| Send message | 1 inbound message |
 | Message delivery | 1 outbound message per subscriber |
-| [Update message](/docs/chat/rooms/messages#update) | 1 inbound message |
+| Update message | 1 inbound message |
 | Message update delivery | 1 outbound message per subscriber |
-| [Delete message](/docs/chat/rooms/messages#delete) | 1 inbound message |
+| Delete message | 1 inbound message |
 | Message deletion delivery | 1 outbound message per subscriber |
-| [History](/docs/chat/rooms/history) retrieval | 1 message per retrieved message |
-| [Typing indicator](/docs/chat/rooms/typing) keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
-| Typing indicator delivery | 1 outbound message per subscriber per heartbeat |
-| Typing indicator stop | 1 inbound message |
+| [History](/docs/chat/rooms/history) ||
+| History retrieval | 1 message per retrieved message |
+| [Typing indicators](/docs/chat/rooms/typing) ||
+| Typing keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
+| Typing keystroke delivery | 1 outbound message per subscriber per heartbeat |
+| Typing stop | 1 inbound message |
 | Typing stop delivery | 1 outbound message per subscriber |
-| [Room reaction](/docs/chat/rooms/reactions) | 1 inbound message |
+| [Room reactions](/docs/chat/rooms/reactions) ||
+| Room reaction | 1 inbound message |
 | Room reaction delivery | 1 outbound message per subscriber |
-| [Message reaction](/docs/chat/rooms/message-reactions) send | 1 inbound message |
+| [Message reactions](/docs/chat/rooms/message-reactions) ||
+| Message reaction send | 1 inbound message |
 | Message reaction delete | 1 inbound message |
 | Message reaction summary delivery | 1 outbound message per subscriber; multiple reactions may be rolled up into a single summary |
-| [Presence](/docs/chat/rooms/presence) enter | 1 inbound message |
+| [Presence](/docs/chat/rooms/presence) ||
+| Presence enter | 1 inbound message |
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| [Occupancy](/docs/chat/rooms/occupancy) event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
-| [Moderation](/docs/chat/moderation) action | 1 inbound message; triggers a message update or delete which follows standard delivery |
+| [Occupancy](/docs/chat/rooms/occupancy) ||
+| Occupancy event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
+| [Moderation](/docs/chat/moderation) ||
+| Moderation action | 1 inbound message; triggers a message update or delete which follows standard delivery |
 
 <Aside data-type="further-reading">
 For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).

src/pages/docs/liveobjects/pricing.mdx

@@ -15,9 +15,11 @@ The following table shows how LiveObjects operations contribute to your message
 
 | Operation | Messages counted |
 | --- | --- |
-| [LiveMap](/docs/liveobjects/map) set or remove | 1 inbound message per operation |
+| [LiveMap](/docs/liveobjects/map) ||
+| LiveMap set or remove | 1 inbound message per operation |
 | LiveMap create (shallow) | 2 inbound messages (create + assign) |
-| [LiveCounter](/docs/liveobjects/counter) increment or decrement | 1 inbound message |
+| [LiveCounter](/docs/liveobjects/counter) ||
+| LiveCounter increment or decrement | 1 inbound message |
 | LiveCounter create | 2 inbound messages (create + assign) |
 | ObjectMessage delivery | 1 outbound message per connected client |
 | [Synchronization](#synchronization) | 1 message per object synchronized |

src/pages/docs/platform/pricing/message-counting.mdx

@@ -38,25 +38,32 @@ The following table shows how [Pub/Sub](/docs/pub-sub) operations contribute to
 
 | Operation | Messages counted |
 | --- | --- |
-| [Publish](/docs/channels/messages#publish) | 1 inbound message |
+| [Messages](/docs/channels/messages) ||
+| Publish | 1 inbound message |
 | Message delivery | 1 outbound message per subscriber |
-| [Presence](/docs/presence-occupancy/presence) enter | 1 inbound message |
+| [Presence](/docs/presence-occupancy/presence) ||
+| Presence enter | 1 inbound message |
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| [Persistence](/docs/storage-history/storage) storage | 1 additional message per stored message |
-| [History](/docs/storage-history/history) retrieval | 1 message per retrieved message |
-| [Integration](/docs/platform/integrations) delivery | 1 outbound message per integration target |
-| Inbound [integration](/docs/platform/integrations#inbound) publish | 1 inbound message |
+| Presence REST query | 1 message per member returned |
+| Batch presence request | 1 message per member across all queried channels |
+| [Storage and history](/docs/storage-history/storage) ||
+| Persistence storage | 1 additional message per stored message |
+| History retrieval | 1 message per retrieved message |
 | [Rewind](/docs/channels/options/rewind) on attach | 1 message per rewound message (up to 100) |
-| [Push notification](/docs/push) delivery | 1 message per delivered notification |
-| [Presence REST](/docs/presence-occupancy/presence) query | 1 message per member returned |
-| [Batch presence](/docs/presence-occupancy/presence) request | 1 message per member across all queried channels |
-| [Annotation](/docs/messages/annotations) publish | 1 inbound message |
+| [Integrations](/docs/platform/integrations) ||
+| Integration delivery | 1 outbound message per integration target |
+| [Inbound integration publish](/docs/platform/integrations#inbound) | 1 inbound message |
+| [Push notifications](/docs/push) ||
+| Push notification delivery | 1 message per delivered notification |
+| [Annotations](/docs/messages/annotations) ||
+| Annotation publish | 1 inbound message |
 | Annotation delete | 1 inbound message |
-| [Annotation summary](/docs/messages/annotations#annotation-summaries) delivery | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
-| [Lifecycle event](/docs/metadata-stats/metadata) (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
-| [`[meta]stats:minute`](/docs/metadata-stats/metadata) event | 1 message per event |
+| [Annotation summary delivery](/docs/messages/annotations#annotation-summaries) | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
+| [Metadata and stats](/docs/metadata-stats/metadata) ||
+| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
+| `[meta]stats:minute` event | 1 message per event |
 | `[meta]log` subscription | Not counted |
 
 For Pub/Sub-specific cost optimization strategies, see [Pub/Sub pricing](/docs/pub-sub/pricing).
@@ -67,28 +74,36 @@ The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat
 
 | Operation | Messages counted |
 | --- | --- |
-| [Send message](/docs/chat/rooms/messages) | 1 inbound message |
+| [Messages](/docs/chat/rooms/messages) ||
+| Send message | 1 inbound message |
 | Message delivery | 1 outbound message per subscriber |
-| [Update message](/docs/chat/rooms/messages#update) | 1 inbound message |
+| Update message | 1 inbound message |
 | Message update delivery | 1 outbound message per subscriber |
-| [Delete message](/docs/chat/rooms/messages#delete) | 1 inbound message |
+| Delete message | 1 inbound message |
 | Message deletion delivery | 1 outbound message per subscriber |
-| [History](/docs/chat/rooms/history) retrieval | 1 message per retrieved message |
-| [Typing indicator](/docs/chat/rooms/typing) keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
-| Typing indicator delivery | 1 outbound message per subscriber per heartbeat |
-| Typing indicator stop | 1 inbound message |
+| [History](/docs/chat/rooms/history) ||
+| History retrieval | 1 message per retrieved message |
+| [Typing indicators](/docs/chat/rooms/typing) ||
+| Typing keystroke | 1 inbound message; repeats every heartbeat interval (default 10s) |
+| Typing keystroke delivery | 1 outbound message per subscriber per heartbeat |
+| Typing stop | 1 inbound message |
 | Typing stop delivery | 1 outbound message per subscriber |
-| [Room reaction](/docs/chat/rooms/reactions) | 1 inbound message |
+| [Room reactions](/docs/chat/rooms/reactions) ||
+| Room reaction | 1 inbound message |
 | Room reaction delivery | 1 outbound message per subscriber |
-| [Message reaction](/docs/chat/rooms/message-reactions) send | 1 inbound message |
+| [Message reactions](/docs/chat/rooms/message-reactions) ||
+| Message reaction send | 1 inbound message |
 | Message reaction delete | 1 inbound message |
 | Message reaction summary delivery | 1 outbound message per subscriber; multiple reactions may be rolled up into a single summary |
-| [Presence](/docs/chat/rooms/presence) enter | 1 inbound message |
+| [Presence](/docs/chat/rooms/presence) ||
+| Presence enter | 1 inbound message |
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| [Occupancy](/docs/chat/rooms/occupancy) event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
-| [Moderation](/docs/chat/moderation) action | 1 inbound message; triggers a message update or delete which follows standard delivery |
+| [Occupancy](/docs/chat/rooms/occupancy) ||
+| Occupancy event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
+| [Moderation](/docs/chat/moderation) ||
+| Moderation action | 1 inbound message; triggers a message update or delete which follows standard delivery |
 
 For Chat-specific cost optimization strategies, see [Chat pricing](/docs/chat/pricing).
 
@@ -98,9 +113,11 @@ For Chat-specific cost optimization strategies, see [Chat pricing](/docs/chat/pr
 
 | Operation | Messages counted |
 | --- | --- |
-| [LiveMap](/docs/liveobjects/map) set or remove | 1 inbound message per operation |
+| [LiveMap](/docs/liveobjects/map) ||
+| LiveMap set or remove | 1 inbound message per operation |
 | LiveMap create (shallow) | 2 inbound messages (create + assign) |
-| [LiveCounter](/docs/liveobjects/counter) increment or decrement | 1 inbound message |
+| [LiveCounter](/docs/liveobjects/counter) ||
+| LiveCounter increment or decrement | 1 inbound message |
 | LiveCounter create | 2 inbound messages (create + assign) |
 | ObjectMessage delivery | 1 outbound message per connected client |
 | [Synchronization](/docs/liveobjects/pricing#synchronization) | 1 message per object synchronized |
@@ -117,16 +134,20 @@ The [Spaces SDK](/docs/spaces) is built on top of [Pub/Sub](/docs/pub-sub) chann
 
 | Operation | Messages counted |
 | --- | --- |
-| [Enter](/docs/spaces/space#enter) space | 1 inbound message |
-| [Leave](/docs/spaces/space#leave) space | 1 inbound message |
-| [Update profile](/docs/spaces/space#update-profile) | 1 inbound message |
+| [Members](/docs/spaces/space) ||
+| Enter space | 1 inbound message |
+| Leave space | 1 inbound message |
+| Update profile | 1 inbound message |
 | Space event delivery | 1 outbound message per subscriber |
-| [Set location](/docs/spaces/locations#set) | 1 inbound message |
+| [Locations](/docs/spaces/locations) ||
+| Set location | 1 inbound message |
 | Location event delivery | 1 outbound message per subscriber |
-| [Set cursor](/docs/spaces/cursors#set) position | 1 inbound message per batch (default batch interval 25ms) |
+| [Cursors](/docs/spaces/cursors) ||
+| Set cursor position | 1 inbound message per batch (default batch interval 25ms) |
 | Cursor event delivery | 1 outbound message per subscriber |
-| [Acquire lock](/docs/spaces/locking#acquire) | 1 inbound message |
-| [Release lock](/docs/spaces/locking#release) | 1 inbound message |
+| [Locking](/docs/spaces/locking) ||
+| Acquire lock | 1 inbound message |
+| Release lock | 1 inbound message |
 | Lock event delivery | 1 outbound message per subscriber |
 
 Live cursors use a [separate channel](/docs/spaces/cursors#foundations) from other space features due to their high update frequency. Registering multiple subscription listeners for the same event does not increase your message count, as these are [client-side filtered events](/docs/spaces/space#subscribe).

src/pages/docs/pub-sub/pricing.mdx

@@ -13,25 +13,32 @@ The following table shows how Pub/Sub operations contribute to your message coun
 
 | Operation | Messages counted |
 | --- | --- |
-| [Publish](/docs/channels/messages#publish) | 1 inbound message |
+| [Messages](/docs/channels/messages) ||
+| Publish | 1 inbound message |
 | Message delivery | 1 outbound message per subscriber |
-| [Presence](/docs/presence-occupancy/presence) enter | 1 inbound message |
+| [Presence](/docs/presence-occupancy/presence) ||
+| Presence enter | 1 inbound message |
 | Presence leave | 1 inbound message |
 | Presence update | 1 inbound message |
 | Presence event delivery | 1 outbound message per presence subscriber |
-| [Persistence](/docs/storage-history/storage) storage | 1 additional message per stored message |
-| [History](/docs/storage-history/history) retrieval | 1 message per retrieved message |
-| [Integration](/docs/platform/integrations) delivery | 1 outbound message per integration target |
-| Inbound [integration](/docs/platform/integrations#inbound) publish | 1 inbound message |
+| Presence REST query | 1 message per member returned |
+| Batch presence request | 1 message per member across all queried channels |
+| [Storage and history](/docs/storage-history/storage) ||
+| Persistence storage | 1 additional message per stored message |
+| History retrieval | 1 message per retrieved message |
 | [Rewind](/docs/channels/options/rewind) on attach | 1 message per rewound message (up to 100) |
-| [Push notification](/docs/push) delivery | 1 message per delivered notification |
-| [Presence REST](/docs/presence-occupancy/presence) query | 1 message per member returned |
-| [Batch presence](/docs/presence-occupancy/presence) request | 1 message per member across all queried channels |
-| [Annotation](/docs/messages/annotations) publish | 1 inbound message |
+| [Integrations](/docs/platform/integrations) ||
+| Integration delivery | 1 outbound message per integration target |
+| [Inbound integration publish](/docs/platform/integrations#inbound) | 1 inbound message |
+| [Push notifications](/docs/push) ||
+| Push notification delivery | 1 message per delivered notification |
+| [Annotations](/docs/messages/annotations) ||
+| Annotation publish | 1 inbound message |
 | Annotation delete | 1 inbound message |
-| [Annotation summary](/docs/messages/annotations#annotation-summaries) delivery | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
-| [Lifecycle event](/docs/metadata-stats/metadata) (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
-| [`[meta]stats:minute`](/docs/metadata-stats/metadata) event | 1 message per event |
+| [Annotation summary delivery](/docs/messages/annotations#annotation-summaries) | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
+| [Metadata and stats](/docs/metadata-stats/metadata) ||
+| Lifecycle event (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
+| `[meta]stats:minute` event | 1 message per event |
 | `[meta]log` subscription | Not counted |
 
 <Aside data-type="further-reading">

src/pages/docs/spaces/pricing.mdx

@@ -13,16 +13,20 @@ The following table shows how Spaces operations contribute to your message count
 
 | Operation | Messages counted |
 | --- | --- |
-| [Enter](/docs/spaces/space#enter) space | 1 inbound message |
-| [Leave](/docs/spaces/space#leave) space | 1 inbound message |
-| [Update profile](/docs/spaces/space#update-profile) | 1 inbound message |
+| [Members](/docs/spaces/space) ||
+| Enter space | 1 inbound message |
+| Leave space | 1 inbound message |
+| Update profile | 1 inbound message |
 | Space event delivery | 1 outbound message per subscriber |
-| [Set location](/docs/spaces/locations#set) | 1 inbound message |
+| [Locations](/docs/spaces/locations) ||
+| Set location | 1 inbound message |
 | Location event delivery | 1 outbound message per subscriber |
-| [Set cursor](/docs/spaces/cursors#set) position | 1 inbound message per batch (default batch interval 25ms) |
+| [Cursors](/docs/spaces/cursors) ||
+| Set cursor position | 1 inbound message per batch (default batch interval 25ms) |
 | Cursor event delivery | 1 outbound message per subscriber |
-| [Acquire lock](/docs/spaces/locking#acquire) | 1 inbound message |
-| [Release lock](/docs/spaces/locking#release) | 1 inbound message |
+| [Locking](/docs/spaces/locking) ||
+| Acquire lock | 1 inbound message |
+| Release lock | 1 inbound message |
 | Lock event delivery | 1 outbound message per subscriber |
 
 Registering multiple subscription listeners for the same event does not increase your message count. These are [client-side filtered events](/docs/spaces/space#subscribe) where only a single message is published per event by Ably.