Update dataflowTSG

Author: jess-hu-340

articles/data-factory/data-flow-troubleshoot-guide.md

@@ -197,8 +197,7 @@ This section lists common error codes and messages reported by mapping data flow
 ### Error code: DF-CSVWriter-InvalidQuoteSetting 
 
 - **Message**: Job failed while writing data with error: Quote character and escape character cannot be empty if column value contains column delimiter 
-- **Cause**: Both quote characters and esca 
-pe characters are empty when column value contains column delimiter. 
+- **Cause**: Both quote characters and the escape characters are empty when column value contains column delimiter. 
 - **Recommendation**: Set your quote character or escape character. 
 
 ### Error code: DF-Delimited-ColumnDelimiterMissed
@@ -501,9 +500,9 @@ F-D
 
 - **Cause**: You are not permitted to access the storage account either due to missing roles for managed identity/service principal authentication or network firewall settings. 
 - **Recommendation**: When using managed identity/service principal authentication, 
-1. For source: In Storage Explorer, grant the managed identity/service principal at least **Execute** permission for ALL upstream folders and the file system, along with **Read** permission for the files to copy. Alternatively, in Access control (IAM), grant the managed identity/service principal at least the **Storage Blob Data Reader** role. 
-2. For sink: In Storage Explorer, grant the managed identity/service principal at least **Execute** permission for ALL upstream folders and the file system, along with **Write** permission for the sink folder. Alternatively, in Access control (IAM), grant the managed identity/service principal at least the **Storage Blob Data Contributor** role. 
-Also please ensure that the network firewall settings in the storage account are configured correctly, as turning on firewall rules for your storage account blocks incoming requests for data by default, unless the requests originate from a service operating within an Azure Virtual Network (VNet) or from allowed public IP addresses. 
+    1. For source: In Storage Explorer, grant the managed identity/service principal at least **Execute** permission for ALL upstream folders and the file system, along with **Read** permission for the files to copy. Alternatively, in Access control (IAM), grant the managed identity/service principal at least the **Storage Blob Data Reader** role. 
+    2. For sink: In Storage Explorer, grant the managed identity/service principal at least **Execute** permission for ALL upstream folders and the file system, along with **Write** permission for the sink folder. Alternatively, in Access control (IAM), grant the managed identity/service principal at least the **Storage Blob Data Contributor** role. 
+    Also please ensure that the network firewall settings in the storage account are configured correctly, as turning on firewall rules for your storage account blocks incoming requests for data by default, unless the requests originate from a service operating within an Azure Virtual Network (VNet) or from allowed public IP addresses. 
 
 ### Error code: DF-Executor-UnreachableStorageAccount 
 
@@ -668,9 +667,9 @@ Also please ensure that the network firewall settings in the storage account are
 ### Error code: DF-SAPODP-DataParsingFailed 
 
 - **Cause**: Mostly you have hidden column settings in your SAP table. When you use SAP mapping data flow to read data from SAP server, it returns all the schema (columns, including hidden ones), but returned data do not contain related values. So, data misalignment happened and lead to parse value issue or wrong data value issue.  
-- **Recommendation**: There are two solutions for this issue： 
-1. Remove hidden settings from the related column(s) through SAP GUI.   
-2. If you want to keep existed SAP settings unchanged, use hidden feature (manually add DSL property `enableProjection:true` in script) in SAP mapping data flow to filter the hidden column(s) and continue to read data.  
+- **Recommendation**: There are two recommendations for this issue： 
+    1. Remove hidden settings from the related column(s) through SAP GUI.   
+    2. If you want to keep existed SAP settings unchanged, use hidden feature (manually add DSL property `enableProjection:true` in script) in SAP mapping data flow to filter the hidden column(s) and continue to read data.  
 
 ### Error code: DF-SAPODP-ObjectInvalid