Update duplicate-detection.md

Author: EldertGrootenboer

articles/service-bus-messaging/duplicate-detection.md

@@ -29,7 +29,7 @@ The `MessageId` can always be some GUID, but anchoring the identifier to the bus
 >- When **partitioning** is **enabled**, `MessageId+PartitionKey` is used to determine uniqueness. When sessions are enabled, partition key and session ID must be the same. 
 >- When **partitioning** is **disabled** (default), only `MessageId` is used to determine uniqueness.
 >- For information about `SessionId`, `PartitionKey`, and `MessageId`, see [Use of partition keys](service-bus-partitioning.md#use-of-partition-keys).
->- When using **partitioning**, ensure that the batch of messages being sent does not contain any partition identifying properties. Since deduplication relies on explicitly setting message IDs to determine uniqueness, it is not recommended to use deduplication and batching together on partitioned namespaces.
+>- When using **partitioning**, when sending batches of messages you should ensure that they do not contain any partition identifying properties. Since deduplication relies on explicitly setting message IDs to determine uniqueness, it is not recommended to use deduplication and batching together on partitioned namespaces.
 
 > [!NOTE]
 > Scheduled messages are included in duplicate detection. Therefore, if you send a scheduled message and then send a duplicate non-scheduled message, the non-scheduled message gets dropped. Similarly, if you send a non-scheduled message and then a duplicate scheduled message, the scheduled message is dropped.