task-oriented chat: add per connect in chargeable items list in per-minute pricing

Author: vladvelici

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

@@ -52,7 +52,7 @@ Depending on the specifics of your platform, you can choose between per-minute o
 
 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 and active room (active channel). 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 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.