Update configure-queues.mdx

Author: maheshwarip

src/content/docs/queues/configuration/configure-queues.mdx

@@ -14,20 +14,20 @@ import { WranglerConfig, Type } from "~/components";
 Cloudflare Queues can be configured using [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Cloudflare's Developer Platform, which includes [Workers](/workers/), [R2](/r2/), and other developer products.
 
 
-Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a Queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
+Each Producer and Consumer Worker has a [Wrangler configuration file](/workers/wrangler/configuration/) that specifies environment variables, triggers, and resources, such as a queue. To enable Worker-to-resource communication, you must set up a [binding](/workers/runtime-apis/bindings/) in your Worker project's Wrangler file.
 
 Use the options below to configure your queue.
 
 :::note
 
 
-Below are options for Queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
+Below are options for queues, refer to the Wrangler documentation for a full reference of the [Wrangler configuration file](/workers/wrangler/configuration/).
 
 
 :::
 
 ## Queue configuration
-The following Queue level settings can be configured using Wrangler:
+The following queue level settings can be configured using Wrangler:
 
 ```sh
 $ npx run wrangler queues update --delivery-delay-secs 60 --message-retention-period-secs 3000
@@ -63,7 +63,7 @@ To produce to a queue, set up a binding in your Wrangler file. These options sho
 
 * <code>queue</code> <Type text="string" />
 
-  * The name of the Queue.
+  * The name of the queue.
 
 * <code>binding</code> <Type text="string" />
 
@@ -96,7 +96,7 @@ Refer to [Limits](/queues/platform/limits) to review the maximum values for each
 
 * <code>queue</code> <Type text="string" />
 
-  * The name of the Queue.
+  * The name of the queue.
 
 * <code>max\_batch\_size</code> <Type text="number" /> <Type text="optional" />
 
@@ -115,9 +115,9 @@ Refer to [Limits](/queues/platform/limits) to review the maximum values for each
 
 * <code>dead\_letter\_queue</code> <Type text="string" /> <Type text="optional" />
 
-  * The name of another Queue to send a message if it fails processing at least `max_retries` times.
+  * The name of another queue to send a message if it fails processing at least `max_retries` times.
   * If a `dead_letter_queue` is not defined, messages that repeatedly fail processing will eventually be discarded.
-  * If there is no Queue with the specified name, it will be created automatically.
+  * If there is no queue with the specified name, it will be created automatically.
 
 * <code>max\_concurrency</code> <Type text="number" /> <Type text="optional" />