Merge pull request #296324 from spelluru/sbusfreshness0313

Freshness review in March

Author: prmerger-automator[bot]

articles/event-hubs/event-hubs-features.md

@@ -1,8 +1,8 @@
 ---
-title: Overview of features - Azure Event Hubs | Microsoft Docs
+title: Overview of features
 description: This article provides details about features and terminology of Azure Event Hubs.
 ms.topic: overview
-ms.date: 02/15/2024
+ms.date: 03/13/2025
 ---
 
 # Features and terminology in Azure Event Hubs
@@ -52,9 +52,9 @@ If you need to archive events beyond the allowed retention period, you can have
 The reason for Event Hubs' limit on data retention based on time is to prevent large volumes of historic customer data getting trapped in a deep store that is only indexed by a timestamp and only allows for sequential access. The architectural philosophy here's that historic data needs richer indexing and more direct access than the real-time eventing interface that Event Hubs or Kafka provide. Event streaming engines aren't well suited to play the role of data lakes or long-term archives for event sourcing. 
 
 > [!NOTE]
-> Event Hubs is a real-time event stream engine and is not designed to be used instead of a database and/or as a permanent store for infinitely held event streams. 
+> Event Hubs is a real-time event stream engine and isn't designed to be used instead of a database and/or as a permanent store for infinitely held event streams. 
 > 
-> The deeper the history of an event stream gets, the more you will need auxiliary indexes to find a particular historical slice of a given stream. Inspection of event payloads and indexing aren't within the feature scope of Event Hubs (or Apache Kafka). Databases and specialized analytics stores and engines such as [Azure Data Lake Store](../data-lake-store/data-lake-store-overview.md), [Azure Data Lake Analytics](../data-lake-analytics/data-lake-analytics-overview.md) and [Azure Synapse](../synapse-analytics/overview-what-is.md) are therefore far better suited for storing historic events.
+> The deeper the history of an event stream gets, the more you'll need auxiliary indexes to find a particular historical slice of a given stream. Inspection of event payloads and indexing isn't within the feature scope of Event Hubs (or Apache Kafka). Databases and specialized analytics stores and engines such as [Azure Data Lake Store](../data-lake-store/data-lake-store-overview.md), [Azure Data Lake Analytics](../data-lake-analytics/data-lake-analytics-overview.md), and [Azure Synapse](../synapse-analytics/overview-what-is.md) are therefore far better suited for storing historic events.
 >
 > [Event Hubs Capture](event-hubs-capture-overview.md) integrates directly with Azure Blob Storage and Azure Data Lake Storage and, through that integration, also enables [flowing events directly into Azure Synapse](store-captured-data-data-warehouse.md).
 

articles/event-hubs/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: spelluru
   ms.author: spelluru
-  ms.date: 02/15/2024
+  ms.date: 03/13/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 

articles/service-bus-messaging/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: spelluru
   ms.author: spelluru
-  ms.date: 02/22/2024
+  ms.date: 03/13/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 

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

@@ -1,8 +1,8 @@
 ---
-title: Introduction to Azure Service Bus, an enterprise message broker
+title: Introduction to Azure Service Bus
 description: This article provides a high-level overview of Azure Service Bus, a fully managed enterprise integration serverless message broker. 
 ms.topic: overview
-ms.date: 02/23/2024
+ms.date: 03/13/2025
 ---
 
 # What is Azure Service Bus?
@@ -116,11 +116,11 @@ Subscribers can define which messages they want to receive from a topic. These m
 
 If an error occurs that causes the client to have any doubt about the outcome of a send operation, duplicate detection takes the doubt out of these situations by enabling the sender to resend the same message, and the queue or topic discards any duplicate copies. For more information, see [Duplicate detection](duplicate-detection.md).
 
-## Batch delete of Messages
-Azure Service Bus supports deletion of messages in batches. This is useful in scenarios when messages within queues or subscriptions have become expired , or no longer relevant, necessitating a cleanup. For more information, see [Batch delete](batch-delete.md).
+## Batch deletion of Messages
+Azure Service Bus supports deletion of messages in batches. This is useful in scenarios when messages within queues or subscriptions have become expired, or no longer relevant, necessitating a cleanup. For more information, see [Batch delete](batch-delete.md).
 
 ### Security
-Service Bus supports security protocols such as [Shared Access Signatures (SAS)](service-bus-sas.md), [Role Based Access Control (RBAC)](service-bus-role-based-access-control.md) (RBAC) and [Managed identities for Azure resources](service-bus-managed-service-identity.md).
+Service Bus supports security protocols such as [Shared Access Signatures (SAS)](service-bus-sas.md), [Role Based Access Control (RBAC)](service-bus-role-based-access-control.md) (RBAC), and [Managed identities for Azure resources](service-bus-managed-service-identity.md).
 
 Service Bus supports standard [Advanced Message Queuing Protocol (AMQP) 1.0](service-bus-amqp-overview.md) and [HTTP/REST](/rest/api/servicebus/) protocols.