Merge pull request #220497 from whhender/purview-freshness-jingwang

Purview freshness jingwang

Author: prmerger-automator[bot]

articles/purview/concept-data-lineage.md

@@ -5,7 +5,7 @@ author: linda33wj
 ms.author: jingwang
 ms.service: purview
 ms.topic: conceptual
-ms.date: 09/27/2021
+ms.date: 12/05/2022
 ---
 # Data lineage in Microsoft Purview
 

articles/purview/how-to-lineage-azure-synapse-analytics.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 09/27/2021
+ms.date: 12/05/2022
 ---
 # How to get lineage from Azure Synapse Analytics into Microsoft Purview
 
@@ -36,7 +36,7 @@ You can connect an Azure Synapse workspace to Microsoft Purview, and the connect
 
 ### Step 2: Run pipeline in Azure Synapse workspace
 
-You can create pipelines with Copy activity in Azure Synapse workspace. You don't need any additional configuration for lineage data capture. The lineage data will automatically be captured during the activities execution.
+You can create pipelines with Copy activity in Azure Synapse workspace. You don't need any other configuration for lineage data capture. The lineage data will automatically be captured during the activities execution.
 
 ### Step 3: Monitor lineage reporting status
 

articles/purview/how-to-lineage-spark-atlas-connector.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 04/28/2021
+ms.date: 12/05/2022
 ---
 # How to use Apache Atlas connector to collect Spark lineage
 
@@ -24,7 +24,7 @@ Since Microsoft Purview supports Atlas API and Atlas native hook, the connector
 
 ## Configuration requirement
 
-The connectors require a version of Spark 2.4.0+. But Spark version 3 is not supported. The Spark supports three types of listener required to be set:  
+The connectors require a version of Spark 2.4.0+. But Spark version 3 isn't supported. The Spark supports three types of listener required to be set:  
 
 | Listener | 	Since Spark Version|
 | ------------------- | ------------------- | 
@@ -42,7 +42,7 @@ The following steps are documented based on DataBricks as an example:
 
 1.  Generate package
     1. Pull code from GitHub: https://github.com/hortonworks-spark/spark-atlas-connector
-    2. [For Windows] Comment out the **maven-enforcer-plugin** in spark-atlas-connector\pom.xml to remove the dependency on Unix.
+    2. [For Windows], Comment out the **maven-enforcer-plugin** in spark-atlas-connector\pom.xml to remove the dependency on Unix.
 
     ```web
     <requireOS>
@@ -161,14 +161,14 @@ Kick off The Spark job and check the lineage info in your Microsoft Purview acco
 :::image type="content" source="./media/how-to-lineage-spark-atlas-connector/purview-with-spark-lineage.png" alt-text="Screenshot showing purview with spark lineage" lightbox="./media/how-to-lineage-spark-atlas-connector/purview-with-spark-lineage.png":::
 
 ## Known limitations with the connector for Spark lineage
-1. Supports SQL/DataFrame API (in other words, it does not support RDD). This connector relies on query listener to retrieve query and examine the impacts.
+1. Supports SQL/DataFrame API (in other words, it doesn't support RDD). This connector relies on query listener to retrieve query and examine the impacts.
 
 2. All "inputs" and "outputs" from multiple queries are combined into single "spark_process" entity.
 
     "spark_process" maps to an "applicationId" in Spark. It allows admin to track all changes that occurred as part of an application. But also causes lineage/relationship graph in "spark_process" to be complicated and less meaningful.
 3. Only part of inputs is tracked in Streaming query.
 
-* Kafka source supports subscribing with "pattern" and this connector does not enumerate all existing matching topics, or even all possible topics 
+* Kafka source supports subscribing with "pattern" and this connector doesn't enumerate all existing matching topics, or even all possible topics 
 
 * The "executed plan" provides actual topics with (micro) batch reads and processes. As a result, only inputs that participate in (micro) batch are included as "inputs" of "spark_process" entity.
 
@@ -178,7 +178,7 @@ Kick off The Spark job and check the lineage info in your Microsoft Purview acco
 
     The "drop table" event from Spark only provides db and table name, which is NOT sufficient to create the unique key to recognize the table.
 
-    The connector depends on reading the Spark Catalog to get table information. Spark have already dropped the table when this connector notices the table is dropped, so drop table will not work.
+    The connector depends on reading the Spark Catalog to get table information. Spark have already dropped the table when this connector notices the table is dropped, so drop table won't work.
 
 
 ## Next steps

articles/purview/how-to-link-azure-data-factory.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: how-to
-ms.date: 11/01/2021
+ms.date: 12/05/2022
 ---
 # How to connect Azure Data Factory and Microsoft Purview
 
@@ -52,7 +52,7 @@ Follow the steps below to connect an existing data factory to your Microsoft Pur
 
     Some Data Factory instances might be disabled if the data factory is already connected to the current Microsoft Purview account, or the data factory doesn't have a managed identity.
 
-    A warning message will be displayed if any of the selected Data Factories are already connected to other Microsoft Purview account. By selecting OK, the Data Factory connection with the other Microsoft Purview account will be disconnected. No additional confirmations are required.
+    A warning message will be displayed if any of the selected Data Factories are already connected to other Microsoft Purview account. When you select OK, the Data Factory connection with the other Microsoft Purview account will be disconnected. No other confirmations are required.
 
     :::image type="content" source="./media/how-to-link-azure-data-factory/warning-for-disconnect-factory.png" alt-text="Screenshot showing warning to disconnect Azure Data Factory.":::
 
@@ -61,7 +61,7 @@ Follow the steps below to connect an existing data factory to your Microsoft Pur
 
 ### How authentication works
 
-Data factory's managed identity is used to authenticate lineage push operations from data factory to Microsoft Purview. When connecting data factory to Microsoft Purview on UI, it adds the role assignment automatically.
+Data factory's managed identity is used to authenticate lineage push operations from data factory to Microsoft Purview. When you connect your data factory to Microsoft Purview on UI, it adds the role assignment automatically.
 
 Grant the data factory's managed identity **Data Curator** role on Microsoft Purview **root collection**. Learn more about [Access control in Microsoft Purview](../purview/catalog-permissions.md) and [Add roles and restrict access through collections](../purview/how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
 
@@ -127,7 +127,7 @@ An example of this pattern would be the following:
 
 ### Data movement with 1:1 lineage and wildcard support
 
-Another common scenario for capturing lineage, is using a wildcard to copy files from a single input dataset to a single output dataset. The wildcard allows the copy activity to match multiple files for copying using a common portion of the file name. Microsoft Purview captures file-level lineage for each individual file copied by the corresponding copy activity.
+Another common scenario for capturing lineage is using a wildcard to copy files from a single input dataset to a single output dataset. The wildcard allows the copy activity to match multiple files for copying using a common portion of the file name. Microsoft Purview captures file-level lineage for each individual file copied by the corresponding copy activity.
 
 An example of this pattern would be the following:
 

articles/purview/troubleshoot-connections.md

@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 09/27/2021
+ms.date: 12/05/2022
 ms.custom: ignite-fall-2021
 ---
 # Troubleshoot your connections in Microsoft Purview
@@ -90,5 +90,5 @@ If your Microsoft Purview scan used to successfully run, but are now failing, ch
 
 ## Next steps
 
-- [Browse the Microsoft Purview Data catalog](how-to-browse-catalog.md)
+- [Browse the Microsoft Purview Data Catalog](how-to-browse-catalog.md)
 - [Search the Microsoft Purview Data Catalog](how-to-search-catalog.md)