edit

Author: anaharris-ms

articles/reliability/availability-zones-service-support.md

@@ -1,6 +1,6 @@
 ---
 title: Azure services that support availability zones
-description: Learn what services are supported by availability zones and understand resiliency across all Azure services.
+description: Learn which services offer availability zone support and understand resiliency across all Azure services.
 ms.service: reliability
 ms.subservice: availability-zones
 ms.topic: conceptual
@@ -43,7 +43,7 @@ The following regions currently support availability zones:
 
 
 
-\* To learn more about availability zones and available services support in these regions, contact your Microsoft sales or customer representative. For the upcoming regions that will support availability zones, see [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/).
+\* To learn more about availability zones and available services support in these regions, contact your Microsoft sales or customer representative. For upcoming regions that support availability zones, see [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/).
 
 ## Azure services with availability zone support
 
@@ -77,7 +77,7 @@ Azure offerings are grouped into three categories that reflect their _regional_
 
 
 >[!IMPORTANT]
->Some services, although they are zone-redundant, may have limited support for availability zones. For example, some may only support availability zones for certain tiers, regions, or SKUs. To get more information on service limitations for availability zone support, select that service in the table below.
+>Some services, although they are zone-redundant, may have limited support for availability zones. For example, some may only support availability zones for certain tiers, regions, or SKUs. To get more information on service limitations for availability zone support, select that service in the following table.
 
 ### ![An icon that signifies this service is foundational.](media/icon-foundational.svg) Foundational services
 
@@ -208,7 +208,7 @@ Azure offerings are grouped into three categories that reflect their _regional_
 | Azure Bot Services  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
 | Azure Cloud Shell  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
 | Azure Content Delivery Network  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
-| Azure Cost Management and Billing | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
+| Azure Cost Management | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
 | Microsoft Defender for IoT  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
 | Azure DNS  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |
 | Azure Front Door  | ![An icon that signifies this service is always available.](media/icon-always-available.svg) |

articles/reliability/reliability-notification-hubs.md

@@ -84,8 +84,8 @@ Paired and flexible region recovery only backs up metadata. You must implement a
 
 Azure Notification Hubs supports two types of device registrations: installations and registrations. We recommend that you back up your registrations to either:
 
-1. **A storage solution of your choice**: If a DR event occurs, there will be some downtime for restoration activities.
-1. **Another hub you create in another region**: Use this option to back up your registrations. As a working hub, you can implement code to switch to this copy. To keep a secondary notification hub in sync with the primary notification hub, you can use one of the following options to back up your registrations:
+-  **A storage solution of your choice**: If a DR event occurs, there will be some downtime for restoration activities.
+- **Another hub you create in another region**: Use this option to back up your registrations. As a working hub, you can implement code to switch to this copy. To keep a secondary notification hub in sync with the primary notification hub, you can use one of the following options to back up your registrations:
    - **For installations**: Use an app backend that simultaneously creates and updates installations in both notification hubs. Installations enable you to specify your own unique device identifier, making it more suitable for the replication scenario. For more information, see this [sample code](https://github.com/Azure/azure-notificationhubs-dotnet/tree/main/Samples/RedundantHubSample).
    - **For registrations**: Use an app backend that gets a regular dump of registrations from the primary notification hub as a backup. It can then perform a bulk insert into the secondary notification hub. See [Export and import Azure Notification Hubs registrations in bulk](/azure/notification-hubs/export-modify-registrations-bulk).