diff --git a/content/topics/messaging/delivery-shapes.svg b/content/topics/messaging/delivery-shapes.svg
deleted file mode 100644
index 78d84af..0000000
--- a/content/topics/messaging/delivery-shapes.svg
+++ /dev/null
@@ -1,57 +0,0 @@
-
-
diff --git a/content/topics/messaging/pubsub-delivery.svg b/content/topics/messaging/pubsub-delivery.svg
new file mode 100644
index 0000000..a705fca
--- /dev/null
+++ b/content/topics/messaging/pubsub-delivery.svg
@@ -0,0 +1,17 @@
+
diff --git a/content/topics/messaging/queue-delivery.svg b/content/topics/messaging/queue-delivery.svg
new file mode 100644
index 0000000..24a44d0
--- /dev/null
+++ b/content/topics/messaging/queue-delivery.svg
@@ -0,0 +1,17 @@
+
diff --git a/content/topics/messaging/stream-delivery.svg b/content/topics/messaging/stream-delivery.svg
new file mode 100644
index 0000000..4bc4642
--- /dev/null
+++ b/content/topics/messaging/stream-delivery.svg
@@ -0,0 +1,14 @@
+
diff --git a/content/topics/messaging/topic.md b/content/topics/messaging/topic.md
index c8aee5f..a3e3aae 100644
--- a/content/topics/messaging/topic.md
+++ b/content/topics/messaging/topic.md
@@ -16,39 +16,29 @@ childTopicIds:
relatedTopicIds: []
---
-## Choose from the requirement
+
-### Work queue
+- **Use:** distribute thumbnail jobs among workers.
+- **Plan for:** retries can repeat work; make effects duplicate-safe.
-Distribute thumbnail jobs among workers.
+
-**Tradeoff:** Retries can repeat work; effects must tolerate duplicates.
+- **Use:** let independent applications each react to the same event.
+- **Remember:** durable subscriptions or subscriber queues can retain messages while consumers are offline.
-### Publish/subscribe
+
-Let billing, email, and analytics each react to an order event.
+- **Use:** retained history, replay, or ordered event processing.
+- **Plan for:** retention limits replay; ordering is commonly per partition, not global. Multiple consumers are optional.
-**Tradeoff:** Each subscription needs its own backlog and failure policy.
-
-### Event stream/log
-
-Retain events for replay or process an ordered sequence.
-
-**Tradeoff:** Manage retention and consumer positions; ordering has a defined boundary.
-
-## How delivery differs
-
-
-
-## Before choosing
-
-- **Pub/sub can be durable:** offline consumers do not automatically lose messages. Retention and subscription settings matter.
-- **Streams do not require multiple consumers:** retention, replay, and ordered event processing are stronger selection reasons. Ordering is commonly per partition, not global.
-- **Products overlap:** queues, pub/sub, and logs are models, not mutually exclusive product categories.
+> **Database jobs can also fit.** A durable job table avoids another service, but workers need safe claiming, retries, and recovery; polling adds database load.
-A **producer** sends messages; a **consumer** processes them; a **broker** is infrastructure that routes or stores them. A **topic** names a publication destination; its delivery semantics depend on the product.
+## Terms and boundaries
-> **Database jobs can also fit.** A durable job table avoids another service, but workers need safe claiming, retries, and recovery; polling adds database load.
+- **Producer / consumer:** sends / processes messages.
+- **Broker:** infrastructure that routes or stores messages.
+- **Topic:** named publication destination; delivery semantics depend on the product.
+- **Models overlap:** one product can support queues, pub/sub, and logs.
## Sources