fix(mnq): started screenshots

Author: RoRoJ

serverless/messaging/how-to/assets/scaleway-nats-creds.webp

@@ -15,7 +15,7 @@ dates:
 
 This page shows how to create [credentials](/serverless/messaging/concepts/#credentials) for Scaleway **NATS**, **Queues** and **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). Credentials give their bearer (e.g. services and platforms) access to your service. 
 
-You can create multiple sets of credentials for each of your NATS accounts, Queues and Topics and Events services.
+You can create multiple sets of credentials for each of your NATS accounts, and for your Queues and Topics and Events services.
 
 <Macro id="requirements" />
 
@@ -28,17 +28,19 @@ Credentials for NATS accounts are not granular: they necessarily give full read
 
 1. Click **NATS** in the **Serverless** section of the Scaleway console side menu. 
 
-2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the NATS account for which you want to create credentials.
+2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the NATS account for which you want to create credentials. The list of your NATS accounts in the pre-selected region displays.
 
-3. Click **NATS**. The list of your NATS accounts in the pre-selected region displays.
+3. Click the NATS account you want to generate credentials for. The account's **Overview** page displays.
 
-4. Click the NATS account you want to generate credentials for. The account's **Overview** page displays.
+    <Lightbox src="scaleway-nats-overview.webp" alt="In the Scaleway console, the Overview tab of a NATS account is displayed. Three panels are visible: account information (URL and region), Credentials, adn Delete NATS account." />
 
-5. In the **Credentials** panel, click **Generate credentials**. A pop-up displays.
+4. In the **Credentials** panel, click **Generate credentials**. A pop-up displays.
 
 6. Enter a name for these credentials, and click **Generate credentials**.
 
-    The credentials are created and a button displays prompting you to download them in a `.creds` file. 
+    The credentials are created and a button displays prompting you to download them in a `.creds` file.
+
+    <Lightbox src="scaleway_nats_creds.webp" alt="In the Scaleway console, a screen shows that a .creds key file has been generated, which the user is prompted to download." />
 
     <Message type="important">
       The generated credentials are displayed only once. Make sure to download and safely store them before closing the window.
@@ -50,14 +52,16 @@ Credentials for NATS accounts are not granular: they necessarily give full read
 
 ## How to create credentials for Queues
 
-Credentials for Queues are granular: you can define the level of access that they should give.
+Credentials for Queues are granular: you can define the level of access that they should give. Credentials give the specified level of access to all queues that you create in the region they are scoped to.
 
-1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. The **Queues** dashboard displays.
+1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. A list of your queues displays.
 
-2. Click the **Credentials** tab. 
+2. Click the **Credentials** tab.
 
 3. Click **Generate credentials**. A pop-up displays:
 
+    <Lightbox src="scaleway-queues-gen-creds.webp" alt="In the Scaleway console, the Generate credentials screen displays. It prompts the user to choose a region for their credentials, a name, and permissions (write, read and/or manage)" />
+
 4. Choose a region that these credentials should be scoped to.
 
 5. Enter a name for these credentials.
@@ -78,15 +82,15 @@ Credentials for Queues are granular: you can define the level of access that the
 
 ## How to create credentials for Topics and Events
 
-Credentials for Topics and Events are granular: you can define the level of access that they should give.
+Credentials for Topics and Events are granular: you can define the level of access that they should give. Credentials give the specified level of access to all topics that you create in the region they are scoped to.
 
 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. The **Topics and Events** dashboard displays.
 
 2. Click the **Credentials** tab. 
 
 3. Click **Generate credentials**. A pop-up displays:
 
-      TODO screenshot for Topics and Events
+    <Lightbox src="scaleway-topics-gen-creds.webp" alt="In the Scaleway console, the Generate credentials screen displays. It prompts the user to choose a region for their credentials, a name, and permissions (write, read and/or manage)" />
 
 4. Choose a region that these credentials should be scoped to.
 

serverless/messaging/how-to/assets/scaleway-nats-overview.webp

@@ -25,7 +25,7 @@ This page shows how to create and manage your Scaleway [Queues](/serverless/mess
 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu.
 
 2. Click **Create queue**. The Qqeue creation wizard displays.
-    TODO SCREENSHOT
+    <Lightbox src="scaleway-queues-create-queue.webp" alt="In the Scaleway console, the Create a Queue screen displays. The different sections of the screen are described in the steps below." />
 
 3. Select the [region](/serverless/messaging/concepts/#region) in which you want to create the queue.
 
@@ -39,7 +39,7 @@ This page shows how to create and manage your Scaleway [Queues](/serverless/mess
     - **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).
     - **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.
+    - **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.
 
 7. Click **Create queue** to finish.
 
@@ -48,22 +48,22 @@ You are returned to the **Queues** tab, where your newly-created queue now displ
 Go further by clicking on the queue's name to access its **Settings** page and see additional information such as its ARN (Amazon Resource Name) and configuration parameters.
 
 <Message type="tip">
-Remember that you need to [create credentials](/serverless/messaging/how-to/create-credentials/) in order to access your Queues from an API or CLI. Sending messages to Queues requires that credentials have the `can_publish` permission, while receiving messages from Queues requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application.
+Remember that you need to [create credentials](/serverless/messaging/how-to/create-credentials/) in order to access your queues from an API or CLI. Sending messages to queues requires that credentials have the `can_publish` permission, while receiving messages from queues requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application.
 </Message>
 
 ## How to modify a queue's configuration
 
-You can modify the visibility timeout, message retention period and maximum message size of a queue after creation. You can also modify the content based deduplication settings for FIFO Queues. However, you cannot change a queue's name or type after creation.
+You can modify the visibility timeout, message retention period and maximum message size of a queue after creation. You can also modify the content based deduplication settings for FIFO queues. However, you cannot change a queue's name or type after creation.
 
 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu.
 
-2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to configure.
+2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to modify.
 
 3. Click the queue you wish to modify. The queue's **Settings** page displays:
 
-    TODO SCREENSHOT
+    <Lightbox src="scaleway-queues-queue-settings.webp" alt="In the Scaleway console, the queue's settings displays includes a Queue information panel (showing its type, number of messages, region, creation date, URL and ARN), a Queue information panel (with visibility timeout, message retention period, max message size and content based deduplication settings), and a Delete queue panel (with a button to delete the queue)." />
 
-4. Modify the visibility timeout, message retention period, maximum message size, and (for FIFO Queues) content-based deduplication values as you wish.
+4. Modify the visibility timeout, message retention period, maximum message size, and (for FIFO queues) content-based deduplication values as you wish.
 
 5. Click **Save**.
 
@@ -81,7 +81,7 @@ You can use the **Purge** feature to delete all messages from a queue.
 
     A pop-up asks you to confirm that you understand this action will delete all your queued messages.
 
-5. Type **PURGE** and click **Purge Queue**.
+5. Type **PURGE** and click **Purge queue**.
 
 ## How to delete a queue