Apply suggestions from code review

RoRoJ · bene2k1 · nerda-codes · RoRoJ · commit 2bfc964c917a · 2024-11-20T14:32:38.000+01:00
Co-authored-by: Benedikt Rollik &lt;brollik@scaleway.com&gt;
Co-authored-by: nerda-codes &lt;87707325+nerda-codes@users.noreply.github.com&gt;
diff --git a/faq/messaging-and-queuing.mdx b/faq/messaging-and-queuing.mdx
@@ -31,16 +31,16 @@ The following subscriber types are supported:
 
 For more details on supported and unsupported Topics and Events features, see our [dedicated page](/serverless/messaging/reference-content/sns-support/).
 
-## Can I configure Scalewat NATS via Terraform?
+## Can I configure Scaleway NATS via Terraform?
 
-Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on how to configure with the Terraform [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs).
+Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on how to configure Scaleway NATS with the Terraform [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs).
 
 ## How are NATS, Queues, and Topics and Events billed?
 
 Billing is based on:
 
 - For NATS: [Stream volume](/serverless/messaging/concepts/#stream-volume) (the total sum of each message's size going through the stream) and [stream persistence](/serverless/messaging/concepts/#stream-persistence) (the total amount of data stored * duration)
 - For Queues: [Queue volume](/serverless/messaging/concepts/#queue-volume) (the total sum of each message's size going through the queue)
-- For Topics and Events : [Topic Volume](/serverless/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions)
+- For Topics and Events: [Topic Volume](/serverless/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions)
 
 For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/).
diff --git a/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx b/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx
@@ -15,7 +15,7 @@ categories:
 
 A webhook is an automated message sent in real-time from one system to another when a specific event happens, the message is typically conveyed using HTTP requests that are sent to an endpoint of your choice.
 
-You can set up webhooks for Scaleway Transaction Email and subscribe them to [Topics and Events topics](/serverless/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints.
+You can set up webhooks for Scaleway Transactional Email and subscribe them to [Topics and Events topics](/serverless/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints.
 
 
 <Macro id="requirements" />
diff --git a/serverless/functions/reference-content/use-cases.mdx b/serverless/functions/reference-content/use-cases.mdx
@@ -38,7 +38,7 @@ This example shows how to handle different HTTP methods (POST and GET) as well a
 
 ## Go - Queues Publish message
 
-You can use this example to publish a message to an Scaleway queue using the MNQ namespace from the Scaleway Go SDK.
+You can use this example to publish a message to a Scaleway queue using the MNQ namespace from the Scaleway Go SDK.
 
 [MNQ SQS Publish message using Golang](https://github.com/scaleway/serverless-examples/blob/main/functions/go-mnq-sqs-publish/README.md)
 
diff --git a/serverless/messaging/api-cli/python-node-sqs.mdx b/serverless/messaging/api-cli/python-node-sqs.mdx
@@ -118,7 +118,7 @@ sqs = boto3.resource('sqs',
   The `endpoint_url` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Queues.
 </Message>
 
-Once connected, you can use any functions available with the SDK - just check that they're [supported by Scaleway Queues](/serverless/messaging/reference-content/sqs-support/). See the [official documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more details, or read on to see some examples.
+Once connected, you can use any functions available with the SDK - just check that they are [supported by Scaleway Queues](/serverless/messaging/reference-content/sqs-support/). See the [official documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more details, or read on to see some examples.
 
 ### Create queue (Python)
 
diff --git a/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx b/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx
@@ -174,7 +174,7 @@ The AWS-CLI is an open-source tool built on top of the AWS SDK for Python (Boto)
     aws sns unsubscribe --subscription-arn $(jq -r .SubscriptionArn my-subscription.json)
     ```
 
-6. Use the following command to delete the Scaleway queue (if you had an Scaleway Queues target):
+6. Use the following command to delete the Scaleway queue (if you had a Scaleway Queues target):
 
     ```sh
     aws sqs delete-queue --queue-url $(jq -r .QueueUrl my-queue.json)
diff --git a/serverless/messaging/concepts.mdx b/serverless/messaging/concepts.mdx
@@ -51,7 +51,7 @@ A message broker is a piece of software that allows applications, systems and se
 
 ## Message retention period
 
-The message retention period is a setting that can be configured for a  queue. It represents 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. Read more in our dedicated documentation on [creating queues](/serverless/messaging/how-to/create-manage-queues/).
+The message retention period is a setting that can be configured for a queue. It represents 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. Read more in our dedicated documentation on [creating queues](/serverless/messaging/how-to/create-manage-queues/).
 
 ## Messaging and Queuing
 
diff --git a/serverless/messaging/how-to/create-credentials.mdx b/serverless/messaging/how-to/create-credentials.mdx
@@ -36,7 +36,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read
 
 4. In the **Credentials** panel, click **Generate credentials**. A pop-up displays.
 
-6. Enter a name for these credentials, and click **Generate credentials**.
+5. 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.
 
diff --git a/serverless/messaging/how-to/create-manage-queues.mdx b/serverless/messaging/how-to/create-manage-queues.mdx
@@ -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**.
+4. Type **PURGE** and click **Purge queue**.
 
 ## How to delete a queue
 
diff --git a/serverless/messaging/how-to/create-manage-subscriptions.mdx b/serverless/messaging/how-to/create-manage-subscriptions.mdx
@@ -32,7 +32,7 @@ This page shows how to create and manage [subscriptions](/serverless/messaging/c
 4. Click **Create Subscription**. The subscription creation wizard displays.
     <Lightbox src="scaleway-topics-create-subs.webp" alt="In the Scaleway console, the Create a Subscription screen displays. The different sections of the screen are described in the steps below" />
 
-5. Verify the parameters of the topic that you are creating a subscription for (name, type and).
+5. Verify the parameters of the topic that you are creating a subscription for (name, and type).
 
 6. Choose a protocol, based on the type of endpoint or client you want to subscribe. Click the tab below for further details and full instructions on each protocol:
 
diff --git a/serverless/messaging/how-to/manage-credentials.mdx b/serverless/messaging/how-to/manage-credentials.mdx
@@ -55,7 +55,7 @@ Credentials for **Queues** and **Topics and Events** can be updated to change th
 
     A pop-up displays, warning you that this action is irreversible and the key will no longer be able to access your service.
 
-4. Click **Revoke credentials**.
+5. Click **Revoke credentials**.
 
     The credentials are revoked and you are returned to the product's **Credentials** listing.
 
diff --git a/serverless/messaging/quickstart.mdx b/serverless/messaging/quickstart.mdx
@@ -230,7 +230,7 @@ You are returned to the **Topics** tab, where your newly-created topic now displ
 4. Click **Create Subscription**. The subscription creation wizard displays.
     <Lightbox src="scaleway-topics-create-subs.webp" alt="In the Scaleway console, the Create a Subscription screen displays. The different sections of the screen are described in the steps below" />
 
-5. Verify the parameters of the topic that you are creating a subscription for (name, type and).
+5. Verify the parameters of the topic that you are creating a subscription for (name and type).
 
 6. Choose a protocol, based on the type of endpoint or client you want to subscribe. Click the tab below for further details and full instructions on each protocol:
 
diff --git a/serverless/messaging/reference-content/sns-overview.mdx b/serverless/messaging/reference-content/sns-overview.mdx
@@ -21,7 +21,7 @@ Scaleway Topics and Events is a managed messaging service that facilitates the s
 
 SNS is a managed messaging service developed by AWS and leveraged by Scaleway Topics and Events.
 
-SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/serverless/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/serverless/messaging/concepts#topicexchange), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Topcs and Events makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway.
+SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/serverless/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/serverless/messaging/concepts#topicexchange), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Topics and Events makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway.
 
 <Message type="note">
   Some SNS features are not yet available with Scaleway Topics and Events. Supported subscribers are currently limited to:
diff --git a/tutorials/create-serverless-scraping/index.mdx b/tutorials/create-serverless-scraping/index.mdx
@@ -16,7 +16,7 @@ dates:
 ---
 
 In this tutorial, we show how to set up a simple application that reads [Hacker News](https://news.ycombinator.com) and processes the articles it finds there asynchronously. To do so, we  use Scaleway serverless products and deploy two functions:
- - A producer function, activated by a recurrent cron trigger, that scrapes HackerNews for articles published in the last 15 minutes and pushes the title and URL of the articles to an queue created with Scaleway Queues.
+ - A producer function, activated by a recurrent cron trigger, that scrapes HackerNews for articles published in the last 15 minutes and pushes the title and URL of the articles to a queue created with Scaleway Queues.
  - A consumer function, triggered by each new message on the queue, that consumes messages published to the queue, scrapes some data from the linked article, and then writes the data into a Scaleway Managed Database.
 
 <Lightbox src="scaleway-scraping-architecture.webp" alt="" />
diff --git a/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx b/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx
@@ -25,7 +25,7 @@ In the [previous tutorial](/tutorials/transform-bucket-images-triggers-functions
 - A Scaleway [Project](/identity-and-access-management/organizations-and-projects/quickstart/#project) dedicated to this tutorial
 - A source [bucket](/storage/object/how-to/create-a-bucket/) containing images
 - An empty destination bucket
-- An [Scaleway queue](/serverless/messaging/how-to/create-manage-queues) with credentials
+- A [Scaleway queue](/serverless/messaging/how-to/create-manage-queues) with credentials
 
 You will now learn how to deploy Serverless Functions and connect them using triggers.
 
