update

Author: spelluru

articles/event-hubs/event-hubs-geo-dr.md

@@ -147,8 +147,8 @@ If pairing between primary and secondary namespace already exists, private endpo
 > [!NOTE]
 > While we allow read-only access to the secondary namespace, updates to the private endpoint configurations are permitted. 
 
-### Virtual networks
-When creating a disaster recovery configuration for your application and Event Hubs namespaces, you should create private endpoints for both primary and secondary Event Hubs namespaces against virtual networks hosting both primary and secondary instances of your application. 
+### Recommended configuration
+When creating a disaster recovery configuration for your application and Event Hubs namespaces, you must create private endpoints for both primary and secondary Event Hubs namespaces against virtual networks hosting both primary and secondary instances of your application. 
 
 Let's say you have two virtual networks: VNET-1, VNET-2 and these primary and secondary namespaces: EventHubs-Namespace1-Primary, EventHubs-Namespace2-Secondary. You need to do the following steps: 
 

articles/service-bus-messaging/service-bus-geo-dr.md

@@ -160,7 +160,7 @@ If pairing between primary and secondary namespace already exists, private endpo
 > [!NOTE]
 > While we allow read-only access to the secondary namespace, updates to the private endpoint configurations are permitted. 
 
-### Virtual networks
+### Recommended configuration
 When creating a disaster recovery configuration for your application and Service Bus, you should create private endpoints for both primary and secondary Service Bus namespaces against virtual networks hosting both primary and secondary instances of your application.
 
 Let's say you have two virtual networks: VNET-1, VNET-2 and these primary and second namespaces: ServiceBus-Namespace1-Primary, ServiceBus-Namespace2-Secondary. You need to do the following steps: