Update

Author: spelluru

articles/event-grid/mqtt-client-microsoft-entra-token-and-rbac.md

@@ -1,5 +1,5 @@
 ---
-title: Microsoft Entra JWT authentication and RBAC authorization for clients with Microsoft Entra identity
+title: Microsoft Entra `JWT` authentication and RBAC authorization for clients with Microsoft Entra identity
 description: Describes JWT authentication and RBAC roles to authorize clients with Microsoft Entra identity to publish or subscribe MQTT messages
 ms.topic: conceptual
 ms.custom:
@@ -12,14 +12,14 @@ ms.subservice: mqtt
 
 # Microsoft Entra JWT authentication and Azure RBAC authorization to publish or subscribe MQTT messages
 
-You can authenticate MQTT clients with Microsoft Entra JWT to connect to Event Grid namespace.  You can use Azure role-based access control (Azure RBAC) to enable MQTT clients, with Microsoft Entra identity, to publish or subscribe access to specific topic spaces.
+You can authenticate MQTT clients with Microsoft Entra JWT to connect to Event Grid namespace. You can use Azure role-based access control (Azure RBAC) to enable MQTT clients, with Microsoft Entra identity, to publish or subscribe access to specific topic spaces.
 
 > [!IMPORTANT]
 > - This feature is supported only when using MQTT v5 protocol version
 > - JWT authentication is supported for Managed Identities and Service principals only
 
 ## Prerequisites
