Freshness on Disaster Recovery conceptual article

Author: jpconnock

articles/azure-app-configuration/concept-disaster-recovery.md

@@ -5,7 +5,7 @@ author: lisaguthrie
 ms.author: lcozzens
 ms.service: azure-app-configuration
 ms.topic: conceptual
-ms.date: 05/29/2019
+ms.date: 02/20/2020
 ---
 
 # Resiliency and disaster recovery
@@ -22,7 +22,7 @@ Your application loads its configuration from both the primary and secondary sto
 
 ## Failover between configuration stores
 
-Technically, your application isn't executing a failover. It's attempting to retrieve the same set of configuration data from two App Configuration stores simultaneously. Arrange your code so that it loads from the secondary store first and then the primary store. This approach ensures that the configuration data in the primary store takes precedence whenever it's available. The following code snippet shows how you can implement this arrangement in the .NET Core CLI:
+Technically, your application isn't executing a failover. It's attempting to retrieve the same set of configuration data from two App Configuration stores simultaneously. Arrange your code so that it loads from the secondary store first and then the primary store. This approach ensures that the configuration data in the primary store takes precedence whenever it's available. The following code snippet shows how you can implement this arrangement in .NET Core:
 
 #### [.NET Core 2.x](#tab/core2x)
 
@@ -65,17 +65,18 @@ From the Azure portal, you can push a change to another configuration store by f
 
 1. Go to the **Import/Export** tab, and select **Export** > **App Configuration** > **Target** > **Select a resource**.
 
-2. In the new blade that opens, specify the subscription, resource group, and resource name of your secondary store, and then select **Apply**.
+1. In the new blade that opens, specify the subscription, resource group, and resource name of your secondary store, then select **Apply**.
 
-3. The UI is updated so that you can choose what configuration data you want to export to your secondary store. You can leave the default time value as is and set both **From label** and **To label** to the same value. Select **Apply**.
+1. The UI is updated so that you can choose what configuration data you want to export to your secondary store. You can leave the default time value as is and set both **From label** and **To label** to the same value. Select **Apply**.
 
-4. Repeat the previous steps for all configuration changes.
+1. Repeat the previous steps for all configuration changes.
 
 To automate this export process, use the Azure CLI. The following command shows how to export a single configuration change from the primary store to the secondary:
 
+```azurecli
     az appconfig kv export --destination appconfig --name {PrimaryStore} --label {Label} --dest-name {SecondaryStore} --dest-label {Label}
+```
 
 ## Next steps
 
 In this article, you learned how to augment your application to achieve geo-resiliency during runtime for App Configuration. You also can embed configuration data from App Configuration at build or deployment time. For more information, see [Integrate with a CI/CD pipeline](./integrate-ci-cd-pipeline.md).
-