adding lightbox

Author: axisc

articles/event-hubs/geo-replication.md

@@ -16,7 +16,7 @@ The Event Hubs Geo-replication feature provides replication of both metadata (en
 > The Event Hubs Geo-replication feature is available on the Premium and Dedicated tier only.
 >
 
-This feature ensures that metadata and data of a namespace is continuously replicated from a primary region to the secondary region. The namespace can be thought of as being virtually extended to more than one region, with one region being the primary and the other being the secondary.
+This feature ensures that metadata and data of a namespace is continuously replicated from a primary region to the secondary region. The namespace can be thought of as being extended to more than one region, with one region being the primary and the other being the secondary.
 
 At any time, the secondary region can be promoted to become a primary region. Promoting a secondary repoints the namespace FQDN (fully qualified domain name) to the selected secondary region, and the previous primary region is demoted to a secondary region.
 
@@ -250,7 +250,7 @@ When implementing Geo-Replication for an Event Hubs namespace that uses private
 > [!IMPORTANT]
 > When promoting a secondary region for Event Hubs, the DNS entry also needs to be updated to point to the corresponding endpoint.
 
-:::image type="content" source="./media/geo-replication/geo-replication-private-endpoints.png" alt-text="Screenshot showing two VNETs with their own private endpoints and VMs connected to an on-premises instance and an Event Hubs namespace.":::
+:::image type="content" source="./media/geo-replication/geo-replication-private-endpoints.png" alt-text="Screenshot showing two VNETs with their own private endpoints and VMs connected to an on-premises instance and an Event Hubs namespace." lightbox="./media/geo-replication/geo-replication-private-endpoints.png":::
 
 The advantage of this approach is that failover can occur independently at the application layer or on the Event Hubs namespace:
 

articles/event-hubs/use-geo-replication.md

@@ -35,7 +35,7 @@ This tutorial shows you how to use the Geo-replication with Event Hubs. To learn
 
 2. Provide a name for the namespace, and select **Enable Geo-replication**.
 
-    :::image type="content" source="./media/use-geo-replication/premium-namespace-create.png" alt-text="Screenshot of premium namespace create UI with geo-replication UI.":::
+    :::image type="content" source="./media/use-geo-replication/premium-namespace-create.png" alt-text="Screenshot of premium namespace create UI with geo-replication UI." lightbox="./media/use-geo-replication/premium-namespace-create.png":::
 
 ---
 
@@ -79,7 +79,7 @@ In the case where your primary region goes down completely, you can still perfor
 ## Switch replication mode
 
 To switch between replication modes, or update the maximum replication lag, click on the link under **Replication consistency**, and click the checkbox to enable / disable synchronous replication, or update the value in the textbox to change the asynchronous maximum replication lag.
-:::image type="content" source="./media/use-geo-replication/update-namespace-geo-replication-configuration.png" alt-text="Screenshot showing how to update the configuration of the Geo-Replication feature.":::
+:::image type="content" source="./media/use-geo-replication/update-namespace-geo-replication-configuration.png" alt-text="Screenshot showing how to update the configuration of the Geo-Replication feature." lightbox="./media/use-geo-replication/update-namespace-geo-replication-configuration.png":::
 
 ## Remove a secondary
 To remove a Geo-replication pairing with a secondary, select **Geo-replication** on the left menu, select the secondary region, and then select **Remove**. At the prompt, enter the word **delete**, and then you can delete the secondary.