Fixup following Paddy review

Author: rainbowFi

src/pages/docs/ai-transport/index.mdx

@@ -153,4 +153,4 @@ The cost of streaming token responses over Ably depends on:
 - the number of subscribers receiving the response.
 - the [token streaming pattern](/docs/ai-transport/features/token-streaming#token-streaming-patterns) you choose.
 
-For example, an AI support chatbot sending a response of 250 tokens at 70 tokens/s to a single client using the [message-per-response](/docs/ai-transport/features/token-streaming/message-per-response) pattern would consume 90 inbound messages, 90 outbound messages and 90 persisted messages. See the [AI support chatbot pricing example](/docs/platform/pricing/examples/ai-chatbot) for a full breakdown of the costs in this scenario.
+For example, suppose an AI support chatbot sends a response of 300 tokens, each as a discrete update, using the [message-per-response](/docs/ai-transport/features/token-streaming/message-per-response) pattern, and with a single client subscribed to the channel. With AI Transport's [append rollup](/docs/ai-transport/messaging/token-rate-limits#per-response), this will result in usage of 100 inbound messages, 100 outbound messages and 100 persisted messages. See the [AI support chatbot pricing example](/docs/platform/pricing/examples/ai-chatbot) for a full breakdown of the costs in this scenario.

src/pages/docs/platform/pricing/examples/ai-chatbot.mdx

@@ -1,5 +1,5 @@
 ---
-title: AI support chatbot
+title: AI support chatbot pricing example
 meta_description: "Calculate AI Transport pricing for conversations with an AI chatbot. Example shows how using the message-per-response pattern and modifying the append rollup window can generate cost savings."
 meta_keywords: "chatbot, support chat, token streaming, token cost, AI Transport pricing, Ably AI Transport pricing, stream cost, Pub/Sub pricing, realtime data delivery, Ably Pub/Sub pricing"
 intro: "This example uses consumption-based pricing for an AI support chatbot use case, where a single agent is publishing tokens to user over AI Transport."
@@ -12,7 +12,7 @@ The scale and features used in this calculation.
 | Scale | Features |
 |-------|----------|
 | 4 user prompts to get to resolution | ✓ Message-per-response |
-| 250 tokens per LLM response | |
+| 300 token events per LLM response | |
 | 75 appends per second from agent | |
 | 3 minute average chat duration | |
 | 1 million chats | |
@@ -23,32 +23,25 @@ The high level cost breakdown for this scenario is given in the table below. Mes
 
 | Item | Calculation | Cost |
 |------|-------------|------|
-| Messages | 1092M × $2.50/M | $2730 |
+| Messages | 1212M × $2.50/M | $3030 |
 | Connection minutes | 6M × $1.00/M | $6 |
 | Channel minutes | 3M × $1.00/M | $3 |
 | Package fee |  | [See plans](/pricing) |
-| **Total** |  | **~$2739/M chats** |
+| **Total** |  | **~$3039/M chats** |
 
 ### Message usage breakdown
 
 Several factors influence the total message usage. The message-per-response pattern includes [automatic rollup of append events](/docs/ai-transport/features/token-streaming/token-rate-limits#per-response) to reduce consumption costs and avoid rate limits.
 
+- Agent stream time: 300 token events ÷ 75 appends per second = 4 seconds of streaming per response
+- Messages published after rollup: 4 seconds x 25 messages/s = **100 messages per response**
+
 | Type | Calculation | Inbound | Outbound | Total messages | Cost |
 |------|-------------|---------|----------|----------------|------|
 | User prompts | 1M chats × 4 prompts | 4M | 4M | 8M | $20 |
-| Agent responses | 1M chats x 4 responses x 250 token events per response | 360M | 360M | 720M | $1800 |
-| Persisted messages | Every inbound message is persisted | 364M | 0 | 364M | $910 |
-| **Total** | | **728M** | **364M** | **1092M** | **$2730** |
-
-### Effect of append rollup
-
-The calculation above uses the default append rollup window of 40ms, chosen to control costs with minimum impact on responsiveness. For a text chatbot use case, you could increase the window to 200ms without noticably impacting the user experience.
-
-| Rollup window | Inbound response messages | Total messages | Cost |
-|---------------|---------------------------|----------------|------|
-| 40ms | 360 per chat | 1092M | $2730/M chats |
-| 100ms | 144 per chat | 444M | $1110/M chats |
-| 200ms | 72 per chat | 228M | $570/M chats |
+| Agent responses | 1M chats x 4 responses x 100 messages per response | 400M | 400M | 800M | $2000 |
+| Persisted messages | Every inbound message is persisted | 404M | 0 | 404M | $1010 |
+| **Total** | | **808M** | **404M** | **1212M** | **$3030** |
 
 <Aside data-type='further-reading'>
 Useful links for exploring this topic in more detail.