fixed merge issues

Author: flang-msft

articles/azure-cache-for-redis/enterprise-private-public-access.md

@@ -113,15 +113,16 @@ In this section, you add a private endpoint to an existing Azure Managed Redis i
 
 1. Select the **Next: Resource** at the bottom of the pane.
 
-1. In the **Resource** pane, select your **Subscription**. 
+1. In the **Resource** pane, select your **Subscription**.
+
     1. Then, choose the **Resource type** as `Microsoft.Cache/redisEnterprise`.
     1. Then select the cache you want to connect the private endpoint to for the **Resource** property.
 
 1. Select the **Next: Virtual Network** button at the bottom of the pane.
 
 1. In the **Virtual Network** pane, select the **Virtual Network** and **Subnet** you created in the [previous section](#create-a-virtual-network-with-a-subnet).
 
-<!-- We don't talk about DNS zones -->
+    <!-- We don't talk about DNS zones -->
 
 1. Select the **Next: Tags** button at the bottom of the pane.
 

articles/redis/private-link.md

@@ -68,8 +68,6 @@ You can confirm the number of sent packets is equal to the received packets. Con
 Steps to check your private endpoint configuration:
 
 1. Verify if your private endpoint is configured correctly. For more information, see [Create a private endpoint with a new Azure Managed Redis instance](private-link.md#create-a-virtual-network-with-a-subnet).
-1. 
-1. 
 
 1. Verify if your application is connecting to `<instancename>.<region>.redis.azure.net` on port 10000. We recommend avoiding the use of `<instancename>.<region>.privatelink.redis.cache.windows.net` in the configuration or the connection string.