fixes based on reivew comments

Author: vladvelici

src/pages/docs/guides/chat/build-task-oriented.mdx

@@ -40,9 +40,9 @@ For large-scale chat scenarios with many users per room, see our [building lives
 
 **Task-oriented room architecture:** The optimal approach is one chat room per task, where all participants join to communicate within that specific context. Rooms are:
 
-* **Automatically scaled** - Ably handles any number of concurrent rooms without provisioning
-* **History-enabled** - messages stored for 30 days by default (configurable up to a year on request)
-* **Kept under control** - [capabilites](/docs/chat/setup#authentication) let you control who can join and the level of access to features and actions
+* **Automatically scaled** - Ably handles any number of concurrent rooms without provisioning.
+* **History-enabled** - messages stored for 30 days by default (configurable up to a year on request).
+* **Kept under control** - [capabilites](/docs/chat/setup#authentication) let you control who can join and the level of access to features and actions.
 
 Each room includes all task participants: customers and agents in support, buyers and sellers in marketplaces, players in games, team members in projects. Participants can join and leave as the task evolves. Access to message history and other features can be granted to all or select participants via capabilities.
 
@@ -78,7 +78,7 @@ const header = {
 }
 const currentTime = Math.round(Date.now() / 1000);
 
-// The clientID could be the users ID in your application,
+// The clientId could be the users ID in your application,
 // or a random string if you want to make users anonymous.
 //
 // The capabilities here allow the holder of this token to publish and subscribe to messages,
@@ -103,11 +103,11 @@ console.log('JWT is: ' + ablyJwt);
 
 How you authenticate is also key. To balance security and experience, you want short-lived tokens that can be easily revoked if a user is misbehaving or needs their permissions changed, but automatically expire after a period of time. This means that if a token is compromised, it will only be valid for a limited time. **In production apps, you should not use API keys for client-side authentication**. You can use them server-side, but as they are long-lived and require explicit revocation, exposure to untrusted users poses a continuing risk.
 
-Authentication is best achieved using JSON Web Tokens (JWTs). These are tied to a particular clientID and come with a set of [capabilities](/docs/chat/setup#authentication) that control what a client can and cannot do - for example whether they can send messages, join a certain room or moderate. Ably's SDKs handle the timing and process of requesting a new token for you, refreshing it when it expires. All you need to do is provide a server-side endpoint that can generate the JWT for the client. This enables clients to use your existing authentication systems or user sessions to generate their Ably token.
+Authentication is best achieved using JSON Web Tokens (JWTs). These are tied to a particular `clientId` and come with a set of [capabilities](/docs/chat/setup#authentication) that control what a client can and cannot do - for example whether they can send messages, join a certain room or moderate. Ably's SDKs handle the timing and process of requesting a new token for you, refreshing it when it expires. All you need to do is provide a server-side endpoint that can generate the JWT for the client. This enables clients to use your existing authentication systems or user sessions to generate their Ably token.
 
-## Presence: Know who's available for your task
+## Presence: Know who's available in the room
 
-Ably's [presence](/docs/chat/rooms/presence) feature shows you who's currently active in your task-oriented chat. This is especially valuable for scenarios where task completion depends on participant availability:
+[Presence](/docs/chat/rooms/presence) shows you who's currently active in the room. This is especially valuable for scenarios where task completion depends on participant availability:
 
 * **Support tickets:** See when agents are online and available to help.
 * **Deliveries:** Know if the delivery driver or customer is actively monitoring the chat.
@@ -122,9 +122,28 @@ Beyond just online/offline status, presence can include rich information:
 
 This contextual presence information helps participants understand not just who's online, but who's ready and able to engage with the current task.
 
+```javascript
+// subscribe to presence events
+const { unsubscribe } = room.presence.subscribe((event) => {
+  console.log(`${event.member.clientId} entered with data: ${event.member.data}`);
+
+  const presentMembers = await room.presence.get();
+  console.log('Present members:', presentMembers);
+});
+
+// join presence
+await room.presence.enter({ status: 'available' });
+
+// change presence data
+await room.presence.enter({ status: 'busy' });
+
+// leave presence
+await room.presence.leave();
+```
+
 ## Typing indicators
 
-Typing indicators are now a common feature in most chat applications. They show when someone is actively composing a message, helping to:
+[Typing indicators](/docs/chat/rooms/typing) are a common feature in most chat applications. They show when someone is actively composing a message, helping to:
 
 * **Manage expectations:** Users know when a response is being prepared.
 * **Reduce duplicate messages:** See that someone is already addressing the question.
@@ -171,8 +190,9 @@ Message reactions in Ably Chat come in three types: `unique`, `distinct` and `mu
 
 Message history is crucial for task-oriented chats, ensuring continuity and context even when participants join mid-task or return after interruptions.
 
-Ably stores [chat history](/docs/chat/rooms/history) for 30 days by default, with options to extend up to a year.
+Ably stores [chat history](/docs/chat/rooms/history) for 30 days by default, with options to extend up to a year on request.
 
+Message history provides users with:
 * **Task continuity:** New participants can quickly understand the current state and previous decisions.
 * **Context preservation:** Users returning to a task don't lose important information.
 * **Audit trail:** Complete conversation records for compliance, training, or dispute resolution.
@@ -197,7 +217,17 @@ const subscription = room.messages.subscribe((messageEvent) => {
 
 // Load recent history for context
 // This ensures you get a complete picture without missing messages
-await subscription.historyBeforeSubscription({limit: 50});
+let historyResponse = await subscription.historyBeforeSubscription({limit: 50});
+
+// Itarate through all pages
+while (true) {
+  console.log('Messages: ', historyResponse.items);
+  if (historyResponse.hasNext()) {
+    historyResponse = await historyResponse.next();
+  } else {
+    break;
+  }
+}
 ```
 </Code>
 
@@ -210,10 +240,10 @@ See the [React UI Kit](/docs/chat/react-ui-kit) for more details.
 Ably's comprehensive platform enables you to combine chat with other realtime features to create rich, interactive task experiences.
 
 **Pub/Sub channels** add interactive elements:
-- **Live polls:** Quick feedback during collaborative decisions
-- **Status updates:** Real-time progress indicators for tasks
-- **Interactive ratings:** Instant feedback collection
-- **Live auctions:** Real-time bidding in marketplace scenarios
+- **Live polls:** Quick feedback during collaborative decisions.
+- **Status updates:** Real-time progress indicators for tasks.
+- **Interactive ratings:** Instant feedback collection.
+- **Live auctions:** Real-time bidding in marketplace scenarios.
 
 These combined services transform basic chat into comprehensive task management platforms, where communication, coordination, and real-time updates work together seamlessly.
 
@@ -235,11 +265,11 @@ Best for most task-oriented scenarios, where immediacy often matters. It can be
      * **Hate speech and harassment:** Detecting discriminatory language, threats, or targeted abuse.
      * **Discrimination:** Detecting discriminatory language, threats, or targeted abuse.
      * **Inappropriate content:** Flagging adult content, violence, or graphic material.
-     * **Toxicity:** Measuring overall message sentiment and hostility
+     * **Toxicity:** Measuring overall message sentiment and hostility.
 
 2. **Technical integration**
    * **Latency impact:** AI moderation adds up to 100ms to message delivery.
-   * **Integration options:** Choose from pre-built integrations or connect your existing moderation systems via webhooks, serverless functions, or queues
+   * **Integration options:** Choose from pre-built integrations or connect your existing moderation systems via webhooks, serverless functions, or queues.
 
 3. **Task-specific approaches**
    * **Customer support:** Protect both customers and agents from abuse and harassment.
@@ -279,15 +309,15 @@ AI chatbots are revolutionizing the way we interact with digital platforms. Inte
 
 Ably's flexible [integration capabilities](/docs/platform/integrations) make it easy to connect your chat system with AI services. Through Ably's integrations, you can automatically route messages to:
 
-* Serverless functions (AWS Lambda, Azure Functions, etc.),
-* Event streaming services including Kafka, SQS and Pulsar,
+* Serverless functions (AWS Lambda, Azure Functions, and others).
+* Event streaming services including Kafka, SQS and Pulsar.
 * Webhooks and custom endpoints.
 
 This enables powerful AI features like:
 
-* Sentiment analysis of chat messages,
-* AI-powered responses to common questions and support queries,
-* Chat summarization and key point extraction,
+* Sentiment analysis of chat messages.
+* AI-powered responses to common questions and support queries.
+* Chat summarization and key point extraction.
 * Automatically adding contextual information for your agents to help them be more effective.
 
 For example, you could set up an integration that sends all messages from each chat room to an AI service for sentiment analysis,
@@ -333,20 +363,20 @@ Task-oriented chats are typically short-lived but can be numerous, making effici
 
 **Consumption-based pricing** is ideal for most task-oriented scenarios:
 
-* **Pay per message/minute:** Only pay for actual engagement, perfect for sporadic task conversations
-* **Volume discounts:** Lower rates as your usage scales across all your tasks
-* **No user-based fees:** You're not charged for users who join briefly or tasks that end quickly
+* **Pay per message/minute:** Only pay for actual engagement, perfect for sporadic task conversations.
+* **Volume discounts:** Lower rates as your usage scales across all your tasks.
+* **No user-based fees:** You're not charged for users who join briefly or tasks that end quickly.
 
 **MAU-based pricing** works well when you have:
 
-* **Consistent task volume:** Regular support tickets, frequent deliveries, or ongoing collaborative work
-* **Predictable user engagement:** Teams or customers who regularly participate in tasks
-* **Longer-term task relationships:** Ongoing gaming communities or service subscriptions
+* **Consistent task volume:** Regular support tickets, frequent deliveries, or ongoing collaborative work.
+* **Predictable user engagement:** Teams or customers who regularly participate in tasks.
+* **Longer-term task relationships:** Ongoing gaming communities or service subscriptions.
 
 For example:
-- **Support platforms:** Often benefit from consumption pricing due to variable ticket volume
-- **Delivery services:** MAU pricing if you have consistent delivery personnel and customers
-- **Gaming platforms:** Consumption pricing for casual games, MAU for subscription-based gaming
+- **Support platforms:** Often benefit from consumption pricing due to variable ticket volume.
+- **Delivery services:** MAU pricing if you have consistent delivery personnel and customers.
+- **Gaming platforms:** Consumption pricing for casual games, MAU for subscription-based gaming.
 
 A full breakdown of pricing options can be found on the [pricing page](/pricing).