removed metadata ops limit

Author: khdownie

articles/storage/files/storage-troubleshooting-files-performance.md

@@ -4,14 +4,14 @@ description: Troubleshoot known performance issues with Azure file shares. Disco
 author: khdownie
 ms.service: storage
 ms.topic: troubleshooting
-ms.date: 07/06/2021
+ms.date: 10/03/2022
 ms.author: kendownie
 ms.subservice: files
 #Customer intent: As a < type of user >, I want < what? > so that < why? >.
 ---
 # Troubleshoot Azure file shares performance issues
 
-This article lists some common problems related to Azure file shares. It provides potential causes and workarounds for when you encounter these problems.
+This article lists some common problems related to Azure file shares and provides potential causes and workarounds.
 
 ## Applies to
 | File share type | SMB | NFS |
@@ -76,10 +76,9 @@ To determine whether most of your requests are metadata-centric, start by follow
 #### Workaround
 
 - Check to see whether the application can be modified to reduce the number of metadata operations.
-- Add a virtual hard disk (VHD) on the file share and mount the VHD from the client to perform file operations against the data. This approach works for single writer/reader scenarios or scenarios with multiple readers and no writers. Because the file system is owned by the client rather than Azure Files, this allows metadata operations to be local. The setup offers performance similar to that of a local directly attached storage.
-    -   To mount a VHD on a Windows client, use the [Mount-DiskImage](/powershell/module/storage/mount-diskimage) PowerShell cmdlet.
-    -   To mount a VHD on Linux, consult the documentation for your Linux distribution.
-- If you're continuously hitting the metadata operations limit that a single Azure file share can accommodate (2,000 operations per file share), we suggest separating the file share into multiple file shares within the same storage account.
+- Add a virtual hard disk (VHD) on the file share and mount the VHD from the client to perform file operations against the data. This approach works for single writer/reader scenarios or scenarios with multiple readers and no writers. Because the file system is owned by the client rather than Azure Files, this allows metadata operations to be local. The setup offers performance similar to that of local directly attached storage.
+    -   To mount a VHD on a Windows client, use the [`Mount-DiskImage`](/powershell/module/storage/mount-diskimage) PowerShell cmdlet.
+    -   To mount a VHD on Linux, consult the documentation for your Linux distribution. [Here's an example](https://man7.org/linux/man-pages/man5/nfs.5.html).  
 
 ### Cause 3: Single-threaded application