Merge pull request #260401 from paulth1/three-mqtt-articles

[AQ] edit pass: Three mqtt articles

Author: ShawnJackson

articles/event-grid/mqtt-publish-and-subscribe-cli.md

@@ -1,6 +1,6 @@
 ---
-title: 'Quickstart: Publish and subscribe on an MQTT topic using CLI'
-description: 'Quickstart guide to use Azure Event Grid’s MQTT broker feature and Azure CLI to publish and subscribe MQTT messages on a topic'
+title: 'Quickstart: Publish and subscribe on an MQTT topic by using the CLI'
+description: Quickstart guide to use the Azure Event Grid MQTT broker feature and the Azure CLI to publish and subscribe to MQTT messages on a topic.
 ms.topic: quickstart
 ms.custom:
   - build-2023
@@ -12,113 +12,112 @@ ms.author: geguirgu
 ms.subservice: mqtt
 ---
 
-# Quickstart: Publish and subscribe to MQTT messages on Event Grid Namespace with Azure CLI
+# Quickstart: Publish and subscribe to MQTT messages on an Event Grid namespace with the Azure CLI
 
-Azure Event Grid’s MQTT broker feature supports messaging using the MQTT protocol.  Clients (both devices and cloud applications) can publish and subscribe MQTT messages over flexible hierarchical topics for scenarios such as high scale broadcast, and command & control.
+The Azure Event Grid MQTT broker feature supports messaging by using the MQTT protocol. Clients (both devices and cloud applications) can publish and subscribe to MQTT messages over flexible hierarchical topics for scenarios such as high-scale broadcast and command and control.
 
+In this article, you use the Azure CLI to:
 
-In this article, you use the Azure CLI to do the following tasks:
-1. Create an Event Grid namespace and enable MQTT broker
-2. Create subresources such as clients, client groups, and topic spaces
-3. Grant clients access to publish and subscribe to topic spaces
-4. Publish and receive MQTT messages
+- Create an Event Grid namespace and enable the MQTT broker.
+- Create subresources such as clients, client groups, and topic spaces.
+- Grant clients access to publish and subscribe to topic spaces.
+- Publish and receive MQTT messages.
+
+If you don't have an [Azure subscription](/azure/guides/developer/azure-developer-guide#understanding-accounts-subscriptions-and-billing), create an [Azure free account](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) before you begin.
 
 ## Prerequisites
