Apply suggestions from code review

Author: Oxyjun

src/content/docs/queues/configuration/pause-purge.mdx

@@ -8,26 +8,31 @@ import { WranglerConfig, Type, MetaInfo } from "~/components";
 
 ## Pause Delivery
 
-You can pause delivery of messages from your Queue to any connected consumers. Pausing a queue is useful to manage downtime (such as if your consumer Worker is unhealthy), without losing any messages.
+You can pause delivery of messages from your Queue to any connected consumers. Pausing a Queue is useful when managing downtime (for example, if your consumer Worker is unhealthy) without losing any messages.
 
 Queues continue to receive and store messages even while delivery is paused. Messages in a paused queue are still subject to expiry, if the messages become older than the queue message retention period.
 
-Pausing affects both [push-based consumer Workers](/queues/reference/how-queues-works#consumers), and [pull based consumers](/queues/configuration/pull-consumers).
+Pausing affects both [push-based consumer Workers](/queues/reference/how-queues-works#consumers) and [pull based consumers](/queues/configuration/pull-consumers).
 
 ### Pause and resume delivery using Wrangler
+
 The following command will pause message delivery from your queue:
+
 ```sh
 $ npx run wrangler queues pause-delivery <QUEUE-NAME>
 ```
+
 - `queue-name` <Type text="string" /> <MetaInfo text="required" />
-  - The name of the queue which delivery should be paused.
+  - The name of the queue for which delivery should be paused.
 
 The following command will resume message delivery:
+
 ```sh
 $ npx run wrangler queues resume-delivery <QUEUE-NAME>
 ```
+
 - `queue-name` <Type text="string" /> <MetaInfo text="required" />
-  - The name of the queue from which delivery should be resumed.
+  - The name of the queue for which delivery should be resumed.
 
 ### What happens to HTTP Pull consumers with a paused queue?
 When a queue is paused, messages cannot be pulled by an [HTTP pull based consumer](/queues/configuration/pull-consumers). Requests to pull messages will receive a `409` response, along with an error message stating `queue_delivery_paused`.
@@ -37,11 +42,11 @@ Purging a queue permanently deletes any messages currently stored in the Queue.
 
 Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the Queue.
 
-:::note
+:::caution
 Purging a queue is an irreversible operation. Make sure to use this operation carefully.
 :::
 
-### Purge queue using wrangler
+### Purge queue using Wrangler
 The following command will purge messages from your Queue. You will be prompted to enter the Queue name to confirm the operation.
 ```sh
 $ npx run wrangler queues purge <QUEUE-NAME>

src/content/docs/workers/wrangler/commands.mdx

@@ -1356,7 +1356,7 @@ Permanently delete all messages in a queue.
 wrangler queues purge <queue-name>
 ```
 - `queue-name` <Type text="string" /> <MetaInfo text="required" />
-  - The name of the queue which delivery should be purged.
+  - The name of the queue for which delivery should be purged.
 
 ### `pause-delivery`