Merge pull request #286888 from axisc/patch-1

Update geo-replication.md

Author: prmerger-automator[bot]

articles/event-hubs/geo-replication.md

@@ -21,11 +21,11 @@ These features shouldn't be confused with Availability Zones. Both geographic re
 > - This feature is currently in public preview, and as such shouldn't be used in production scenarios.
 > - The following regions are currently supported in the public preview.
 >
-> | US               | Europe        |
-> |------------------|---------------|
-> | Central US EUAP  | Italy North   |
-> |                  | Spain Central |
-> |                  | Norway East   |
+> | US               | Europe        | APAC          |
+> |------------------|---------------|---------------| 
+> | Central US EUAP  | Italy North   | Australia Central |
+> | Canada Central   | Spain Central | Australia East |
+> | Canada East      | Norway East   ||
 
 
 ## Metadata disaster recovery vs. Geo-replication of metadata and data
@@ -152,4 +152,4 @@ Clients that use the Event Hubs SDK need to upgrade to the April 2024 version of
 Event Hubs dedicated clusters are priced independently of geo-replication. Use of geo-replication with Event Hubs dedicated requires you to have at least two dedicated clusters in separate regions. The dedicated clusters used as secondary instances for geo-replication can be used for other workloads. There's a charge for geo-replication based on the published bandwidth * the number of secondary regions. The geo-replication charge is waived in early public preview. 
 
 ## Related content
-To learn how to use the Geo-replication feature, see [Use Geo-replication](use-geo-replication.md).
+To learn how to use the Geo-replication feature, see [Use Geo-replication](use-geo-replication.md).