-- If you don't have an [Azure subscription](/azure/guides/developer/azure-developer-guide#understanding-accounts-subscriptions-and-billing), create an [Azure free account](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) before you begin.
-- If you're new to Azure Event Grid, read through [Event Grid overview](/azure/event-grid/overview) before starting this tutorial.
-- Register the Event Grid resource provider as per [Register the Event Grid resource provider](/azure/event-grid/custom-event-quickstart-portal#register-the-event-grid-resource-provider).
-- Make sure that port 8883 is open in your firewall. The sample in this tutorial uses MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments.
+
+- If you're new to Event Grid, read through the [Event Grid overview](/azure/event-grid/overview) before you start this tutorial.
+- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](/azure/event-grid/custom-event-quickstart-portal#register-the-event-grid-resource-provider).
+- Make sure that port 8883 is open in your firewall. The sample in this tutorial uses the MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments.
 - Use the Bash environment in [Azure Cloud Shell](/azure/cloud-shell/overview). For more information, see [Quickstart for Bash in Azure Cloud Shell](/azure/cloud-shell/quickstart).
-- If you prefer to run CLI reference commands locally, [install](/cli/azure/install-azure-cli) the Azure CLI. If you're running on Windows or macOS, consider running Azure CLI in a Docker container. For more information, see [How to run the Azure CLI in a Docker container](/cli/azure/run-azure-cli-docker).
-- If you're using a local installation, sign in to the Azure CLI by using the [az login](/cli/azure/reference-index#az-login) command. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
+- If you prefer to run CLI reference commands locally, [install](/cli/azure/install-azure-cli) the Azure CLI. If you're running on Windows or macOS, consider running the Azure CLI in a Docker container. For more information, see [Run the Azure CLI in a Docker container](/cli/azure/run-azure-cli-docker).
+- If you're using a local installation, sign in to the Azure CLI by using the [az login](/cli/azure/reference-index#az-login) command. To finish the authentication process, follow the steps that appear in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
 - When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see [Use extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
 - Run [az version](/cli/azure/reference-index?#az-version) to find the version and dependent libraries that are installed. To upgrade to the latest version, run [az upgrade](/cli/azure/reference-index?#az-upgrade).
-- This article requires version 2.53.1 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
+- This article requires version 2.53.1 or later of the Azure CLI. If you're using Azure Cloud Shell, the latest version is already installed.
 - You need an X.509 client certificate to generate the thumbprint and authenticate the client connection.
-- Review the Event Grid namespace [CLI documentation](/cli/azure/eventgrid/namespace)
+- Review the Event Grid namespace [CLI documentation](/cli/azure/eventgrid/namespace).
 
-## Generate sample client certificate and thumbprint
-If you don't already have a certificate, you can create a sample certificate using the [step CLI](https://smallstep.com/docs/step-cli/installation/). Consider installing manually for Windows. 
+## Generate a sample client certificate and thumbprint
 
-After a successful installation of Step, you should open a command prompt in your user profile folder (Win+R type %USERPROFILE%).
+If you don't already have a certificate, you can create a sample certificate by using the [step CLI](https://smallstep.com/docs/step-cli/installation/). Consider installing manually for Windows.
 
-1. To create root and intermediate certificates, run the following command.  Remember the password, which needs to be used in the next step.
+After a successful installation by using the step CLI, open a command prompt in your user profile folder (Win+R type %USERPROFILE%).
 
-```powershell
-step ca init --deployment-type standalone --name MqttAppSamplesCA --dns localhost --address 127.0.0.1:443 --provisioner MqttAppSamplesCAProvisioner
-```
+1. To create root and intermediate certificates, run the following command. Remember the password, which you need to use in the next step.
 
-2. Using the CA files generated to create certificate for the client.  Ensure to use the correct path for the cert and secrets files in the command.
+    ```powershell
+    step ca init --deployment-type standalone --name MqttAppSamplesCA --dns localhost --address 127.0.0.1:443 --provisioner MqttAppSamplesCAProvisioner
+    ```
 
-```powershell
-step certificate create client1-authnID client1-authnID.pem client1-authnID.key --ca .step/certs/intermediate_ca.crt --ca-key .step/secrets/intermediate_ca_key --no-password --insecure --not-after 2400h
-```
+1. Use the certificate authority (CA) files generated to create a certificate for the client. Make sure to use the correct path for the cert and secrets files in the command.
 
-3. To view the thumbprint, run the Step command.
+    ```powershell
+    step certificate create client1-authnID client1-authnID.pem client1-authnID.key --ca .step/certs/intermediate_ca.crt --ca-key .step/secrets/intermediate_ca_key --no-password --insecure --not-after 2400h
+    ```
 
-```powershell
-step certificate fingerprint client1-authnID.pem
-```
+1. To view the thumbprint, run the step command.
+    
+    ```powershell
+    step certificate fingerprint client1-authnID.pem
+    ```
 
-## Create a Namespace
+## Create a namespace
 
-Use the command to create a namespace.  Update the command with your Resource group, and a Namespace name.
+Use the command to create a namespace. Update the command with your resource group and a namespace name.
 
 ```azurecli-interactive
 az eventgrid namespace create -g {Resource Group} -n {Namespace Name} --topic-spaces-configuration "{state:Enabled}"
 ```
 
-> [!NOTE]
-> To keep the QuickStart simple, you'll create a namespace with minimal properties.  For detailed steps about configuring network, security, and other settings on other pages of the wizard, see [create and manage namespaces](create-view-manage-namespaces.md).
+To keep the quickstart simple, you create a namespace with minimal properties. For detailed steps about configuring network, security, and other settings on other pages of the wizard, see [Create and manage namespaces](create-view-manage-namespaces.md).
 
 ## Create clients
 
-Use the command to create the client.  Update the command with your Resource group, and a Namespace name.
+Use the command to create the client. Update the command with your resource group and a namespace name.
 
 ```azurecli-interactive
 az eventgrid namespace client create -g {Resource Group} --namespace-name {Namespace Name} -n {Client Name} --authentication-name client1-authnID --client-certificate-authentication "{validationScheme:ThumbprintMatch,allowed-thumbprints:[Client Thumbprint]}"
 ```
-
-> [!NOTE]
->  - To keep the QuickStart simple, you'll be using Thumbprint match for authentication.  For detailed steps on using X.509 CA certificate chain for client authentication, see [client authentication using certificate chain](./mqtt-certificate-chain-client-authentication.md).
-> - Also for this exercise, we use the default $all client group, which includes all the clients in the namespace.  To learn more about creating custom client groups using client attributes, see [client groups](mqtt-client-groups.md) document.
+- To keep the quickstart simple, you use thumbprint match for authentication. For steps on how to use the X.509 CA certificate chain for client authentication, see [Client authentication using certificate chain](./mqtt-certificate-chain-client-authentication.md).
+- For this exercise, we use the default `$all client` group, which includes all the clients in the namespace. To learn more about creating custom client groups by using client attributes, see [Client groups](mqtt-client-groups.md).
 
 ## Create topic spaces
 
-Use the command to create the topic space.  Update the command with your Resource group, namespace name, and a topic space name.
+Use the command to create the topic space. Update the command with your resource group, namespace name, and topic space name.
 
 ```azurecli-interactive
 az eventgrid namespace topic-space create -g {Resource Group} --namespace-name {Namespace Name} -n {Topicspace Name} --topic-templates ['contosotopics/topic1']
 ```
 
-## Create PermissionBindings
+## Create permission bindings
 
-Use the az resource command to create the first permission binding for publisher permission.  Update the command with your Resource group, namespace name, and a permission binding name.
+Use the `az resource` command to create the first permission binding for publisher permission. Update the command with your resource group, namespace name, and permission binding name.
 
 ```azurecli-interactive
 az eventgrid namespace permission-binding create -g {Resource Group} --namespace-name {Namespace Name} -n {Permission Binding Name} --client-group-name '$all' --permission publisher --topic-space-name {Topicspace Name}
 ```
 
-Use the command to create the second permission binding.  Update the command with your Resource group, namespace name and a permission binding name.  This permission binding is for subscriber.
+Use the command to create the second permission binding. Update the command with your resource group, namespace name, and permission binding name. This permission binding is for subscribers.
 
 ```azurecli-interactive
 az eventgrid namespace permission-binding create -g {Resource Group} --namespace-name {Namespace Name} -n {Name of second Permission Binding} --client-group-name '$all' --permission publisher --topic-space-name {Topicspace Name}
 ```
 
-## Publish and subscribe MQTT messages
+## Publish and subscribe to MQTT messages
 
-The following sample code is a simple .NET publisher that attempts to connect, and publish to a namespace, and subscribes to the MQTT topic.  You can use the code to modify per your requirement and run the code in Visual Studio or any of your favorite tools.  
+The following sample code is a simple .NET publisher that attempts to connect and publish to a namespace and subscribes to the MQTT topic. You can use the code to modify according to your requirement and run the code in Visual Studio or any of your favorite tools.
 
-You need to install the MQTTnet package (version 4.1.4.563) from NuGet to run this code.  
-(In Visual Studio, right click on the project name in Solution Explorer, go to Manage NuGet packages, search for MQTTnet.  Select MQTTnet package and install.)
+You need to install the MQTTnet package (version 4.1.4.563) from NuGet to run this code. (In Visual Studio, right-click the project name in Solution Explorer, go to **Manage NuGet packages**, and search for **MQTTnet**. Select **MQTTnet package** and install.)
 
 > [!NOTE]
->The following sample code is only for demonstration purposes and is not intended for production use.
+>The following sample code is for demonstration purposes only and isn't intended for production use.
 
-**Sample C# code to connect a client, publish/subscribe MQTT message on a topic**
+### Sample C# code to connect a client, publish, and subscribe to an MQTT message on a topic
 
 > [!IMPORTANT]
-> Please update the client certificate and key pem file paths depending on location of your client certificate files.  Also, ensure the client authentication name, topic information match with your configuration.
+> Update the client certificate and key pem file paths depending on the location of your client certificate files. Also, ensure that the client authentication name and topic information match with your configuration.
 
 ```csharp
 using MQTTnet.Client;
@@ -162,8 +161,9 @@ while (true)
 
 ```
 
-You can replicate and modify the same code for multiple clients to perform publish / subscribe among the clients.
+You can replicate and modify the same code for multiple clients to publish and subscribe among the clients.
 
 ## Next steps
-- [Route MQTT messages to Event Hubs](mqtt-routing-to-event-hubs-cli.md)
-- For code samples, go to [this repository.](https://github.com/Azure-Samples/MqttApplicationSamples/tree/main)
+
+- [Route MQTT messages to Event Hubs](mqtt-routing-to-event-hubs-cli.md).
+- For code samples, go to [this GitHub repository](https://github.com/Azure-Samples/MqttApplicationSamples/tree/main).