Merge pull request #277859 from spelluru/uuf0611

UUF Feedback

Author: prmerger-automator[bot]

articles/event-grid/create-view-manage-namespaces.md

@@ -1,6 +1,6 @@
 ---
 title: Create, view, and manage Azure Event Grid namespaces
-description: This article describes how to create, view and manage namespaces
+description: This article describes how to create, view, and manage namespaces
 author: robece
 ms.topic: how-to
 ms.custom:
@@ -12,11 +12,11 @@ ms.date: 11/15/2023
 
 # Create, view, and manage namespaces
 
-A namespace in Azure Event Grid is a logical container for one or more topics, clients, client groups, topic spaces and permission bindings. It provides a unique namespace, allowing you to have multiple resources in the same Azure region. With an Azure Event Grid namespace you can group now together related resources and manage them as a single unit in your Azure subscription.
+A namespace in Azure Event Grid is a logical container for one or more topics, clients, client groups, topic spaces, and permission bindings. It provides a unique namespace, allowing you to have multiple resources in the same Azure region. Using an Azure Event Grid namespace, you can group together related resources and manage them as a single unit in your Azure subscription.
 
 
 
-This article shows you how to use the Azure portal to create, view and manage an Azure Event Grid namespace.
+This article shows you how to use the Azure portal to create, view, and manage an Azure Event Grid namespace.
 
 ## Create a namespace
 
@@ -32,15 +32,15 @@ This article shows you how to use the Azure portal to create, view and manage an
     1. Select an existing **resource group** or create a resource group.
     1. Enter a **name** for the namespace.
     1. Select the region or **location** where you want to create the namespace. 
-    1. If the selected region supports availability zones, the **Availability zones** checkbox can be enabled or disabled. The checkbox is selected by default if the region supports availability zones. However, you can uncheck and disable availability zones if needed. The selection cannot be changed once the namespace is created.
+    1. If the selected region supports availability zones, the **Availability zones** checkbox can be enabled or disabled. The checkbox is selected by default if the region supports availability zones. However, you can uncheck and disable availability zones if needed. The selection can't be changed once the namespace is created.
     1. Use the slider or text box to specify the number of **throughput units** for the namespace. Throughput units (TUs) define the ingress and egress event rate capacity in namespaces.
     1. Select **Next: Networking** at the bottom of the page. 
 
         :::image type="content" source="media/create-view-manage-namespaces/create-namespace-basics-page.png" alt-text="Screenshot showing the Basics tab of Create namespace page.":::        
 1. Follow steps from [Configure IP firewall](configure-firewall.md) or [Configure private endpoints](mqtt-configure-private-endpoints.md) to configure IP firewall or private endpoints for the namespace, and then select **Next: Security** at the bottom of the page.
 1. On the **Security** page, create a managed identity by following instructions from [Enable managed identity for a namespace](event-grid-namespace-managed-identity.md), and then select **Next: Tags** at the bottom of the page. 
 1. On the **Tags** tab, add the tags in case you need them. Then, select **Next: Review + create** at the bottom of the page.
-6. On the **Review + create** tab, review your settings and select **Create**.
+6. On the **Review + create** tab, review your settings, and select **Create**.
 1. On the **Deployment succeeded** page, select **Go to resource** to navigate to your namespace. 
 
 ## View a namespace

articles/service-bus-messaging/batch-delete.md

@@ -7,13 +7,13 @@ ms.date: 05/20/2024
 
 # Batch delete messages in Azure Service Bus (Preview)
 
-Azure Service Bus is a fully managed enterprise integration message broker that enables you to send and receive messages between decoupled applications and services. However, sometimes you may want to delete messages from a queue or subscription without processing them, for example, if they're expired, corrupted, or irrelevant. This article shows you how to delete messages in batches in Azure Service Bus. 
+Azure Service Bus is a fully managed enterprise integration message broker that enables you to send and receive messages between decoupled applications and services. However, sometimes you might want to delete messages from a queue or subscription without processing them, for example, if they're expired, corrupted, or irrelevant. This article shows you how to delete messages in batches in Azure Service Bus. 
 
 ## Scenarios for Batch deletion of messages
 
-There are several scenarios where you may want to use the batch delete messages feature in Azure Service Bus. Some of them are:
+There are several scenarios where you might want to use the batch delete messages feature in Azure Service Bus. Some of them are:
 
-- Expired Messages: Delete messages that exceed their "time to live" (TTL) value and are in the dead-letter queue.
+- Expired Messages: Delete messages that exceed their time to live (TTL) value and are in the dead-letter queue.
 - Failed Validation or Processing: Remove messages that failed validation or processing logic and are in the dead-letter queue.
 - Irrelevant Messages: Delete messages no longer relevant for your application logic from the active queue.
 - Handling Duplicates or Incorrect Content: Remove duplicate or incorrect messages from the active queue.
@@ -25,10 +25,10 @@ By using the batch delete messages feature, you can delete multiple messages fro
 
 ## How to batch delete messages in Service Bus
 
