Merge pull request #268033 from normesta/normesta-reg-updates-13

A quick fix

Author: prmerger-automator[bot]

articles/storage/blobs/network-file-system-protocol-known-issues.md

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: conceptual
-ms.date: 08/18/2023
+ms.date: 03/04/2024
 ms.author: normesta
 ---
 
@@ -21,11 +21,11 @@ This article describes limitations and known issues of Network File System (NFS)
 
 - NFS 3.0 support can't be enabled on existing storage accounts.
 
-- NFS 3.0 support can't be disabled in a storage account after you've enabled it.
+- NFS 3.0 support can't be disabled in a storage account after you enable it.
 
-- GRS, GZRS, and RA-GRS redundancy options aren't supported when you create an NFS 3.0 storage account.
+- Geo-redundant storage (GRS), Geo-zone-redundant storage (GZRS), and Read-access geo-redundant storage (RA-GRS) redundancy options aren't supported when you create an NFS 3.0 storage account.
 
-- Access control lists (ACLs) can't be used to authorize an NFS 3.0 request. In fact, if the ACL or a blob or directory contains an entry for a named user or group, that file becomes inaccessible on the client for non-root users. You'll have to remove these entries to restore access to non-root users on the client.  For information about how to remove an ACL entry for named users and groups, see [How to set ACLs](data-lake-storage-access-control.md#how-to-set-acls).
+- Access control lists (ACLs) can't be used to authorize an NFS 3.0 request. In fact, if the ACL or a blob or directory contains an entry for a named user or group, that file becomes inaccessible on the client for nonroot users. You have to remove these entries to restore access to nonroot users on the client. For information about how to remove an ACL entry for named users and groups, see [How to set ACLs](data-lake-storage-access-control.md#how-to-set-acls).
 
 ## NFS 3.0 features
 
@@ -37,21 +37,21 @@ The following NFS 3.0 features aren't yet supported.
 
 - Mounting subdirectories. You can only mount the root directory (Container).
 
-- Listing mounts (For example: by using the command `showmount -a`)
+- Listing mounts (For example: by using the command `showmount -a`).
 
-- Listing exports (For example: by using the command `showmount -e`)
+- Listing exports (For example: by using the command `showmount -e`).
 
-- Hard link
+- Hard link.
 
-- Exporting a container as read-only
+- Exporting a container as read-only.
 
 ## NFS 3.0 clients
 
-Windows client for NFS is not yet supported.
+Windows client for NFS isn't yet supported. However, there's a workaround available that uses the Windows Subsystem for Linux (WSL 2) to mount storage by using the NFS 3.0 protocol. See the [BlobNFS-wsl2](https://github.com/Azure/BlobNFS-wsl2/tree/develop) project on GitHub.
 
 ## Blob Storage features
 
-When you enable NFS 3.0 protocol support, some Blob Storage features will be fully supported, but some features might be supported only at the preview level or not yet supported at all.
+When you enable NFS 3.0 protocol support, some Blob Storage features are fully supported, but some features might be supported only at the preview level or not yet supported at all.
 
 To see how each Blob Storage feature is supported in accounts that have NFS 3.0 support enabled, see [Blob Storage feature support for Azure Storage accounts](storage-feature-support-in-storage-accounts.md).
 
@@ -62,7 +62,7 @@ To see how each Blob Storage feature is supported in accounts that have NFS 3.0
 
 The names of NFS operations don't appear in resource logs or in responses returned by the Event Grid. Only block blob operations appear. When your application makes a request by using the NFS 3.0 protocol, that request is translated into combination of block blob operations. For example, NFS 3.0 read Remote Procedure Call (RPC) requests are translated into Get Blob operation. NFS 3.0 write RPC requests are translated into a combination of Get Block List, Put Block, and Put Block List.
 
-Storage Events aren't supported for NFS specific operations. However, if you are performing blob or data lake storage operations on NFS enabled account, then the events shall get created based on the API being called.
+Storage Events aren't supported for NFS specific operations. However, if you're performing blob or data lake storage operations on NFS enabled account, then the events shall get created based on the API being called.
 
 ## Group membership in an NFS share