Update pages/queues/troubleshooting/approximate-messages-unexpected.mdx

RoRoJ · web-flow · commit 4abf1f09ac04 · 2025-06-02T10:43:20.000+02:00
diff --git a/pages/queues/troubleshooting/approximate-messages-unexpected.mdx b/pages/queues/troubleshooting/approximate-messages-unexpected.mdx
@@ -25,4 +25,4 @@ The cause of the problem is that the underlying message broker used by Scaleway
 
 ## Solution 
 
-We can confirm that the `ChangeMessageVisibility` feature works properly, but the name of the `ApproximateNumberOfMessagesNotVisible` attribute is misleading. The attribute name contains the qualifier "Approximate" for a reason, and its value may not always reflect the actual number of messages that are not visible.
+We can confirm that the `ChangeMessageVisibility` feature works properly, and the name of the `ApproximateNumberOfMessagesNotVisible` attribute may be misleading. That said, the attribute name contains the qualifier "Approximate" for a reason, and as such its value may not always reflect the actual number of messages that are not visible.

Original file line number	Diff line number	Diff line change
`@@ -25,4 +25,4 @@ The cause of the problem is that the underlying message broker used by Scaleway`
`25`	`25`
`26`	`26`	`## Solution`
`27`	`27`
`28`		-We can confirm that the `ChangeMessageVisibility` feature works properly, but the name of the `ApproximateNumberOfMessagesNotVisible` attribute is misleading. The attribute name contains the qualifier "Approximate" for a reason, and its value may not always reflect the actual number of messages that are not visible.
	`28`	+We can confirm that the `ChangeMessageVisibility` feature works properly, and the name of the `ApproximateNumberOfMessagesNotVisible` attribute may be misleading. That said, the attribute name contains the qualifier "Approximate" for a reason, and as such its value may not always reflect the actual number of messages that are not visible.