Merge pull request #4392 from gaurikasar/high-availability

made changes for HA docs

Author: v-regandowner

articles/postgresql/high-availability/how-to-configure-high-availability.md

@@ -35,7 +35,7 @@ The **Zonal Resiliency** option controls whether your server is protected across
 - Enabled – When you select this option, Azure tries to create the standby server in a different availability zone than the primary. This option gives you the best protection against zone-level failures.
 - Disabled – High availability isn't configured.
 
-If you enable zonal resiliency but your region lacks capacity for a zone-redundant setup, an extra checkbox appears under the Enabled option. Selecting this checkbox allows the standby server to be created in the same zone as the primary server. When zonal capacity becomes available, Azure notifies you. At that point, you can use either PITR or read replicas to migrate workloads to a zone-redundant HA configuration for maximum resiliency. For more information, see the [Limitations and Considerations](#limitations-and-considerations) section.
+If you enable zonal resiliency but your region lacks capacity for a zone-redundant setup, an extra checkbox appears under the Enabled option. Selecting this checkbox allows the standby server to be created in the same zone as the primary server. When zonal capacity becomes available, Azure automatically migrates your workloads from Same-Zone HA to Zone-redundant HA.
 
 1. If you didn't enable Zonal Resiliency, select the **Enabled** option.
 
@@ -125,7 +125,7 @@ The **--zonal-resiliency** parameter helps you create a standby server in a diff
 - Enabled – When you select this option, Azure tries to create the standby server in a different availability zone than the primary. This option gives you the best protection against zone-level failures.
 - Disabled – High availability isn't configured.
 
-To ensure your server is configured for high availability, enable the `--allow-same-zone` parameter. In regions without multiple availability zones, this option allows the standby server to be created in the same zone as the primary. When zonal capacity becomes available, Azure notifies you. At that point, you can use PITR or read replicas to migrate to a zone‑redundant HA configuration for maximum resiliency. For more information, refer to the [Limitations and Considerations](#limitations-and-considerations) section.
+To ensure your server is configured for high availability, enable the `--allow-same-zone` parameter. In regions without multiple availability zones, this option allows the standby server to be created in the same zone as the primary. When zonal capacity becomes available, Azure automatically migrates your workloads from same-zone HA to zone-redundant HA.
 
 ```azurecli-interactive
 az postgres flexible-server update \
@@ -198,7 +198,7 @@ You can configure high availability when you first create your Azure Database fo
 
    :::image type="content" source="./media/how-to-configure-high-availability/high-availability-enable-zonal-resiliency.png" alt-text="Screenshot that shows enabling HA with zone-redundant option." lightbox="./media/how-to-configure-high-availability/high-availability-enable-zonal-resiliency.png":::
 
-   - If zonal capacity isn't available, select the **Allow standby in same zone if zonal resiliency fails** checkbox as a fallback. If you don't select this option, you can't proceed to the next step in the create workflow. This check ensures high availability remains enabled. When zonal capacity becomes available, Azure notifies you. You can then use PITR or read replicas to migrate workloads to a zone-redundant HA configuration for maximum resiliency.
+   - If zonal capacity isn't available, select the **Allow standby in same zone if zonal resiliency fails** checkbox as a fallback. If you don't select this option, you can't proceed to the next step in the create workflow. This check ensures high availability remains enabled. When zonal capacity becomes available, Azure automatically migrates your workloads from Same-Zone HA to Zone-redundant HA.
 
      :::image type="content" source="./media/how-to-configure-high-availability/high-availability-enable-same-zone-error.png" alt-text="Screenshot that shows validation error message for same-zone HA option." lightbox="./media/how-to-configure-high-availability/high-availability-enable-same-zone-error.png":::
 
@@ -290,7 +290,7 @@ This region is single availability zone. Zone redundant high availability is not
 Use the **--zonal-resiliency** parameter when creating an Azure Database for PostgreSQL flexible server instance. This ensures the standby server is provisioned in a different availability zone than the primary, improving protection against zone‑level failures.
 
 If the region doesn't currently support multiple availability zones, add the **--allow-same-zone** parameter. This parameter acts as a fallback: if Azure can't create the standby in another zone, it creates the standby in the same zone as the primary so that high availability is still enabled in your chosen region.
-When zonal capacity later becomes available, Azure notifies you. You can then use PITR or a read replica to move your workloads to a zone‑redundant HA configuration for improved resiliency.
+When zonal capacity later becomes available, Azure automatically migrates your workloads from same-zone HA to zone-redundant HA.
 
 The `--zonal-resiliency` parameter accepts these values: