Service Bus Freshness - 1219

Author: spelluru

articles/service-bus-messaging/service-bus-messaging-exceptions-latest.md

@@ -3,7 +3,7 @@ title: Azure Service Bus - messaging exceptions | Microsoft Docs
 description: This article provides a list of Azure Service Bus messaging exceptions and suggested actions to taken when the exception occurs.
 ms.topic: article
 ms.custom: devx-track-dotnet
-ms.date: 02/17/2023
+ms.date: 12/19/2024
 ---
 
 # Service Bus messaging exceptions (.NET)
@@ -206,12 +206,12 @@ We recommend that you follow these verification steps, depending on the type of
 
 #### Causes 
 
-- During asynchronous replication (replication lag greater than zero), the client tries to perform an operation on a service bus entity (queue, topic) or performs a management operation, but the operation cannot be completed because the replication lag between the primary and the secondary regions has exceeded the maximum allowed replication lag in seconds. 
-    - **Example**: The operation is being throttled because with it the new replication lag would reach 38323 seconds, which is greater than the maximum replication lag that was set (300 seconds). The current replication lag for the latest operation being replicated is 0 seconds. 
+- During asynchronous replication (replication lag greater than zero), the client tries to perform an operation on a service bus entity (queue, topic) or performs a management operation, but the operation can't be completed because the replication lag between the primary and the secondary regions has exceeded the maximum allowed replication lag in seconds. 
+    - **Example**: The operation is being throttled because with it the new replication lag would reach 38,323 seconds, which is greater than the maximum replication lag that was set (300 seconds). The current replication lag for the latest operation being replicated is 0 seconds. 
 - The replication queue for an entity exceeds its maximum size in bytes. The maximum size in bytes for a replication queue is an internal limit set by Service Bus. 
     - **Example**: Replication queue size 73128000 exceeded threshold 67108864.  
 - In synchronous replication, a request times out while waiting for another request to replicate. 
-    - **Example**: High volume of requests from client application for skarri-storage-exp1(westus3)/q1:MessagingJournal. Replication to other region(s) is in progress.  
+    - **Example**: High volume of requests from client application for skarri-storage-exp1(westus3)/q1:MessagingJournal. Replication to other regions is in progress.  
 
 #### Resolution 
 
@@ -221,26 +221,26 @@ We recommend that you follow these verification steps, depending on the type of
 
 #### Cause 
 
-- A timeout exception in Geo DR means that the operation did not complete within the client-provided timeout. 
+- A timeout exception in Geo DR means that the operation didn't complete within the client-provided timeout. 
     - In synchronous replication, an operation’s primary region write and replication to secondary regions are within the scope of the operation’s timeout. 
-    - In asynchronous replication, an operation’s primary region write is within the scope of the operation’s timeout, but an operation’s replication to secondary regions is not within the scope of the operation’s timeout. 
-    - **Example**: The operation did not complete within the allocated time 00:01:00 for object message. (ServiceTimeout). 
+    - In asynchronous replication, an operation’s primary region write is within the scope of the operation’s timeout, but an operation’s replication to secondary regions isn't within the scope of the operation’s timeout. 
+    - **Example**: The operation didn't complete within the allocated time 00:01:00 for object message. (ServiceTimeout). 
 
 #### Resolution
 
 - The client should retry the operation. 
-- Note that some steps of a timed-out operation may have been completed. It’s possible that a timed-out operation may have been written to the primary region and some secondary regions. If an operation has been written to the primary region, it will eventually be replicated to all secondary regions regardless of client timeout. 
+- Some steps of a timed-out operation might have been completed. It’s possible that a timed-out operation might have been written to the primary region and some secondary regions. If an operation has been written to the primary region, it will eventually be replicated to all secondary regions regardless of client timeout. 
 
 ### BadRequest 
 
 #### Cause
 
-- During a planned failover, the primary region is temporarily set as read-only in order to allow the secondary region to catch up. If the client attempts a write operation to the primary region while it is in this temporary read-only state, then the client will be receive a BadRequest exception. 
+- During a planned failover, the primary region is temporarily set as read-only in order to allow the secondary region to catch up. If the client attempts a write operation to the primary region while it is in this temporary read-only state, then the client receives a BadRequest exception. 
     - **Example**: Replication role switch in progress, primary replica:<entity-name> is ReadOnly.
 
 #### Resolution
-- The client must wait for planned failover to complete before write operations will succeed. 
-- In case planned failover takes too long, it is possible to trigger a forced failover instead. 
+- The client must wait for planned failover to complete before write operations succeed. 
+- In case planned failover takes too long, it's possible to trigger a forced failover instead. 
 
 ## Next steps
 

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

@@ -1,12 +1,10 @@
----
+`---
 title: Create partitioned Azure Service Bus queues and topics | Microsoft Docs
 description: Describes how to partition Service Bus queues and topics by using multiple message brokers.
 ms.topic: article
-ms.date: 10/12/2022
+ms.date: 12/19/2024
 ms.devlang: csharp
-ms.custom:
-  - devx-track-csharp
-  - ignite-2023
+# Customer intent: I want to learn how to create partitioned queues and topics in Azure Service Bus. 
 ---
 
 # Partitioned queues and topics
@@ -18,7 +16,7 @@ Azure Service Bus employs multiple message brokers to process messages and multi
 > - Partitioning is available at entity creation for all queues and topics in Basic or Standard SKUs. A namespace can have both partitioned and non-partitioned entities.
 > - Partitioning is available at namespace creation for the Premium messaging SKU, and all queues and topics in that namespace will be partitioned. Any previously migrated partitioned entities in Premium namespaces will continue to work as expected.
 > - When partitioning is enabled in the Basic or Standard SKUs, we will always create 16 partitions.
-> - When partitioning is enabled in the Premium SKU, the amount of partitions is specified during namespace creation.
+> - When partitioning is enabled in the Premium SKU, the number of partitions is specified during namespace creation.
  
 It isn't possible to change the partitioning option on any existing namespace, queue, or topic; you can only set the option when you create the entity.
 

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

@@ -1,10 +1,11 @@
 ---
-title: Overview of transaction processing in Azure Service Bus
+title: Transactions in Azure Service Bus
 description: This article gives you an overview of transaction processing and the send via feature in Azure Service Bus.
-ms.topic: article
-ms.date: 11/13/2023
+ms.topic: concept-article
+ms.date: 12/19/2024
 ms.devlang: csharp
 ms.custom: devx-track-csharp
+# Customer intent: I want to know how Azure Service Bus supports transactions. 
 ---
 
 # Overview of Service Bus transaction processing
@@ -89,11 +90,10 @@ To learn more about the `EnableCrossEntityTransactions` property, see the follow
 A transaction times out after 2 minutes. The transaction timer starts when the first operation in the transaction starts. 
 
 
-## Next steps
+## Related content
 
 For more information about Service Bus queues, see the following articles:
 
-* [How to use Service Bus queues](service-bus-dotnet-get-started-with-queues.md)
 * [Chaining Service Bus entities with autoforwarding](service-bus-auto-forwarding.md)
 * [Working with transactions sample](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample06_Transactions.md) (`Azure.Messaging.ServiceBus` library)
 * [Azure Queue Storage and Service Bus queues compared](service-bus-azure-and-service-bus-queues-compared-contrasted.md)