-You can delete messages by calling [DeleteMessagesAsync](/dotnet/api/azure.messaging.servicebus.servicebusreceiver.deletemessagesasync?view=azure-dotnet-preview) on Service Bus Receiver object. On the server side, DeleteMessagesAsync requires two parameters: messageCount and beforeEnqueueTime as described below:
+You can delete messages by calling [DeleteMessagesAsync](/dotnet/api/azure.messaging.servicebus.servicebusreceiver.deletemessagesasync?view=azure-dotnet-preview) on Service Bus Receiver object. On the server side, `DeleteMessagesAsync` requires two parameters: `messageCount` and `beforeEnqueueTime`.
 
-- messageCount : The desired number of messages to delete.The service may delete fewer messages than this limit.
-- beforeEnqueueTime : An optional DateTimeOffset, in UTC, representing the cutoff time for deletion. Only messages that were enqueued before this time will be deleted. 
+- `messageCount`: The desired number of messages to delete. The service might delete fewer messages than this limit.
+- `beforeEnqueueTime`: An optional DateTimeOffset, in UTC, representing the cutoff time for deletion. Only messages that were enqueued before this time are deleted. 
 
 Additionally, you can call [PurgeMessagesAsync](/dotnet/api/azure.messaging.servicebus.servicebusreceiver.purgemessagesasync?view=azure-dotnet-preview) to purge all messages from entity. 
 

articles/service-bus-messaging/enable-auto-forward.md

@@ -68,7 +68,7 @@ az servicebus topic subscription create \
 To **update the auto forward setting for a subscription to a topic**, use the [`az servicebus topic subscription update`](/cli/azure/servicebus/topic/subscription#az-servicebus-topic-subscription-update) command with `--forward-to` set to the name of queue or topic to which you want the messages to be forwarded.
 
 ```azurecli-interactive
-az servicebus topic subscription create \
+az servicebus topic subscription update \
     --resource-group myresourcegroup \
     --namespace-name mynamespace \
     --topic-name mytopic \
@@ -281,7 +281,7 @@ Try the samples in the language of your choice to explore Azure Service Bus feat
 - [Azure Service Bus client library samples for JavaScript](/samples/azure/azure-sdk-for-js/service-bus-javascript/)
 - [Azure Service Bus client library samples for TypeScript](/samples/azure/azure-sdk-for-js/service-bus-typescript/)
 
-Find samples for the older .NET and Java client libraries below:
+Find samples for the older .NET and Java client libraries:
 - [Azure Service Bus client library samples for .NET (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.Azure.ServiceBus/)
 - [Azure Service Bus client library samples for Java (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/Java/azure-servicebus)
 

articles/service-bus-messaging/enable-dead-letter.md

@@ -73,7 +73,7 @@ az servicebus topic subscription update \
 ```
 
 > [!NOTE]
-> If you specify a queue or topic by using the `--forward-dead-lettered-messages-to` parameter, Event Grid automatically forwards dead-lettered messages to that queue or topic. Here's an example: `az servicebus queue create --resource-group mysbusrg --namespace-name mysbusns --name myqueue --enable-dead-lettering-on-message-expiration true --forward-dead-lettered-messages-to myqueue2`.
+> If you specify a queue or topic by using the `--forward-dead-lettered-messages-to` parameter, Service Bus automatically forwards dead-lettered messages to that queue or topic. Here's an example: `az servicebus queue create --resource-group mysbusrg --namespace-name mysbusns --name myqueue --enable-dead-lettering-on-message-expiration true --forward-dead-lettered-messages-to myqueue2`.
 
 ## Using Azure PowerShell
 To **create a queue with dead lettering on message expiration enabled**, use the [`New-AzServiceBusQueue`](/powershell/module/az.servicebus/new-azservicebusqueue) command with `-DeadLetteringOnMessageExpiration` set to `$True`. 
@@ -273,7 +273,7 @@ Try the samples in the language of your choice to explore Azure Service Bus feat
 - [Azure Service Bus client library samples for JavaScript](/samples/azure/azure-sdk-for-js/service-bus-javascript/)
 - [Azure Service Bus client library samples for TypeScript](/samples/azure/azure-sdk-for-js/service-bus-typescript/)
 
-Find samples for the older .NET and Java client libraries below:
+Find samples for the older .NET and Java client libraries:
 - [Azure Service Bus client library samples for .NET (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.Azure.ServiceBus/)
 - [Azure Service Bus client library samples for Java (legacy)](https://github.com/Azure/azure-service-bus/tree/master/samples/Java/azure-servicebus)
 

articles/service-bus-messaging/service-bus-premium-messaging.md

@@ -16,7 +16,7 @@ Some high-level differences are highlighted in the following table.
 
 | Criteria | Premium | Standard |
 |--- | --- | --- |
-| Throughout | High throughput |Variable throughput |
+| Throughput | High throughput |Variable throughput |
 | Performance | Predictable performance |Variable latency |
 | Pricing | Fixed pricing |Pay as you go variable pricing |
 | Scale | Ability to scale workload up and down |N/A |