Merge pull request #309005 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/expressroute/metro.md

@@ -52,7 +52,7 @@ The following diagram allows for a comparison between the standard ExpressRoute
 | Madrid Metro | Equinix MD2<br>Digital Realty MAD1 | 1 | Spain Central | &check; | Colt<br>Equinix<br>Megaport<sup>1</sup> |
 | Milan Metro | Irideos Milan<br>Data4Italy Milan | 1 | Italy North | &check; | Equinix<br>Megaport<sup>1</sup> |
 | Singapore Metro | Global Switch Tai Seng<br>Equinix SG1 | 2 | Southeast Asia | &check; | Colt<br>Equinix<br>Megaport |
-| Taipei Metro | Chief Telecom<br>Chunghwa Telecom Co. Ltd | 2 | Taiwan North | &check; | |
+| Taipei Metro | Chief Telecom<br>Chunghwa Telecom Co. Ltd | 2 | Taiwan North | &check; | Chunghwa Telecom |
 | Zurich Metro |  Digital Realty ZUR2<br>Equinix ZH5 | 1 | Switzerland North | &check; | Colt<br>Digital Realty |
 | Washington DC Metro | Equinix DC6<br>CoreSite VA3 | 1 | East US<br/>East US 2 | &check; |  Equinix<sup>1</sup><br>Megaport<sup>1</sup> |
 

articles/firewall/secured-hub-customer-public-ip.md

@@ -15,9 +15,7 @@ ms.author: duau
 
 Azure Firewall in Virtual WAN secured hubs now supports the use of customer-provided public IP addresses. This capability enables organizations to bring their own public IP addresses when deploying Azure Firewall in a secured Virtual WAN hub, providing greater flexibility and control over network infrastructure.
 
-With this feature, instead of relying on Azure-managed public IP addresses, you can specify your own public IP addresses that are already allocated in your Azure subscription. This is valuable for organizations that need to maintain consistent IP addresses for compliance, security policies, or integration with third-party systems.
-
-This capability is available only for new deployments of secured hub Azure Firewalls. For existing secured Virtual WAN hubs with Azure Firewall already deployed, you must delete the hub firewall and redeploy it during scheduled maintenance hours to take advantage of customer-provided public IP addresses.
+With this feature, instead of relying on Azure-managed public IP addresses, you can specify your own public IP addresses that are already allocated in your Azure subscription. This is particularly valuable for organizations that require consistent IP addresses for compliance, security policies, or integration with third-party systems.
 
 You can configure this feature using either the Azure portal or Azure PowerShell.
 
@@ -57,7 +55,7 @@ Before you can use customer-provided public IP addresses with secured hub Azure
 - **IP prefix (recommended)**: For better management, allocate your public IP addresses from a public IP address prefix pool.ided public IP address support in secured hubs
 description: Learn how to use customer-provided public IP addresses with Azure Firewall in secured Virtual WAN hubs for enhanced control and DDoS protection.
 
-The capability is available to new as well as existing deployments of secured hub Firewalls. 
+The capability is available for both new and existing deployments of secured hub Firewalls. 
 
 ## Configure a new Secure Hub Azure Firewall with customer tenant public IP 
 

articles/operator-service-manager/helm-requirements.md

@@ -229,7 +229,7 @@ To ensure consistent and predictable deployments, we recommend the following for
   * Using latest can cause unexpected behavior because the actual image behind latest can change without notice.
   * In a cluster registry setup, if the tag value changes but the tag name stays the same, the cluster registry will not re-download the updated image.
   * This can lead to running outdated or inconsistent images.
-* Instead, alway Use immutable tags like `:1.4.2` 
+* Instead, always use immutable tags like `:1.4.2` 
 *	Ensure every build produces a unique tag, do not overwrite existing tags.
 
 These practices help prevent deployment issues and improve traceability, rollback safety, and security compliance.