resolve blocking issues

Author: b-ahibbard

articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md

@@ -44,7 +44,7 @@ In this section we’ll focus on how to configure the Linux client and how to ch
 
 ## Configure NFSv4.1 ID domain on Azure NetApp Files
 
-You can specify a desired NFSv4.1 ID domain for all non-LDAP volumes using the Azure portal. This setting applies applies to all non-LDAP volumes across all NetApp accounts in the same subscription and region. It does not affect LDAP-enabled volumes in the same NetApp subscription and region. 
+You can specify a desired NFSv4.1 ID domain for all non-LDAP volumes using the Azure portal. This setting applies to all non-LDAP volumes across all NetApp accounts in the same subscription and region. It does not affect LDAP-enabled volumes in the same NetApp subscription and region. 
 
 ### Register the feature
 
@@ -72,7 +72,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 1. Select **Configure**.
 1. To use the default domain `defaultv4iddomain.com`, select the box next to **Use Default NFSv4 ID Domain**. To use another domain, uncheck the text box and provide the name of the NFSv4.1 ID domain.
 
-  :::image type="content" source="../media/azure-netapp-files/nfsv4-id-domain.png" alt-text="Screenshot with field to set NFSv4 domain." lightbox="../media/azure-netapp-files/nfsv4-id-domain.png":::
+    :::image type="content" source="../media/azure-netapp-files/nfsv4-id-domain.png" alt-text="Screenshot with field to set NFSv4 domain." lightbox="../media/azure-netapp-files/nfsv4-id-domain.png":::
 
 1. Select **Save**.
 

articles/azure-netapp-files/configure-ldap-extended-groups.md

@@ -27,7 +27,7 @@ Azure NetApp Files supports fetching of extended groups from the LDAP name servi
 When it’s determined that LDAP will be used for operations such as name lookup and fetching extended groups, the following process occurs:
 
 1. Azure NetApp Files uses an LDAP client configuration to make a connection attempt to the AD DS/Azure AD DS LDAP server that is specified in the [Azure NetApp Files AD configuration](create-active-directory-connections.md).
-1. If the TCP connection over the defined AD DS/Azure AD DS LDAP service port is successful, then the Azure NetApp Files LDAP client attempts to “bind” (sign in) to the AD DS/Azure ADDS LDAP server (domain controller) by using the defined credentials in the LDAP client configuration.
+1. If the TCP connection over the defined AD DS/Azure AD DS LDAP service port is successful, then the Azure NetApp Files LDAP client attempts to “bind” (sign in) to the AD DS/Azure AD DS LDAP server (domain controller) by using the defined credentials in the LDAP client configuration.
 1. If the bind is successful, then the Azure NetApp Files LDAP client uses the RFC 2307bis LDAP schema to make an LDAP search query to the AD DS/Azure AD DS LDAP server (domain controller).
 The following information is passed to the server in the query:
    * [Base/user DN](configure-ldap-extended-groups.md#ldap-search-scope) (to narrow search scope)