PR prepublishing review blocking & non-blocking issues

Author: b-hchen

articles/azure-netapp-files/dual-protocol-permission-behaviors.md

@@ -42,8 +42,8 @@ In a dual-protocol NAS environment, only one security permission style can be ac
 
 | Security style | Considerations |
 | - | - |
-| UNIX | <ul><li>Windows clients can only set UNIX permission attributes through SMBs that map to UNIX attributes (Read/Write/Execute only; no special permissions). </li> <li>NFSv4.x ACLs don't have GUI management. Management is done only via CLI using [nfs4_getfacl and nfs4_setfacl commands](https://manpages.debian.org/testing/nfs4-acl-tools/index.html). </li> <li> If a file or folder has NFSv4.x ACLs, the Windows security properties tab can't display them. </li></ul>| 
-| NTFS | <ul><li> UNIX clients can't set attributes through NFS via commands such as `chown/chmod`.  </li>  <li>NFS clients show only approximated NTFS permissions when using `ls` commands. For instance, if a user has a permission in a Windows NTFS ACL that can't be cleanly translated into a POSIX mode bit (such as traverse directory), it's translated into the closest POSIX mode-bit value (such as `1` for execute). </li></ul>|
+| UNIX | - Windows clients can only set UNIX permission attributes through SMBs that map to UNIX attributes (Read/Write/Execute only; no special permissions). <br> - NFSv4.x ACLs don't have GUI management. Management is done only via CLI using [nfs4_getfacl and nfs4_setfacl commands](https://manpages.debian.org/testing/nfs4-acl-tools/index.html). <br> - If a file or folder has NFSv4.x ACLs, the Windows security properties tab can't display them. <br> | 
+| NTFS | -  UNIX clients can't set attributes through NFS via commands such as `chown/chmod`.  <br> - NFS clients show only approximated NTFS permissions when using `ls` commands. For instance, if a user has a permission in a Windows NTFS ACL that can't be cleanly translated into a POSIX mode bit (such as traverse directory), it's translated into the closest POSIX mode-bit value (such as `1` for execute). <br> |
 
 The selection of volume security style determines how the name mapping for a user is performed. This operation is the core piece of how dual-protocol volumes maintain predictable permissions regardless of protocol in use.
 
@@ -108,7 +108,7 @@ The following figure shows an example of that kind of configuration.
 
 :::image type="content" source="../media/azure-netapp-files/hub-spoke-dual-protocol.png" alt-text="Illustration that shows hub spoke architecture with Azure NetApp Files and Active Directory cloud resident, NAS clients on-premises." lightbox="../media/azure-netapp-files/hub-spoke-dual-protocol.png":::
 
-## Next Steps
+## Next steps
 
 * [Understand the use of LDAP with Azure NetApp Files](lightweight-directory-access-protocol.md)
 * [Create a dual-protocol volume for Azure NetApp Files](create-volumes-dual-protocol.md)

articles/azure-netapp-files/lightweight-directory-access-protocol.md

@@ -1,5 +1,5 @@
 ---
-title: Understand the use of LDAP with Azure NetApp Files | Microsoft Docs
+title: Understand the use of LDAP with Azure NetApp Files | Microsoft Learn
 description: This article helps you understand how Azure NetApp Files uses lightweight directory access protocol (LDAP).  
 services: azure-netapp-files
 documentationcenter: ''
@@ -169,7 +169,7 @@ The schema type currently used by Azure NetApp Files is a form of schema based o
 
 This RFC extension fits nicely into how Microsoft Active Directory manages users and groups through the usual management tools. This is because when you add a Windows user to a group (and if that group has a valid numeric GID) using the standard Windows management methods, LDAP lookups will pull the necessary supplemental group information from the usual Windows attribute and find the numeric GIDs automatically.
 
-## Next Steps
+## Next steps
 
 * [Configure AD DS LDAP over TLS for Azure NetApp Files](configure-ldap-over-tls.md) 
 * [Understand NFS group memberships and supplemental groups](network-file-system-group-memberships.md)

articles/azure-netapp-files/network-attached-storage-protocols.md

@@ -1,5 +1,5 @@
 ---
-title: Understand NAS protocols in Azure NetApp Files | Microsoft Docs
+title: Understand NAS protocols in Azure NetApp Files | Microsoft Learn
 description: Learn how SMB, NFS, and dual protocols operate in Azure NetApp Files.  
 services: azure-netapp-files
 documentationcenter: ''
@@ -161,7 +161,7 @@ In the following illustration, `user1` authenticates to Azure NetApp Files to ac
 
 In this instance, `user1` gets full control on their own folder (`user1-dir`) and no access to the `HR` folder. This setting is based on the security ACLs specified in the file system, and `user1` will get the expected access regardless of which protocol they're accessing the volumes from.
 
-:::image type="content" source="../media/azure-netapp-files/user1-dual-protocol-example.png" alt-text="Example of user accessing a dual-protocol volume with Azure NetApp Files." lightbox="../media/azure-netapp-files/user1-dual-protocol-example.png":::
+:::image type="content" source="../media/azure-netapp-files/user1-dual-protocol-example.png" alt-text="Diagram of user accessing a dual-protocol volume with Azure NetApp Files." lightbox="../media/azure-netapp-files/user1-dual-protocol-example.png":::
 
 ### Considerations for Azure NetApp Files dual-protocol volumes
 

articles/azure-netapp-files/network-file-system-group-memberships.md

@@ -1,5 +1,5 @@
 ---
-title: Understand NFS group memberships and supplemental groups for Azure NetApp Files | Microsoft Docs
+title: Understand NFS group memberships and supplemental groups for Azure NetApp Files | Microsoft Learn
 description: This article helps you understand NFS group memberships and supplemental groups as they apply to Azure NetApp Files.  
 services: azure-netapp-files
 documentationcenter: ''
@@ -56,7 +56,7 @@ The options to extend the group limitation work the same way that the `manage-gi
 
 The following example shows RPC packet with 16 GIDs.
 
-:::image type="content" source="../media/azure-netapp-files/remote-procedure-call-packets.png" alt-text="Example that shows RPC packet with 16 GIDs." lightbox="../media/azure-netapp-files/remote-procedure-call-packets.png":::
+:::image type="content" source="../media/azure-netapp-files/remote-procedure-call-packets.png" alt-text="Screenshot that shows RPC packet with 16 GIDs." lightbox="../media/azure-netapp-files/remote-procedure-call-packets.png":::
 
 Any GID past the limit of 16 is dropped by the protocol. With extended groups in Azure NetApp Files, when a new NFS request comes in, information about the user’s group membership is requested.