Freshness. Links and Acrolinx.

Author: TimShererWithAquent

articles/event-grid/includes/register-provider-cli.md

@@ -11,13 +11,13 @@
 
 ## Enable the Event Grid resource provider
 
-1. If you haven't previously used Event Grid in your Azure subscription, you might need to register the Event Grid resource provider. Run the following command to register the provider:
+1. If this article is the first time that user use Event Grid in your Azure subscription, you might need to register the Event Grid resource provider. Run the following command to register the provider:
 
     ```azurecli-interactive
     az provider register --namespace Microsoft.EventGrid
     ```
     
-2. It might take a moment for the registration to finish. To check the status, run the following command:
+1. It might take a moment for the registration to finish. To check the status, run the following command:
 
     ```azurecli-interactive
     az provider show --namespace Microsoft.EventGrid --query "registrationState"

articles/event-grid/publish-events-using-namespace-topics.md

@@ -10,16 +10,24 @@ ms.date: 02/20/2024
 
 # Publish to namespace topics and consume events in Azure Event Grid
 
-This article provides a quick introduction to pull delivery using the ``curl`` bash shell command to publish, receive, and acknowledge events. Event Grid resources are created using CLI commands. This article is suitable for a quick test of the pull delivery functionality. For sample code using the data plane SDKs, see the [.NET](event-grid-dotnet-get-started-pull-delivery.md) or the Java samples. For Java, we provide the sample code in two articles: [publish events](publish-events-to-namespace-topics-java.md) and [receive events](receive-events-from-namespace-topics-java.md) quickstarts.
- For more information about the pull delivery model, see the [concepts](concepts-event-grid-namespaces.md) and [pull delivery overview](pull-delivery-overview.md) articles.
+This article provides a quick introduction to pull delivery using the `curl` bash shell command to publish, receive, and acknowledge events. Use Azure CLI commands to create Azure Event Grid resources. This article is suitable for a quick test of the pull delivery functionality.
+
+For sample code that uses the data plane SDKs, see these resources:
+
+- .NET: [Send and receive messages from an Azure Event Grid namespace topic (.NET)](event-grid-dotnet-get-started-pull-delivery.md)
+- Java: [Publish events to namespace topics using Java](publish-events-to-namespace-topics-java.md)
+- Java: [Receive events using pull delivery with Java](receive-events-from-namespace-topics-java.md)
+
+For more information about the pull delivery model, see [Azure Event Grid namespace concepts](concepts-event-grid-namespaces.md) and [Pull delivery with HTTP](pull-delivery-overview.md) articles.
 
 [!INCLUDE [quickstarts-free-trial-note.md](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
 [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
 
-- This article requires version 2.0.70 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.  
+- This article requires version 2.0.70 or later of the Azure CLI. If you use Azure Cloud Shell, the latest version is already installed.  
 
 ## Create a resource group
+
 Create an Azure resource group with the [az group create](/cli/azure/group#az-group-create) command. You use this resource group to contain all resources created in this article.
 
 The general steps to use Cloud Shell to run commands are:
@@ -33,7 +41,7 @@ The general steps to use Cloud Shell to run commands are:
     ```azurecli-interactive
     resource_group="<your-resource-group-name>"
     ```
-2. Create a resource group. Change the location as you see fit. 
+1. Create a resource group. Change the location as you see fit. 
 
     ```azurecli-interactive
     az group create --name $resource_group --location eastus
@@ -48,14 +56,14 @@ An Event Grid namespace provides a user-defined endpoint to which you post your
 - It should be between 3-50 characters.
 - It should be regionally unique.
 - Only allowed characters are a-z, A-Z, 0-9 and -
-- It shouldn't start with reserved key word prefixes like `Microsoft`, `System` or `EventGrid`.
+- It shouldn't start with reserved key word prefixes like `Microsoft`, `System`, or `EventGrid`.
     
 1. Declare a variable to hold the name for your Event Grid namespace. Specify a name for the namespace by replacing `<your-namespace-name>` with a value you like.
 
     ```azurecli-interactive
     namespace="<your-namespace-name>"
     ```
-2. Create a namespace. You might want to change the location where it's deployed. 
+1. Create a namespace. You might want to change the location where you deploy it.
 
     ```azurecli-interactive
     az eventgrid namespace create -g $resource_group -n $namespace -l eastus
@@ -70,22 +78,22 @@ Create a topic that's used to hold all events published to the namespace endpoin
     ```azurecli-interactive
     topic="<your-topic-name>"
     ```
-2. Create your namespace topic:
+1. Create your namespace topic:
 
     ```azurecli-interactive
     az eventgrid namespace topic create -g $resource_group -n $topic --namespace-name $namespace 
     ```
 
 ## Create an event subscription
 
-Create an event subscription setting its delivery mode to *queue*, which supports [pull delivery](pull-delivery-overview.md). For more information on all configuration options,see the latest Event Grid control plane [REST API](/rest/api/eventgrid).
+Create an event subscription setting its delivery mode to *queue*, which supports [pull delivery](pull-delivery-overview.md). For more information on all configuration options, see [Azure Event Grid REST API](/rest/api/eventgrid).
 
 1. Declare a variable to hold the name for an event subscription to your namespace topic. Specify a name for the event subscription by replacing `<your-event-subscription-name>` with a value you like.
 
     ```azurecli-interactive
     event_subscription="<your-event-subscription-name>"
     ```
-2. Create an event subscription to the namespace topic:
+1. Create an event subscription to the namespace topic:
 
     ```azurecli-interactive
     az eventgrid namespace topic event-subscription create -g $resource_group --topic-name $topic -n $event_subscription --namespace-name $namespace --delivery-configuration "{deliveryMode:Queue,queue:{receiveLockDurationInSeconds:300,maxDeliveryCount:4,eventTimeToLive:P1D}}"
