Merge pull request #3058 from ably/FTF-452-write-usp-copy-for-live-objects

Adds USPs to liveobjects docs

Author: GregHolmes

src/pages/docs/liveobjects/concepts/operations.mdx

@@ -31,6 +31,12 @@ When you create or update an object, the change is expressed as an _operation_ t
 
 This document explains the key concepts you need to know when working with operations.
 
+<Aside data-type='usp'>
+Exactly-once delivery
+
+Ably's platform guarantees [idempotent publishing](/docs/platform/architecture/idempotency), ensuring that each operation is applied exactly once across all subscribers — even if the publishing client retries due to network issues.
+</Aside>
+
 ## Operation types <a id="operation-types"/>
 
 Each object type supports specific operations that modify the object's data.

src/pages/docs/liveobjects/inband-objects.mdx

@@ -37,6 +37,12 @@ If you're using LiveObjects from one of the the following languages, then use th
 
 Inband objects works by delivering changes to channel objects as regular channel messages, similar to [inband occupancy](/docs/channels/options#occupancy).
 
+<Aside data-type='usp'>
+Scalable message fanout
+
+Inband object updates are delivered as regular channel messages through Ably's [horizontally scalable architecture](/docs/platform/architecture/platform-scalability), so LiveObjects state changes can be distributed to any number of subscribers simultaneously.
+</Aside>
+
 ## Enable Inband Objects <a id="inband-objects-enable"/>
 
 To enable inband objects, use the `objects` [channel parameter](/docs/channels/options#objects) when getting a channel:

src/pages/docs/liveobjects/index.mdx

@@ -29,7 +29,7 @@ Ably LiveObjects provides a serverless, durable, and scalable way to create, upd
 
 LiveObjects provides a global, durable, and conflict-free shared data layer built on Ably's [global platform](/docs/platform/architecture), so your application state stays perfectly synchronized in realtime without the need to build or manage complex infrastructure yourself.
 
-<Aside class="note">
+<Aside data-type='note'>
 LiveObjects has the same performance guarantees and scaling potential as [channels](/docs/channels).
 </Aside>
 

src/pages/docs/liveobjects/storage.mdx

@@ -29,6 +29,12 @@ This means that if a client disconnects from Ably for a short period of time, it
 
 Operations themselves are not included in the [history](/docs/storage-history/history) or [rewind](/docs/channels/options/rewind) backlog of a channel. Instead, you should interact with objects directly via the client library.
 
+<Aside data-type='usp'>
+Two-tier recovery
+
+Short disconnections (under two minutes) are resolved by replaying missed operations via [automatic connection recovery](/docs/platform/architecture/connection-recovery), while longer disconnections trigger a full resync from durable storage. Either way, clients always converge to the correct state automatically.
+</Aside>
+
 ## Object size limit <a id="limits"/>
 
 The channel object has a maximum size limit, the default is 6.5(MB). This takes into account the size of every LiveObject (Map and Counter). When calculating the size of a channel object, Ably ignores any object or map entry with a [tombstone](/docs/liveobjects/concepts/objects#tombstones).