Legacy doc review

Author: helenktsai

nservicebus/messaging/conventions.md

@@ -1,16 +1,16 @@
 ---
 title: Conventions
-summary: Custom conventions for defining how certain things are detected
+summary: Custom conventions for defining how certain things are detected and to support unobtrusive mode
 component: Core
-reviewed: 2021-10-04
+reviewed: 2024-08-22
 related:
  - nservicebus/messaging/messages-events-commands
  - nservicebus/messaging/unobtrusive-mode
 ---
 
-A *convention* is a way of defining what a certain type is instead of using an interface or an attribute. Using conventions along with avoiding references to NServiceBus assemblies is referred to as *[unobtrusive mode](unobtrusive-mode.md)*. This is ideal for use in cross-platform environments.
+*Conventions* can be used to identify which types are messages, commands, and events, instead of using [marker interfaces](/nservicebus/messaging/messages-events-commands#identifying-messages-marker-interfaces). This can be done to avoid references to the NServiceBus assembly, referred to as *[unobtrusive mode](unobtrusive-mode.md)*. This is ideal for use in cross-platform environments.
 
-Currently conventions exist to identify:
+Currently *conventions* exist to identify:
 
  * [Commands](/nservicebus/messaging/messages-events-commands.md)
  * [Events](/nservicebus/messaging/messages-events-commands.md)
@@ -19,21 +19,21 @@ Currently conventions exist to identify:
  * [Data Bus](/nservicebus/messaging/databus/)
  * [TimeToBeReceived](/nservicebus/messaging/discard-old-messages.md)
 
-Messages can be defined in a *Portable Class Library* (PCL) and shared across multiple platforms even if the platform does not use NServiceBus for message processing.
+Message types can be defined in a *Portable Class Library* (PCL) and shared across multiple platforms, even if the platform does not use NServiceBus for message processing.
 
 snippet: MessageConventions
 
 > [!NOTE]
-> Note that in .NET, the namespace is optional and hence can be null. If any conventions do partial string checks, for example using `EndsWith` or `StartsWith`, then a null check should be used. So include `.Namespace != null` at the start of the convention. Otherwise a null reference exception will occur during the type scanning.
+> In .NET, the namespace is optional and can be null. If any conventions do partial string checks, for example using `EndsWith` or `StartsWith`, then a null check should be used. Include `.Namespace != null` at the start of the convention to avoid a null reference exception during type scanning.
 
 ## Using both default and custom conventions
 
-Defining conventions will replace any of the existing conventions. If both default and custom conventions are needed it is required to embed the NServiceBus marker interfaces/types into the new custom conventions.
+Defining a custom convention will overwrite the default convention. If both default and custom conventions are needed, the default conventions must be specified along with the custom conventions. 
 
 snippet: MessageConventionsDual
 
 partial: encapsulated-conventions
 
 ## Attributes
 
-If attributes are preferred over marker interfaces then this can be achieved via [NServiceBus.AttributeConventions](https://github.com/mauroservienti/NServiceBus.AttributeConventions), a [community package](/nservicebus/community/) that allows using attributes instead of interfaces.
+If attributes are preferred over marker interfaces then this can be achieved using [NServiceBus.AttributeConventions](https://github.com/mauroservienti/NServiceBus.AttributeConventions), a [community package](/nservicebus/community/) that allows using attributes instead of interfaces.