Update reliability-container-registry.md

Author: v-stsavell

articles/reliability/reliability-container-registry.md

@@ -99,10 +99,9 @@ Zone redundancy is included with Premium tier registries at no extra cost. The P
 
 - **Enable zone redundancy on an existing registry.** You can only configure zone redundancy when a registry is created. To enable zone redundancy for registries, you must create a new Premium registry in a supported region and migrate your container images. 
 
+   Existing Basic or Standard tier registries can be upgraded to Premium tier. However, the upgrade itself doesn't enable zone redundancy, and you still have to create a new registry in the Premium tier. 
 
-Although existing Basic or Standard tier registries can be upgraded to Premium tier, the upgrade itself doesn't enable zone redundancy, and you'll still have to create a new registry in the Premium tier. 
-
-    To migrate your artifacts between registries, you can [create a transfer pipeline](/azure/container-registry/container-registry-transfer-prerequisites). Alternatively, you can [import container images to a container registry](/azure/container-registry/container-registry-import-images).
+   To migrate your artifacts between registries, you can [create a transfer pipeline](/azure/container-registry/container-registry-transfer-prerequisites). Alternatively, you can [import container images to a container registry](/azure/container-registry/container-registry-import-images).
 
     If your registry uses [geo-replication](#multi-region-support) and zone redundancy together, you can configure zone redundancy on each regional replica. For more information, see [Create a zone-redundant replica in Container Registry](/azure/container-registry/zone-redundancy-replica).  After a geo-replication is created, you can only change the zone redundancy setting by deleting and recreating the replication.