-- You need an Event Grid namespace with MQTT enabled.  Learn about [creating Event Grid namespace](/azure/event-grid/create-view-manage-namespaces#create-a-namespace)
+- You need an Event Grid namespace with MQTT enabled. Learn about [creating Event Grid namespace](/azure/event-grid/create-view-manage-namespaces#create-a-namespace)
 
 <a name='authentication-using-azure-ad-jwt'></a>
 
@@ -44,21 +44,21 @@ In AUTH packet, you can provide required values in the following fields:
 Authenticate Reason Code with value 25 signifies reauthentication.
 
 > [!NOTE]
-> - Audience: “aud” claim must be set to "https://eventgrid.azure.net/".
+> - Audience: `aud` claim must be set to `https://eventgrid.azure.net/`.
 
 ## Authorization to grant access permissions
-A client using Microsoft Entra ID based JWT authentication needs to be authorized to communicate with the Event Grid namespace.  You can assign the following two built-in roles to provide either publish or subscribe permissions, to clients with Microsoft Entra identities.
+A client using Microsoft Entra ID based JWT authentication needs to be authorized to communicate with the Event Grid namespace. You can assign the following two built-in roles to provide either publish or subscribe permissions, to clients with Microsoft Entra identities.
 
 - Use **EventGrid TopicSpaces Publisher** role to provide MQTT message publisher access
 - Use **EventGrid TopicSpaces Subscriber** role to provide MQTT message subscriber access
 
-You can use these roles to provide permissions at subscription, resource group, Event Grid namespace or Event Grid topicspace scope.
+You can use these roles to provide permissions at subscription, resource group, Event Grid namespace, or Event Grid topic space scope.
 
-## Assigning the publisher role to your Microsoft Entra identity at topicspace scope
+## Assigning the publisher role to your Microsoft Entra identity at topic space scope
 
 1. In the Azure portal, navigate to your Event Grid namespace
-1. Navigate to the topicspace to which you want to authorize access.
-1. Go to the Access control (IAM) page of the topicspace
+1. Navigate to the topic space to which you want to authorize access.
+1. Go to the Access control (IAM) page of the topic space
 1. Select the **Role assignments** tab to view the role assignments at this scope.
 1. Select **+ Add** and Add role assignment.
 1. On the Role tab, select the "Event Grid TopicSpaces Publisher" role.
@@ -69,7 +69,7 @@ You can use these roles to provide permissions at subscription, resource group,
 1. Select **Review + assign** on the Review + assign tab.
 
 > [!NOTE]
-> You can follow similar steps to assign the built-in EventGrid TopicSpaces Subscriber role at topicspace scope.
+> You can follow similar steps to assign the built-in Event Grid TopicSpaces Subscriber role at topic space scope.
 
 ## Next steps
 - See [Publish and subscribe to MQTT message using Event Grid](mqtt-publish-and-subscribe-portal.md)

articles/event-grid/mqtt-overview.md

@@ -48,7 +48,7 @@ MQTT is a publish-subscribe messaging transport protocol that was designed for c
   	- **Last Will and Testament (LWT)** notifies your MQTT clients with the abrupt disconnections of other MQTT clients. You can use LWT to ensure predictable and reliable flow of communication among MQTT clients during unexpected disconnections.
 	- **Persistent sessions** ensure reliability by preserving the client's subscription information and messages when a client disconnects.
 	- **QoS 0 and 1** provide your clients with control over the efficiency and reliability of the communication.
--  MQTT broker is adding more MQTT v3.1.1 features in the future to align more with the MQTT specifications. The following items detail the current differences between features supported by MQTT broker and the MQTT v3.1.1 specification: Retain flag, Message ordering and QoS 2 aren't supported.
+-  MQTT broker is adding more MQTT v3.1.1 features in the future to align more with the MQTT specifications. The following items detail the current differences between features supported by MQTT broker and the MQTT v3.1.1 specification: Retain flag, Message ordering, and QoS 2 aren't supported.
 
 [Learn more about the MQTT broker and current limitations.](mqtt-support.md) 
 

articles/event-grid/overview.md

@@ -24,7 +24,7 @@ Azure Event Grid is used at different stages of data pipelines to achieve a dive
 
 **MQTT messaging**. IoT devices and applications can communicate with each other over MQTT. Event Grid can also be used to route MQTT messages to Azure services or custom endpoints for further data analysis, visualization, or storage. This integration with Azure services enables you to build data pipelines that start with data ingestion from your IoT devices.
 
-**Data distribution using push and pull delivery modes**. At any point in a data pipeline, HTTP applications can consume messages using push or pull APIs. The source of the data may include MQTT clients’ data, but also includes the following data sources that send their events over HTTP:
+**Data distribution using push and pull delivery modes**. At any point in a data pipeline, HTTP applications can consume messages using push or pull APIs. The source of the data might include MQTT clients’ data, but also includes the following data sources that send their events over HTTP:
 
 - Azure services
 - Your custom applications
@@ -43,7 +43,7 @@ Event Grid offers a rich mixture of features. These features include:
 - **Publish-subscribe messaging model** - Communicate efficiently using one-to-many, many-to-one, and one-to-one messaging patterns.
 - **[Built-in cloud integration](mqtt-routing.md)** - Route your MQTT messages to Azure services or custom webhooks for further processing.
 - **Flexible and fine-grained [access control model](mqtt-access-control.md)** - Group clients and topic to simplify access control management, and use the variable support in topic templates for a fine-grained access control.
-- **MQTT broker authentication methods** - [X.509 certificate authentication](mqtt-client-authentication.md) is the industry authentication standard in IoT devices, [Microsoft Entra IDauthentication](mqtt-client-microsoft-entra-token-and-rbac.md) is Azure's authentication standard for applications and [OAuth 2.0 (JSON Web Token) authentication](oauth-json-web-token-authentication.md) provides a lightweight, secure, and flexible option for MQTT clients that are not provisioned in Azure.
+- **MQTT broker authentication methods** - [X.509 certificate authentication](mqtt-client-authentication.md) is the industry authentication standard in IoT devices, [Microsoft Entra IDauthentication](mqtt-client-microsoft-entra-token-and-rbac.md) is Azure's authentication standard for applications and [OAuth 2.0 (JSON Web Token) authentication](oauth-json-web-token-authentication.md) provides a lightweight, secure, and flexible option for MQTT clients that aren't provisioned in Azure.
 - **TLS 1.2 and TLS 1.3 support** - Secure your client communication using robust encryption protocols.
 - **Multi-session support** - Connect your applications with multiple active sessions to ensure reliability and scalability.
 - **MQTT over WebSockets** - Enable connectivity for clients in firewall-restricted environments.
@@ -151,7 +151,7 @@ Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#
 One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid affords clients full control on events consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.
 
 #### Consume events over a private link
-:::image type="content" source="media/overview/consume-private-link-pull-api.png" alt-text="High-level diagram of a consumer app inside a VNET reading events from Event Grid over a private endpoint inside the VNET." lightbox="media/overview/consume-private-link-pull-api-high-res.png" border="false":::
+:::image type="content" source="media/overview/consume-private-link-pull-api.png" alt-text="High-level diagram of a consumer app inside a virtual network reading events from Event Grid over a private endpoint inside the virtual network." lightbox="media/overview/consume-private-link-pull-api-high-res.png" border="false":::
 
 You can configure **private links** to connect to Azure Event Grid to **publish and read** CloudEvents through a [private endpoint](../private-link/private-endpoint-overview.md) in your virtual network. Traffic between your virtual network and Event Grid travels the Microsoft backbone network.