fixup! Tidy up commit

Author: franrob-projects

src/pages/docs/platform/integrations/queues.mdx

@@ -80,17 +80,17 @@ A [Dead Letter Queue](#deadletter) is automatically created. It stores messages
 
 ### Modifying queues <a id="modify"/>
 
-Queues cannot be modified after creation - they are immutable. Different settings require creating a new queue and migrating.
+Queues cannot be modified after creation because they are immutable. Different settings require creating a new queue and migrating.
 
-This includes limits like TTL and max length. Even after upgrading an Ably account, existing queues retain the limits they were created with. Replacement is required to get the higher limits from a new plan.
+This includes limits like TTL and max length. Even after [upgrading](/docs/account/billing-and-payments#upgrading) an Ably account, existing queues retain the limits they were created with. Replacement is required to get the higher limits from a new plan.
 
 Steps to switch to a new queue:
 
-1. Create a new queue with the desired settings
-2. Update consumers to subscribe to both the old and new queues
-3. Change queue rules to route messages to the new queue
-4. Wait for the old queue to drain completely
-5. Delete the old queue once empty
+1. Create a new queue with the required settings.
+2. Update consumers to subscribe to both the old and new queues.
+3. Change queue rules to route messages to the new queue.
+4. Wait for the old queue to drain completely.
+5. Delete the old queue once empty.
 
 This process ensures no message loss during the transition.
 

src/pages/docs/platform/integrations/webhooks/lambda.mdx

@@ -57,7 +57,6 @@ The following steps show you how to create a policy for an AWS Lambda.
 
 <Code>
 ```json
-{
 {
   "Version": "2012-10-17",
   "Statement": [
@@ -106,7 +105,7 @@ Then ensure the checkbox for the policy is selected.
 9. Enter a suitable name for your role.
 10. Click **Create Role**.
 
-## Lambda retry behavior <a id="retries"/>
+## Lambda retry behavior <a id="retry"/>
 
 Ably invokes Lambda functions asynchronously using the `event` invocation type. When a function returns an error, AWS Lambda automatically retries the execution up to two more times with delays between attempts (1 minute, then 2 minutes).