editorial changes

Author: AmandaAZ

support/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity.md

@@ -4,8 +4,8 @@ description: Troubleshoot problems connecting to and accessing SMB Azure file sh
 services: storage
 ms.service: azure-file-storage
 ms.custom: sap:Connectivity, devx-track-azurepowershell, linux-related-content
-ms.date: 02/04/2025
-ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal
+ms.date: 04/24/2025
+ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal, justingross
 ---
 # Troubleshoot Azure Files connectivity and access issues (SMB)
 
@@ -137,17 +137,17 @@ Revert the `LmCompatibilityLevel` value to the default value of 3 in the followi
 
 ### <a id="error-64"></a> Error 64 when you mount an Azure file share
 
-When you try to mount a file share from on-premises or a different datacenter, you might receive the following error:
+When mounting a file share from on-premises or another datacenter, you might see the following error:
 
-- System error 64 has occurred. The specified network name is no longer available.
+> System error 64 has occurred. The specified network name is no longer available.
 
 #### Cause
 
-This most likely has to do with a proxy server or any other kind of NAT device in the datapath that is blocking the connection to map the Azure file share. Using the PowerShell cmdlet ```test-netconnection``` to test for connectivity on port 445 may still be successful.
+This issue is likely caused by a proxy server or another type of Network Address Translation (NAT) device in the datapath that blocks the connection to map the Azure file share. In this case, the PowerShell cmdlet `Test-NetConnection` still might test connectivity on port 445 successfully.
 
 #### Solution
 
-A network trace taken during a reproduction of the issue will show more information on where the error is originating from. In most cases you will need to work with your network/firewall administrators to allow this content to pass through the network device.
+To resolve this issue, reproduce it and collect a network trace to get more information about the error's origin. In most cases, you must work with your network/firewall administrator to allow the content to pass through the network device.
 
 ### <a id="error-0x800704b3"></a> Failed with error code 0x800704b3