Legacy docs review "Controlling What Is Subscribed"

Author: ramonsmits

nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md

@@ -2,18 +2,17 @@
 title: Controlling What Is Subscribed
 summary: When applying the publish-subscribe pattern, there are several ways to control what messages are subscribed to
 component: Core
-reviewed: 2023-05-14
+reviewed: 2025-05-09
 ---
 
-
 ## Automatic subscriptions
 
 The default mode for managing subscriptions is *auto-subscribe*. Every time a subscriber endpoint starts, it determines which events it needs to subscribe to and automatically subscribes to them. For more information on how publish and subscribe works, refer to [Publish-Subscribe](/nservicebus/messaging/publish-subscribe).
 
-Messages matching both of the following criteria will be auto-subscribed at startup:
+Message types matching both of the following criteria will be auto-subscribed at startup:
 
- 1. Defined as an event either using `IEvent` or by the `.DefiningEventsAs` convention.
- 1. At least one [message handler and/or saga](/nservicebus/handlers/) exists for the given event.
+ 1. Defined as an event either using `IEvent` or by the `.DefiningEventsAs` convention
+ 1. At least one [message handler and/or saga](/nservicebus/handlers/) exists for the given event
 
 > [!NOTE]
 > If the selected transport [does not support publish-subscribe natively](/transports/types.md#unicast-only-transports), the publisher for that message must be specified via the [routing](/nservicebus/messaging/routing.md) API.
@@ -38,9 +37,9 @@ snippet: DoNotAutoSubscribeSagas
 In NServiceBus version 6 and above, it is possible to subscribe to messages not defined as events by [manually subscribing](/nservicebus/messaging/publish-subscribe/controlling-what-is-subscribed.md#manually-subscribing-to-a-message) to the message type.
 
 
-### When a subscriber stops or uninstalls
+## When a subscriber stops or uninstalls
 
-A subscriber will not unsubscribe when it stops; it will remain registered at the publisher to receive events. The publisher still sends events to the queue of the stopped subscriber. When the subscriber is started, it will consume the messages from its queue. The subscriber will never lose an event.
+A subscriber will not auto unsubscribe when it stops; it will remain registered at the publisher to receive events. The publisher still sends events to the queue of the stopped subscriber. When the subscriber is started, it will consume the messages from its queue. The subscriber will never lose an event.
 
 
 ## Disabling auto-subscription