Adds INFRA USPs to Pub/Sub

Author: franrob-projects

src/pages/docs/auth/revocation.mdx

@@ -64,6 +64,10 @@ There can be a maximum of 100 target specifiers in a single request.
 
 The token revocation API is rate-limited, so there is a maximum global aggregate rate of revocation requests per app. The rate is configurable by Ably at the application level. As part of the process of enabling revocation on an app Ably will ask you what the maximum rate of token revocations on that app needs to be, and then provision that capacity. The decision is not permanent, it can be changed by Ably on request at any time.
 
+<Aside data-type='see-evidence'>
+By tracking changes over time, Ably can identify gradual degradations before they become critical issues. [Click here for evidence 🔬](https://ably.com/docs/platform/architecture/infrastructure-operations#metrics-collection)
+</Aside>
+
 Note that revocation does not permanently forbid a client, connection, `clientId` or channel. It invalidates token credentials issued before a certain point in time. Ultimately, the app that issues tokens is responsible for whether or not a client is able to continue to interact with the Ably service.
 
 ## Revocation targets <a id="target-specifiers"/>

src/pages/docs/channels/options/index.mdx

@@ -240,6 +240,10 @@ The [`delta`](/docs/channels/options/deltas) feature enables clients to subscrib
 
 [Occupancy](/docs/presence-occupancy/occupancy) provides metrics about the clients attached to a channel, such as the number of connections and the number of clients subscribed to the channel. `occupancy` can be specified in the `params` property in order to subscribe a client to occupancy metrics for the channel. The metrics will be received by a client as events on the channel.
 
+<Aside data-type='see-evidence'>
+Metrics are collected from the host instance and from each of the containers on every instance, providing comprehensive visibility into system performance and resource utilization. [Click here for evidence 🔬](https://ably.com/docs/platform/architecture/infrastructure-operations#metrics-collection)
+</Aside>
+
 As `occupancy` requires a channel subscription, it is only available when using the realtime interface of an Ably SDK.
 
 <Aside data-type="important">

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

@@ -62,6 +62,10 @@ Seeing `channel.region.inactive` events in your [Dev Console](/docs/platform/acc
 
 A `channel.region.inactive` event indicates that a channel no longer has any clients in that specific region, or that the channel is shutting down altogether. This is part of Ably's normal operation to efficiently manage resources across its global infrastructure.
 
+<Aside data-type='see-evidence'>
+With 50% capacity headroom built in, Ably instantly absorbs traffic spikes without degradation or pre-provisioning. [Click here for evidence 🔬](https://ably.com/docs/platform/architecture/infrastructure-operations#resource-implications)
+</Aside>
+
 The following is an example of subscribing to all `[meta]channel.lifecycle` events:
 
 <Code>