@@ -101,7 +109,7 @@ Now, send a sample event to the namespace topic by following steps in this secti
     ```azurecli-interactive 
     namespace_resource_id=$(az eventgrid namespace show -g $resource_group -n $namespace --query "id" --output tsv)
     ```
-2. Get the first key from the namespace:
+1. Get the first key from the namespace:
 
     ```azurecli-interactive
     key=$(az eventgrid namespace list-key -g $resource_group --namespace-name $namespace --query "key1" --output tsv)
@@ -114,14 +122,15 @@ Now, send a sample event to the namespace topic by following steps in this secti
     ```azurecli-interactive
     publish_operation_uri="https://"$(az eventgrid namespace show -g $resource_group -n $namespace --query "topicsConfiguration.hostname" --output tsv)"/topics/"$topic:publish?api-version=2023-06-01-preview
     ```
-2. Create a sample [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md) compliant event:
+1. Create a sample [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md) compliant event:
 
     ```azurecli-interactive
     event=' { "specversion": "1.0", "id": "'"$RANDOM"'", "type": "com.yourcompany.order.ordercreatedV2", "source" : "/mycontext", "subject": "orders/O-234595", "time": "'`date +%Y-%m-%dT%H:%M:%SZ`'", "datacontenttype" : "application/json", "data":{ "orderId": "O-234595", "url": "https://yourcompany.com/orders/o-234595"}} '
     ```
 
-    The `data` element is the payload of your event. Any well-formed JSON can go in this field. For more information on properties (also known as context attributes) that can go in an event, see the [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md) specifications.    
-3. Use CURL to send the event to the topic. CURL is a utility that sends HTTP requests.
+    The `data` element is the payload of your event. Any well-formed JSON can go in this field. Properties that can go into an event are also known as *context attributes*. For more information, see [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md).
+
+1. Use CURL to send the event to the topic. CURL is a utility that sends HTTP requests.
 
     ```azurecli-interactive
     curl -X POST -H "Content-Type: application/cloudevents+json" -H "Authorization:SharedAccessKey $key" -d "$event" $publish_operation_uri
@@ -136,32 +145,33 @@ You receive events from Event Grid using an endpoint that refers to an event sub
     ```azurecli-interactive
     receive_operation_uri="https://"$(az eventgrid namespace show -g $resource_group -n $namespace --query "topicsConfiguration.hostname" --output tsv)"/topics/"$topic/eventsubscriptions/$event_subscription:receive?api-version=2023-06-01-preview
     ```
-2. Submit a request to consume the event:
+
+1. Submit a request to consume the event:
 
     ```azurecli-interactive
     curl -X POST -H "Content-Type: application/json" -H "Authorization:SharedAccessKey $key" $receive_operation_uri
     ```
 
 ### Acknowledge an event
 
-After you receive an event, you pass that event to your application for processing. Once you have successfully processed your event, you no longer need that event to be in your event subscription. To instruct Event Grid to delete the event, you **acknowledge** it using its lock token that you got on the receive operation's response. 
+After you receive an event, you pass that event to your application for processing. After you successfully process your event, you no longer need that event to be in your event subscription. To instruct Event Grid to delete the event, you **acknowledge** it using its lock token that you got on the receive operation's response. 
 
-1. In the previous step, you should have received a response that includes a `brokerProperties` object with a `lockToken` property. Copy the lock token value and set it on an environment variable:
+1. In the previous section, you received a response that includes a `brokerProperties` object with a `lockToken` property. Copy the lock token value and set it on an environment variable:
 
     ```azurecli-interactive
     lockToken="<paste-the-lock-token-here>"
     ```
-2. Now, build the acknowledge operation payload, which specifies the lock token for the event you want to be acknowledged.
+1. Now, build the acknowledge operation payload, which specifies the lock token for the event you want to be acknowledged.
 
     ```azurecli-interactive
     acknowledge_request_payload=' { "lockTokens": ["'$lockToken'"]} '
     ```
-3. Proceed with building the string with the acknowledge operation URI:
+1. Proceed with building the string with the acknowledge operation URI:
 
     ```azurecli-interactive
     acknowledge_operation_uri="https://"$(az eventgrid namespace show -g $resource_group -n $namespace --query "topicsConfiguration.hostname" --output tsv)"/topics/"$topic/eventsubscriptions/$event_subscription:acknowledge?api-version=2023-06-01-preview
     ```
-4. Finally, submit a request to acknowledge the event received:
+1. Finally, submit a request to acknowledge the event received:
 
     ```azurecli-interactive
     curl -X POST -H "Content-Type: application/json" -H "Authorization:SharedAccessKey $key" -d "$acknowledge_request_payload" $acknowledge_operation_uri
@@ -173,5 +183,6 @@ After you receive an event, you pass that event to your application for processi
     {"succeededLockTokens":["CiYKJDQ4NjY5MDEyLTk1OTAtNDdENS1BODdCLUYyMDczNTYxNjcyMxISChDZae43pMpE8J8ovYMSQBZS"],"failedLockTokens":[]}
     ```
     
-## Next steps
-To learn more about pull delivery model, see [Pull delivery overview](pull-delivery-overview.md).
+## Next step
+
+To learn more about pull delivery model, see [Pull delivery with HTTP](pull-delivery-overview.md).