fix(topics): started concepts

Author: RoRoJ

pages/topics-and-events/concepts.mdx

@@ -1,22 +1,18 @@
 ---
 meta:
-  title: NATS, Queues, and Topics and Events - Concepts
-  description: Understand the core concepts of Scaleway NATS, Queues, and Topics and Events. Explore fundamental principles for efficient message handling and service optimization.
+  title: Topics and Events - Concepts
+  description: Understand the core concepts of Scaleway Topics and Events. Explore fundamental principles for efficient message handling and service optimization.
 content:
-  h1: NATS, Queues, and Topics and Events - Concepts
-  paragraph: Understand the core concepts of Scaleway NATS, Queues, and Topics and Events. Explore fundamental principles for efficient message handling and service optimization.
+  h1: Topics and Events - Concepts
+  paragraph: Understand the core concepts of Scaleway Topics and Events. Explore fundamental principles for efficient message handling and service optimization.
 categories:
   -
-tags: messaging queuing concepts nats queues topics events 
+tags: messaging topics subscriptions events
 dates:
-  validation: 2024-10-18
-  posted: 2023-01-04
+  validation: 2025-04-10
+  posted: 2025-04-10
 ---
 
-## Content-based
-
-Content-based messaging systems are a subset of the [publish/subscribe](#publishsubscribe) model, and contrast with [topic-based](#topic-based) systems in terms of the way messages are [filtered](#filtering)/routed. In a content-based messaging system, the subscriber specifies the properties of the messages they want to receive, based on the message's attributes or content. Message delivery is therefore selective, and messages are only delivered to a subscriber if the attributes or content match the constraints they set.
-
 ## Content-based deduplication
 
 Content-based deduplication is a setting available for [FIFO](#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. Read more in our dedicated documentation on [creating queues](/messaging/how-to/create-manage-queues/).