Merge pull request #235868 from sreekzz/patch-161

Freshness MS date update

Author: prmerger-automator[bot]

articles/hdinsight/troubleshoot-sqoop.md

@@ -3,7 +3,7 @@ title: Sqoop import/export command fails for some users in ESP clusters - Azure
 description: 'Apache Sqoop import/export command fails with "Import Failed: java.io.IOException: The ownership on the staging directory /user/yourusername/.staging is not as expected" error for some users in Azure HDInsight ESP cluster'
 ms.service: hdinsight
 ms.topic: troubleshooting
-ms.date: 04/01/2021
+ms.date: 04/26/2023
 ---
 
 # Scenario: Sqoop import/export command fails for usernames greater than 20 characters in Azure HDInsight ESP clusters
@@ -12,16 +12,16 @@ This article describes a known issue and workaround when using Azure HDInsight E
 
 ## Issue
 
-When running sqoop import/export command, it fails with the error below for some users:
+When you run sqoop import/export command, it fails with the error for some users:
 
 ```
 ERROR tool.ImportTool: Import failed: java.io.IOException:
-The ownership on the staging directory /user/yourlongdomainuserna/.staging is not as expected. 
+The ownership on the staging directory /user/yourlongdomainuserna/.staging isn't as expected. 
 It is owned by yourlongdomainusername.
 The directory must be owned by the submitter yourlongdomainuserna or [email protected]
 ```
 
-In the example above, `/user/yourlongdomainuserna/.staging` displays the truncated 20 character username for the username `yourlongdomainusername`.
+In the example, `/user/yourlongdomainuserna/.staging` displays the truncated 20 character username for the username `yourlongdomainusername`.
 
 ## Cause