remove one of the pricing sections

Author: vladvelici

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

@@ -26,7 +26,7 @@ Ably is trusted by organizations delivering chat to millions of users in realtim
 Delivering chat messages in realtime is key to a smooth online experience. Ably's [serverless architecture](/docs/platform/architecture) eliminates the need for you to manage websocket servers. It automatically scales to handle millions of concurrent connections without provisioning or maintenance. Ably also handles all of the edge-cases around delivery, failover and scaling.
 
 Despite the challenges of delivering these guarantees, Ably is designed to keep costs predictable.
-You can choose between MAU-based or per-minute pricing, depending on your needs.
+You can choose between MAU-based (more predictable for a known number of users) or per-minute pricing (consumption-based, pay for what you use), depending on your needs.
 Both pricing models are designed to be cost-effective and scalable.
 Features such as efficient connection management are available to help you reduce costs.
 
@@ -46,16 +46,6 @@ For large-scale chat scenarios with many users per room, see our [building lives
 
 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.
 
-### Pricing flexibility
-
-Depending on the specifics of your platform, you can choose between per-minute or per-MAU pricing.
-
-Note that one chat room is backed by a single Ably Pub/Sub channel. When the room is active, the channel is active.
-
-With per-minute pricing, you will be charged per message, active room (active channel), and active connection. This pricing model is ideal if you have a large number of users who might not be active for a long time. Things like deliveries, support tickets, and marketplace transactions are all good examples of this.
-
-With MAU-based pricing you will only be charged for the number of unique active users in the month (and ovarage if you go over the message limits). This pricing model is ideal if your users are very active throughout the month. Collaboration tools and some gaming scenarios are good examples of this. Paying per MAU is typically more predictable than per-minute pricing. Another use case for MAU-based pricing is if you are a platform and you also charge per MAU, to keep costs in sync with your own pricing model.
-
 ## Message throughput and rate management
 
 In task-oriented chat, each room is typically low throughput. Scaling comes by running as many rooms as you need at the same time. Ably handles everything from 1:1 conversations and small group discussions to [livestream chats](/docs/guides/chat/build-livestream) with the same reliability and scalability guarantees.
@@ -358,7 +348,7 @@ For example:
 - **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, including a cost estimator tailored to your task-oriented scenario, can be found on the [pricing page](/pricing).
+A full breakdown of pricing options can be found on the [pricing page](/pricing).
 
 ### Aggressive connection management