Update articles/operational-excellence/relocation-static-web-apps.md

Co-authored-by: Craig Shoemaker <[email protected]>

Author: anaharris-ms

articles/operational-excellence/relocation-static-web-apps.md

@@ -54,9 +54,9 @@ Review the following prerequisites before you prepare for the relocation.
 ## Downtime
 
 The relocation of an Azure Static Web site introduces downtime to your application. The downtime is affected by which high availability pattern you have implemented for your Azure Static Web site. General patterns are:
-- Cold Standby - the workload data is backed up regularly based on the requirements of the workload. In case of a disaster, the workload is redeployed in a new Azure region and the data is restored.
-- Warm Standby - the workload is deployed in the BCDR region and the data is replicated asynchronously or synchronously. In the event of a disaster, the deployment in the DR region is scaled up and out.
-- [Multi-region](https://learn.microsoft.com/en-us/azure/architecture/web-apps/app-service/architectures/multi-region)  - the workload is deployed in both regions and the data is replicated synchronously. Both regions have a writable copy of the data. The implementation can be Active/Passive or Active/Active.
+- **Cold standby**: Workload data is backed up regularly based on its requirements. In case of a disaster, the workload is redeployed in a new Azure region and data is restored.
+- **Warm standby**: The workload is deployed in the business continuity and disaster recovery (BCDR) region, and data is replicated asynchronously or synchronously. In the event of a disaster, the deployment in the disaster recovery (DR) region is scaled up and out.
+- **Multi-region**: The workload is [deployed in both regions](/azure/architecture/web-apps/app-service/architectures/multi-region) and data is replicated synchronously. Both regions have a writable copy of the data. The implementation can be active/passive or active/active.
 
 ## Prepare