Apply suggestions from code review

RoRoJ · jcirinosclwy · nerda-codes · web-flow · commit 437a0d01ce06 · 2025-06-02T10:43:05.000+02:00
Co-authored-by: Jessica &lt;113192637+jcirinosclwy@users.noreply.github.com&gt;
Co-authored-by: Néda &lt;87707325+nerda-codes@users.noreply.github.com&gt;
diff --git a/pages/nats/faq.mdx b/pages/nats/faq.mdx
@@ -32,4 +32,4 @@ For full pricing details, see our [dedicated pricing page](https://www.scaleway.
 
 ## Can I access the NATS monitoring endpoint in order to deploy autoscaling tools?
 
-The monitoring endpoint is not available on Scaleway NATS. Although you can access your account monitoring information through [Scaleway Cockpit](/cockpit/), this may not be usable by third party autoscaler tools. As a workaround, you may consider coding a solution whereby your worker monitors consumption information via the metadata on each received message, and providing this information to your scaling logic.
+The monitoring endpoint is not available on Scaleway NATS. Although you can access your account monitoring information through [Scaleway Cockpit](/cockpit/), this may not be usable by third-party autoscaling tools. As a workaround, you may consider coding a solution whereby your worker monitors consumption information via the metadata on each received message and provides this information to your scaling logic.
diff --git a/pages/nats/troubleshooting/cant-delete-namespace.mdx b/pages/nats/troubleshooting/cant-delete-namespace.mdx
@@ -27,4 +27,4 @@ Try the following steps:
 
 1. In the Scaleway console, check that you have no remaining resources in either of the [NATS](https://console.scaleway.com/nats/), [Queues](https://console.scaleway.com/queues/), or [Topics and Events](https://console.scaleway.com/topics-events/) sections. **Make sure to check for resources in all regions by using the regional drop-down menu.**
 
-2. If you have delete all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.
+2. If you have deleted all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.
diff --git a/pages/nats/troubleshooting/nats-message-counting.mdx b/pages/nats/troubleshooting/nats-message-counting.mdx
@@ -1,10 +1,10 @@
 ---
 meta:
-  title: NATS queue is reporting  more messages than expected to Scaleway Cockpit
+  title: NATS queue is reporting more messages than expected to Scaleway Cockpit
   description: Understand apparent NATS queue discrepancies in Scaleway Cockpit with our troubleshooting guide.
 content:
-  h1: NATS queue is reporting  more messages than expected to Scaleway Cockpit
-  paragraph:  Understand apparent NATS queue discrepancies in Scaleway Cockpit with our troubleshooting guide.
+  h1: NATS queue is reporting more messages than expected to Scaleway Cockpit
+  paragraph: Understand apparent NATS queue discrepancies in Scaleway Cockpit with our troubleshooting guide.
 tags: nats cockpit messages queues
 dates:
   validation: 2025-05-28
diff --git a/pages/queues/troubleshooting/approximate-messages-unexpected.mdx b/pages/queues/troubleshooting/approximate-messages-unexpected.mdx
@@ -1,10 +1,10 @@
 ---
 meta:
   title: Unexpected value for Approximate Number Of Messages Not Visible
-  description: Understand why you may observe unexpected behavior from the  Approximate Number Of Messages Not Visible attribute when used with the Change Message Visibility feature
+  description: Understand why you may observe unexpected behavior from the Approximate Number Of Messages Not Visible attribute when used with the Change Message Visibility feature
 content:
   h1: Unexpected value for Approximate Number Of Messages Not Visible
-  paragraph:  Understand why you may observe unexpected behavior from the  Approximate Number Of Messages Not Visible attribute when used with the Change Message Visibility feature
+  paragraph: Understand why you may observe unexpected behavior from the  Approximate Number Of Messages Not Visible attribute when used with the Change Message Visibility feature
 tags: queues parameter visibility
 dates:
   validation: 2025-05-28
diff --git a/pages/queues/troubleshooting/cant-delete-namespace.mdx b/pages/queues/troubleshooting/cant-delete-namespace.mdx
@@ -27,4 +27,4 @@ Try the following steps:
 
 1. In the Scaleway console, check that you have no remaining resources in either of the [NATS](https://console.scaleway.com/nats/), [Queues](https://console.scaleway.com/queues/), or [Topics and Events](https://console.scaleway.com/topics-events/) sections. **Make sure to check for resources in all regions by using the regional drop-down menu.**
 
-2. If you have delete all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.
+2. If you have deleted all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.
diff --git a/pages/topics-and-events/troubleshooting/cant-confirm-subscription.mdx b/pages/topics-and-events/troubleshooting/cant-confirm-subscription.mdx
@@ -15,7 +15,7 @@ categories:
 
 ## I'm having trouble confirming a subscription to a topic
 
-When you create An HTTP or HTTPS subscription to a topic, this subscription will have a `Pending` status until you **confirm** it. This is essential to start receiving messages.
+When you create an HTTP or HTTPS subscription to a topic, this subscription will have a `Pending` status until you **confirm** it. This is essential to start receiving messages.
 
 ## Problem: You don't know how to confirm the subscription
 
diff --git a/pages/topics-and-events/troubleshooting/cant-delete-namespace.mdx b/pages/topics-and-events/troubleshooting/cant-delete-namespace.mdx
@@ -27,4 +27,4 @@ Try the following steps:
 
 1. In the Scaleway console, check that you have no remaining resources in either of the [NATS](https://console.scaleway.com/nats/), [Queues](https://console.scaleway.com/queues/), or [Topics and Events](https://console.scaleway.com/topics-events/) sections. **Make sure to check for resources in all regions by using the regional drop-down menu.**
 
-2. If you have delete all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.
+2. If you have deleted all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.

Original file line number	Diff line number	Diff line change
`@@ -32,4 +32,4 @@ For full pricing details, see our [dedicated pricing page](https://www.scaleway.`
`32`	`32`
`33`	`33`	`## Can I access the NATS monitoring endpoint in order to deploy autoscaling tools?`
`34`	`34`
`35`		`-The monitoring endpoint is not available on Scaleway NATS. Although you can access your account monitoring information through [Scaleway Cockpit](/cockpit/), this may not be usable by third party autoscaler tools. As a workaround, you may consider coding a solution whereby your worker monitors consumption information via the metadata on each received message, and providing this information to your scaling logic.`
	`35`	`+The monitoring endpoint is not available on Scaleway NATS. Although you can access your account monitoring information through [Scaleway Cockpit](/cockpit/), this may not be usable by third-party autoscaling tools. As a workaround, you may consider coding a solution whereby your worker monitors consumption information via the metadata on each received message and provides this information to your scaling logic.`
Original file line number	Diff line number	Diff line change
`@@ -27,4 +27,4 @@ Try the following steps:`
`27`	`27`
`28`	`28`	`1. In the Scaleway console, check that you have no remaining resources in either of the [NATS](https://console.scaleway.com/nats/), [Queues](https://console.scaleway.com/queues/), or [Topics and Events](https://console.scaleway.com/topics-events/) sections. Make sure to check for resources in all regions by using the regional drop-down menu.`
`29`	`29`
`30`		`-2. If you have delete all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.`
	`30`	`+2. If you have deleted all resources for these three products and the problem persists, [open a support ticket](https://console.scaleway.com/support/tickets/create) to request manual deletion of the phantom namespace.`