Merge pull request #286563 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/dns/dns-private-resolver-overview.md

@@ -126,7 +126,7 @@ Outbound endpoints have the following limitations:
 
 - IPv6 enabled subnets aren't supported.
 - DNS private resolver doesn't support Azure ExpressRoute FastPath.
-- DNS private resolver inbound endpoint provisioning isn't compatible with [Azure Lighthouse](../lighthouse/overview.md).
+- DNS private resolver isn't compatible with [Azure Lighthouse](../lighthouse/overview.md).
     - To see if Azure Lighthouse is in use, search for **Service providers** in the Azure portal and select **Service provider offers**. 
 
 ## Next steps

articles/event-grid/communication-services-chat-events.md

@@ -14,7 +14,7 @@ Azure Communication Services emits chat events only when Azure Communication Ser
 
 ## Event types
 
-Azure Communication Services emits chat events on two different levels: **User-level** and **Thread-level**. User-level events pertain to a specific user on the chat thread and are delivered once per user. Thread-level events pertain to the entire chat thread and are delivered once per thread. For example: if there are 10 users in a thread, there will be one thread-level event and 10 user-level events, one for each user, when a message is received in a thread.
+Azure Communication Services emits chat events on two different levels: **User-level** and **Thread-level**. User-level events are specific to each user in the chat thread and are delivered once per user, excluding the event sender. Thread-level events pertain to the entire chat thread and are delivered once per thread. For instance, when a message is received in a thread with 10 users, there will be one thread-level event and 9 user-level events, one for each user, except for the sender.
 
 Azure Communication Services emits the following chat event types: