fix(sqs): Fixing typoed max message retenion value in seconds ext-fix-sqs (#4679)

Author: Kantis

pages/messaging/quickstart.mdx

@@ -139,7 +139,7 @@ Credentials for Queues are granular: you can define the level of access that the
 
 6. Configure your queue's **parameters**. The following parameters can be defined:
     - **Visibility timeout**: The length of time (in seconds) during which, after a message is received, it is hidden and cannot be received again by the same or other consumers. This is useful as the queue itself does not automatically delete messages once they are received, and so prevents consumers from receiving the same message many times before they have finished processing it. Therefore, the value set here should be informed by the expected length of time it will take consumers to process messages. The default value is 30 seconds. The value must be between 1 second and 43 200 seconds (12 hours).
-    - **Message retention period**: The length of time (in seconds) that messages are kept in the queue before being deleted. Setting a longer message retention period allows for a longer interval between a message being sent and it being received. The default value is 60 seconds. The value must be between 60 seconds and 1 290 600 seconds (14 days).
+    - **Message retention period**: The length of time (in seconds) that messages are kept in the queue before being deleted. Setting a longer message retention period allows for a longer interval between a message being sent and it being received. The default value is 60 seconds. The value must be between 60 seconds and 1 209 600 seconds (14 days).
     - **Maximum message size**: The maximum size (in kilobytes) of a message that can be sent to the queue. Messages greater than the defined size will be rejected. The default value is 256 KB. The value must be between 1 KB and 256 KB.
     - **Content Based Deduplication**: This setting is only available for FIFO queues. Enable content-based deduplication if the message body is guaranteed to be unique for each message. A unique hash value is generated from the body of each message, which is used as its deduplication ID. This avoids the need to set a deduplication ID when sending messages.
 
@@ -293,4 +293,4 @@ When you no longer want a topic, you can delete it. This action is irreversible
 
     A pop-up asks you to confirm that you understand this action will delete the topic and all of its associated subscriptions.
 
-4. Type **DELETE** and click **Delete topic**.
+4. Type **DELETE** and click **Delete topic**.