Metadata and links updated, minor Acrolinx fixes to improve score

Author: DENKEN02MSFT

articles/digital-twins/concepts-high-availability-disaster-recovery.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Digital Twins
 description: Learn about high availability and disaster recovery features for Azure Digital Twins.
 author: baanders
 ms.author: baanders
-ms.date: 6/20/2023
+ms.date: 4/17/2025
 ms.topic: conceptual
 ms.service: azure-digital-twins
 ---
@@ -17,26 +17,26 @@ Considering business continuity and disaster recovery can help you create resili
 
 Azure Digital Twins supports these features:
 * *Intra-region HA* – Built-in redundancy to deliver on uptime of the service
-* *Cross region DR* – Fail over to a geo-paired Azure region if there's an unexpected data center failure
+* *Cross region DR* – Fail over to an Azure paired region if there's an unexpected data center failure
 
 ## Intra-region HA
 
-Azure Digital Twins provides *intra-region HA* by implementing redundancies within the service. This functionality is reflected in the [service SLA](https://azure.microsoft.com/support/legal/sla/digital-twins) for uptime. No additional work is required by the developers of an Azure Digital Twins solution to take advantage of these HA features. 
+Azure Digital Twins provides *intra-region HA* by implementing redundancies within the service. This functionality is reflected in the [service SLA](https://azure.microsoft.com/support/legal/sla/digital-twins) for uptime. The developers of an Azure Digital Twins solution can take advantage of these HA features without any extra work.
 
 Although Azure Digital Twins offers a high uptime guarantee, transient failures are possible on any distributed computing platform. Appropriate retry policies should be built into the components interacting with your cloud application to handle these transient failures.
 
 ## Cross region DR
 
-It's possible, although unlikely, for a data center to experience extended outages because of power failures or other events in the region. During a rare failure event like this, the intra region HA capability described above may not be sufficient. Azure Digital Twins addresses this scenario with Microsoft-initiated failover.
+It's possible, although unlikely, for a data center to experience extended outages because of power failures or other events in the region. During a rare failure event like this, the intra-region HA capability previously described might not be sufficient. Azure Digital Twins addresses this scenario with Microsoft-initiated failover.
 
-*Microsoft-initiated failover* is exercised in rare situations to fail over all the Azure Digital Twins instances from an affected region to the corresponding [geo-paired region](../reliability/cross-region-replication-azure.md). This process is a default option and will happen without any intervention from you, meaning that the customer data stored in Azure Digital Twins is replicated by default to the paired region. Microsoft reserves the right to make a determination of when this option will be exercised, and this mechanism doesn't involve user consent before the user's instance is failed over.
+*Microsoft-initiated failover* is exercised in rare situations to fail over all the Azure Digital Twins instances from an affected region to the corresponding [paired region](../reliability/cross-region-replication-azure.md). This process is a default option and happens without any intervention from you, meaning that the customer data stored in Azure Digital Twins is replicated by default to the paired region. Microsoft reserves the right to make a determination of when this option is exercised, and this mechanism doesn't involve user consent before the user's instance is failed over.
 
-If it's important for you to keep all data within certain geographical areas, check the location of the [geo-paired region](../reliability/cross-region-replication-azure.md#azure-paired-regions) for the region where you're creating your instance, to ensure that it meets your data residency requirements. For regions with built-in data residency requirements, customer data is always kept within the same region.
+If it's important for you to keep all data within certain geographical areas, check the location of the [paired region](../reliability/cross-region-replication-azure.md#azure-paired-regions) for the region where you're creating your instance, to ensure that it meets your data residency requirements. For regions with built-in data residency requirements, customer data is always kept within the same region.
 
 >[!NOTE]
-> Some Azure services provide an additional option called *customer-initiated failover*, which enables customers to initiate a failover just for their instance, such as to run a DR drill. This mechanism is currently not supported by Azure Digital Twins. 
+> Some Azure services provide another option called *customer-initiated failover*, which enables customers to initiate a failover just for their instance, such as to run a DR drill. Azure Digital Twins doesn't currently support this mechanism.
 >
-> Other Azure services provide an option for users to configure a different region for failover, as a way to meet data residency requirements. This capability is also not supported by Azure Digital Twins. 
+> Other Azure services provide an option for users to configure a different region for failover, as a way to meet data residency requirements. Azure Digital Twins doesn't support this capability. 
 
 ## Monitor service health
 
@@ -58,10 +58,10 @@ To view Service Health events...
 
     :::image type="content" source="media/concepts-high-availability-disaster-recovery/issue-updates.png" alt-text="Screenshot of the Azure portal showing the 'Health History' page with the 'Issue updates' tab highlighted. The tab displays the status of entries." lightbox="media/concepts-high-availability-disaster-recovery/issue-updates.png":::
 
-The information displayed in this tool isn't specific to one Azure Digital instance. After using Service Health to understand what's going with the Azure Digital Twins service in a certain region or subscription, you can take monitoring a step further by using [Azure Resource Health](how-to-monitor-resource-health.md) to drill down into specific instances and see whether they're affected.
+The information displayed in this tool isn't specific to one Azure Digital Twins instance. After using Service Health to understand what's going with the Azure Digital Twins service in a certain region or subscription, you can take monitoring a step further by using [Azure Resource Health](how-to-monitor-resource-health.md) to drill down into specific instances and see whether they're affected.
 
 ## Next steps 
 
 Read about general best practices for HA/DR in these Azure articles: 
-* The article [Design reliable Azure applications](/azure/architecture/framework/resiliency/app-design) describes a general framework to help you think about business continuity and disaster recovery. 
-* The [Disaster recovery and high availability for Azure applications](/azure/architecture/framework/resiliency/backup-and-recovery) paper provides architecture guidance on strategies for Azure applications to achieve High Availability (HA) and Disaster Recovery (DR).
+* [Design review checklist for Reliability](/azure/architecture/framework/resiliency/app-design) describes a general framework to help you think about business continuity and disaster recovery. 
+* [Recommendations for designing a disaster recovery strategy](/azure/architecture/framework/resiliency/backup-and-recovery) provides architecture guidance on strategies for Azure applications to achieve High Availability (HA) and Disaster Recovery (DR).