EDU-1710: Integrations consistenecy

content/account/app/queues.textile

@@ -16,16 +16,14 @@ The  Ably queues tab enables you to:
 
 h3. Provision a new queue
 
-When provisioning a new queue, you'll need to specify several things:
+When provisioning a "new queue":/docs/integrations/queues#prov, you'll need to specify several things:
 
 |_. Field |_. Description |
-| *Name* | Choose a unique name for your queue. This will help you identify it within your dashboard and during application development. |
-| *Region* | Select the geographic region where the queue will be hosted. This is important for optimizing latency and ensuring data residency aligns with your application's requirements. |
-| *TTL (time to Live)* | Set the TTL, which determines how long messages remain in the queue before being automatically deleted if they are not consumed. The default account limit is 60 minutes. You can contact Ably support for assistance if you need a longer TTL. |
-| *Max length* | Define the maximum number of messages the queue can hold at any given time. The default limit is 10,000 messages, but you can request an increase if your application requires more capacity. |
+| *Name* | Enter a unique name for your queue. This name, combined with your app ID, forms the full queue identifier. |
+| *Region* | Select the physical region where the queue will be hosted, for example, US East (Virginia). All queues are replicated across two datacenters in that region for high availability. |
+| *TTL (time to Live)* | Set the time-to-live for messages. The default and maximum is 60 minutes. Messages that are not consumed within the TTL will be moved to the "dead letter Queue":/docs/integrations/queues#deadletter. |
+| *Max length* | Define the maximum number of messages the queue can retain. The default and maximum is 10,000. When the queue is full, the oldest message is moved to the dead letter queue to make space. |
 
 h3(#setup). Set up queue rules
 
-Once you have provisioned a physical queue, you need to set up one or more queue rules to republish messages, presence events or channel events from pub/sub channels into a queue. Queue rules can either be used to publish to internal queues (hosted by Ably) or external external streams or queues (such as Amazon Kinesis and RabbitMQ). Publishing to external streams or queues is part of our "Ably Firehose servers":/docs/general/firehose.
-
-Ably queue rules are setup in the *Integrations* tab found within your app *dashboard*. Find out more about setting up "queue rules":/docs/integrations/queues#setup.
+Once you have provisioned a physical queue, you need to "set up":/docs/integrations/queues#setup one or more queue rules to republish messages, presence events or channel events from pub/sub channels into a queue. Queue rules can either be used to publish to internal queues (hosted by Ably) or external external streams or queues (such as Amazon Kinesis and RabbitMQ). Publishing to external streams or queues is part of our "Ably Firehose servers":/docs/general/firehose..