Merge pull request #203060 from linda33wj/purview

Clarify classification support - batch 1

Author: PRMerger10

articles/purview/register-scan-cassandra-source.md

@@ -75,7 +75,7 @@ To register a new Cassandra server in your data catalog:
 
 ## Scan
 
-Follow the steps below to scan Cassandra to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
+Follow the steps below to scan Cassandra to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
 
 ### Create and run scan
 

articles/purview/register-scan-db2.md

@@ -91,7 +91,7 @@ On the **Register sources (Db2)** screen, do the following:
 
 ## Scan
 
-Follow the steps below to scan Db2 to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+Follow the steps below to scan Db2 to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
 
 ### Authentication for a scan
 

articles/purview/register-scan-erwin-source.md

@@ -102,7 +102,7 @@ On the Register sources (erwin) screen, do the following:
 
 ## Scan
 
-Follow the steps below to scan erwin Mart servers to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
+Follow the steps below to scan erwin Mart servers to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
 
 ### Create and run scan
 

articles/purview/register-scan-google-bigquery-source.md

@@ -84,7 +84,7 @@ On the Register sources (Google BigQuery) screen, do the following:
 
 ## Scan
 
-Follow the steps below to scan a Google BigQuery project to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+Follow the steps below to scan a Google BigQuery project to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
 
 ### Create and run scan
 

articles/purview/register-scan-hive-metastore-source.md

@@ -92,7 +92,7 @@ The only supported authentication for a Hive Metastore database is Basic Authent
 > 1. Confirm you have followed all [**prerequisites**](#prerequisites).
 > 1. Review our [**scan troubleshooting documentation**](troubleshoot-connections.md).
 
-Use the following steps to scan Hive Metastore databases to automatically identify assets and classify your data. For more information about scanning in general, see [Scans and ingestion in Microsoft Purview](concept-scans-and-ingestion.md).
+Use the following steps to scan Hive Metastore databases to automatically identify assets. For more information about scanning in general, see [Scans and ingestion in Microsoft Purview](concept-scans-and-ingestion.md).
 
 1. In the Management Center, select integration runtimes. Make sure that a self-hosted integration runtime is set up. If it isn't set up, use the steps in [Create and manage a self-hosted integration runtime](./manage-integration-runtimes.md).
 

articles/purview/register-scan-looker-source.md

@@ -88,7 +88,7 @@ On the Register sources (Looker) screen, follow these steps:
 
 ## Scan
 
-Follow the steps below to scan Looker to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
+Follow the steps below to scan Looker to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md)
 
 ### Create and run scan
 

articles/purview/register-scan-mongodb.md

@@ -74,7 +74,7 @@ On the **Register sources (MongoDB)** screen, do the following:
 
 ## Scan
 
-Follow the steps below to scan MongoDB to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+Follow the steps below to scan MongoDB to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
 
 ### Authentication for a scan
 

articles/purview/register-scan-mysql.md

@@ -85,7 +85,7 @@ On the **Register sources (MySQL)** screen, follow these steps:
 
 ## Scan
 
-Follow the steps below to scan MySQL to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+Follow the steps below to scan MySQL to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
 
 ### Authentication for a scan
 

articles/purview/register-scan-oracle-source.md

@@ -137,7 +137,7 @@ On the **Register sources (Oracle)** screen, do the following:
 
 ## Scan
 
-Follow the steps below to scan Oracle to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+Follow the steps below to scan Oracle to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
 
 > [!TIP]
 > To troubleshoot any issues with scanning: