3rd refine

dearandyxu · dearandyxu · commit b40424f69e0e · 2020-05-13T17:58:53.000+08:00
diff --git a/articles/data-factory/TOC.yml b/articles/data-factory/TOC.yml
@@ -414,6 +414,8 @@
       href: copy-activity-schema-and-type-mapping.md
     - name: Fault tolerance
       href: copy-activity-fault-tolerance.md
+    - name: Data consistency verification
+      href: copy-activity-data-consistency.md
     - name: Format and compression support (legacy)
       href: supported-file-formats-and-compression-codecs-legacy.md
   - name: Transform data
diff --git a/articles/data-factory/copy-activity-data-consistency.md b/articles/data-factory/copy-activity-data-consistency.md
@@ -98,7 +98,7 @@ path | The path of the log file. | Specify the path that you want to store the l
 ## Monitoring
 
 ### Output from copy activity
-After the copy activity run completely, you can see the result of data consistency verification from the output of each copy activity run:
+After the copy activity runs completely, you can see the result of data consistency verification from the output of each copy activity run:
 
 ```json
 "output": {
@@ -148,7 +148,7 @@ The example of a log file is as following:
 Timestamp, Level, OperationName, OperationItem, Message
 2020-02-26 06:22:56.3190846, Warning, FileSkip, "sample1.csv", "File is skipped after read 548000000 bytes: ErrorCode=DataConsistencySourceDataChanged,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Source file 'sample1.csv' is changed by other clients during the copy activity run.,Source=,'." 
 ```
-From the log file above, you can see sample1.csv has been skipped because it failed to be verified to be consistent between source and destination store. You can get more details about why sample1.csv becomes inconsistent is because it was under changing by other applications when ADF copy activity is copying at the same time. 
+From the log file above, you can see sample1.csv has been skipped because it failed to be verified to be consistent between source and destination store. You can get more details about why sample1.csv becomes inconsistent is because it was underchanging by other applications when ADF copy activity is copying at the same time. 
 
 
 
diff --git a/articles/data-factory/copy-activity-fault-tolerance.md b/articles/data-factory/copy-activity-fault-tolerance.md
@@ -23,17 +23,17 @@ ms.author: yexu
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
-When you copy data from source to destination store, Azure Data Factory copy activity provides certain level of fault tolerances to prevent interruption from a sort of failures in the middle of data movement. For example, you are copying millions of rows from source to destination store, where a primary key has been created in the destination database, but source database does not have any primary keys. When you happen to copy duplicated rows from source to the destination, you will hit the PK violation failure on the destination database. At this moments, copy activity offers you two ways to handle such errors: 
+When you copy data from source to destination store, Azure Data Factory copy activity provides certain level of fault tolerances to prevent interruption from a sort of failures in the middle of data movement. For example, you are copying millions of rows from source to destination store, where a primary key has been created in the destination database, but source database does not have any primary keys. When you happen to copy duplicated rows from source to the destination, you will hit the PK violation failure on the destination database. At this moment, copy activity offers you two ways to handle such errors: 
 - You can abort the copy activity once any failure is encountered. 
-- You can continue to copy the rest by enabling fault tolerance to skip the incompatible data. For example, skip the duplicated row in this case. In addition, you can log the skipped data by enabling session log in copy activity. 
+- You can continue to copy the rest by enabling fault tolerance to skip the incompatible data. For example, skip the duplicated row in this case. In addition, you can log the skipped data by enabling session log within copy activity. 
 
 ## Copying binary files 
 
-ADF supports the following fault tolerance scenario when copying binary files. You can choose to abort the copy activity or continue to copy the rest in the following scenario:
+ADF supports the following fault tolerance scenario when copying binary files. You can choose to abort the copy activity or continue to copy the rest in the following scenarios:
 
-1. The files to be copied by ADF are under deleting via other applications at the same time.
+1. The files to be copied by ADF are being deleted by other applications at the same time.
 2. Some particular folders or files do not allow ADF to access because ACLs of those files or folders require higher permission level than the connection configured in ADF.
-3. One or more files are not verified to be consistent between source and destination store when ADF check their file size or MD5 after copying.
+3. One or more files are not verified to be consistent between source and destination store if you enable data consistency verification setting in ADF.
 
 ### Configuration 
 When you copy binary files between storage stores, you can enable fault tolerance as followings: 
@@ -71,8 +71,8 @@ When you copy binary files between storage stores, you can enable fault toleranc
 Property | Description | Allowed values | Required
 -------- | ----------- | -------------- | -------- 
 skipErrorFile | A group of properties to specify the types of failures you want to skip during the data movement. | | No
-fileMissing | One of the key-value pairs within skipErrorFile property bag to determine if you want to skip files which are being deleted by other applications when ADF is copying in the meanwhile. <br/> -True: you want to copy the rest by skipping the files being deleted by other applications. <br/> - False: you want to abort the copy activity once any files are being deleted from source store in the middle of data movement. <br/>Be aware this property is set to true as default. | True(default) <br/>False | No
-fileForbidden | One of the key-value pairs within skipErrorFile property bag to determine if you want to skip the particular files which you do not have permission to access, read or write.  <br/> -True: you want to copy the rest by skipping the files which you have the permission issue to access, read or write. <br/> - False: you want to abort the copy activity once meeting the permission issue to access, read or write files. | True <br/>False(default) | No
+fileMissing | One of the key-value pairs within skipErrorFile property bag to determine if you want to skip files, which are being deleted by other applications when ADF is copying in the meanwhile. <br/> -True: you want to copy the rest by skipping the files being deleted by other applications. <br/> - False: you want to abort the copy activity once any files are being deleted from source store in the middle of data movement. <br/>Be aware this property is set to true as default. | True(default) <br/>False | No
+fileForbidden | One of the key-value pairs within skipErrorFile property bag to determine if you want to skip the particular files, which you do not have permission to access.  <br/> -True: you want to copy the rest by skipping the files, which you have the permission issue to access. <br/> - False: you want to abort the copy activity once meeting the permission issue to access. | True <br/>False(default) | No
 dataInconsistency | One of the key-value pairs within skipErrorFile property bag to determine if you want to skip the inconsistent data between source and destination store. <br/> -True: you want to copy the rest by skipping inconsistent data. <br/> - False: you want to abort the copy activity once inconsistent data found. <br/>Be aware this property is only valid when you set validateDataConsistency as True. | True <br/>False(default) | No
 logStorageSettings  | A group of properties that can be specified when you want to log the skipped object names. | &nbsp; | No
 linkedServiceName | The linked service of [Azure Blob Storage](connector-azure-blob-storage.md#linked-service-properties) or [Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md#linked-service-properties) to store the session log file. | The names of an `AzureBlobStorage` or `AzureBlobFS` type linked service, which refers to the instance that you want to use to store the log file. | No
@@ -81,7 +81,7 @@ path | The path of the log file. | Specify the path that you want to use to stor
 ### Monitoring 
 
 #### Output from copy activity
-You can get the number of files being read, written and skipped via the output of each copy activity run. 
+You can get the number of files being read, written, and skipped via the output of each copy activity run. 
 
 ```json
 "output": {
@@ -218,7 +218,7 @@ From the sample log file above, you can see one row "data1, data2, data3" has be
 
 ## Copying tabular data (Legacy):
 
-The following is the legacy way to enable fault tolerance for copying non-binary data only. If you are creating new pipeline or activity, you are encouraged to start from [here](#fault-tolerance-for-copying-non-binary-data) instead.
+The following is the legacy way to enable fault tolerance for copying non-binary data only. If you are creating new pipeline or activity, you are encouraged to start from [here](#copying-tabular-data) instead.
 
 ### Configuration
 The following example provides a JSON definition to configure skipping the incompatible rows in Copy Activity:
