Fix broken link and increase Acrolinx score

Author: linda33wj

articles/purview/how-to-monitor-scan-runs.md

@@ -15,13 +15,13 @@ In Microsoft Purview, you can register and scan various types of data sources, a
 
 ## Monitor scan runs
 
-1. Go to your Microsoft Purview account -> open **Microsoft Purview governance portal** -> **Data map** -> **Monitoring**. You need to have **Data source admin** role on any collection to access this page. And you will see the scan runs that belong to the collections on which you have data source admin privilege.
+1. Go to your Microsoft Purview account -> open **Microsoft Purview governance portal** -> **Data map** -> **Monitoring**. You need to have **Data source admin** role on any collection to access this page. And you'll see the scan runs that belong to the collections on which you have data source admin privilege.
 
-1. The high-level KPIs show total scan runs within a period. The time period is defaulted at last 30 days, you can also choose to select last 7 days. Based on the time filter selected, you can see the distribution of successful, failed, canceled, and in progress scan runs by week or by the day in the graph.
+1. The high-level KPIs show total scan runs within a period. The time period is defaulted at last 30 days, you can also choose to select last seven days. Based on the time filter selected, you can see the distribution of successful, failed, canceled, and in progress scan runs by week or by the day in the graph.
 
     :::image type="content" source="./media/how-to-monitor-scan-runs/monitor-scan-runs.png" alt-text="View scan runs over time"  lightbox="./media/how-to-monitor-scan-runs/monitor-scan-runs.png":::
 
-1. At the bottom of the graph, there is a **View more** link for you to explore further. The link opens the **Scan status** page. Here you can see a scan name and the number of times it has succeeded, failed, or been canceled in the time period. You can also filter the list by source types.
+1. At the bottom of the graph, there's a **View more** link for you to explore further. The link opens the **Scan status** page. Here you can see a scan name and the number of times it has succeeded, failed, or been canceled in the time period. You can also filter the list by source types.
 
     :::image type="content" source="./media/how-to-monitor-scan-runs/view-scan-status.png" alt-text="View scan status in details"  lightbox="./media/how-to-monitor-scan-runs/view-scan-status.png":::
 
@@ -39,7 +39,7 @@ You can navigate to scan run history for a given scan from different places:
 - Go to **Data map** -> **Sources** -> select the desired data source -> see **Scans**, **Recent scans** or **Recent failed scans**.
 - Go to **Data map** -> **Collections** -> select the desired collection -> **Scans** -> select the scan name that you want to view more.
 
-Click the **run ID** to check more about the scan run details:
+You can click the **run ID** to check more about the scan run details:
 
 :::image type="content" source="./media/how-to-monitor-scan-runs/monitor-scan-run-details.png" alt-text="View scan run execution details"  lightbox="./media/how-to-monitor-scan-runs/monitor-scan-run-details.png":::
 
@@ -55,34 +55,34 @@ Click the **run ID** to check more about the scan run details:
         | ----------- | ------------------------------------------------------------ |
         | Completed   | The scan phase succeeds.                                     |
         | Failed      | The scan phase fails. You can check the error details by clicking the "More info" link next to it. |
-        | Cancelled   | The scan run is cancelled by user.                           |
+        | Canceled    | The scan run is canceled by user.                           |
         | In Progress | The scan is running in progress.                             |
-        | Queued      | The scan run is waiting for available integration runtime resource.<br>If you use self-hosted integration runtime, note each self-hosted integration runtime node can run a number of concurrent scans at the same time depending on your machine specification (CPU and memory). More scans will be in Queued status. |
-        | Throttled   | The scan run is being throttled. It means this Purview account at the moment has more ongoing scan runs than the allowed max concurrent count. Learn more about the limit [here](how-to-manage-quotas.md). This particular scan run will be waiting and be executed once your other ongoing scan(s) finishes. |
+        | Queued      | The scan run is waiting for available integration runtime resource.<br>If you use self-hosted integration runtime, note each node can run a number of concurrent scans at the same time depending on your machine specification (CPU and memory). More scans will be in Queued status. |
+        | Throttled   | The scan run is being throttled. It means this Microsoft Purview account at the moment has more ongoing scan runs than the allowed max concurrent count. Learn more about the limit [here](how-to-manage-quotas.md). This particular scan run will be waiting and be executed once your other ongoing scan(s) finishes. |
 
     - **Scan type**: Manual or scheduled scan.
-    - **Assets discovered**: Number of assets that are discovered from the source. For both full and incremental scan, it includes all the assets being enumerated from the source under the configured scope, regardless of whether they are existing assets or newly created/updated assets since last scan run.
+    - **Assets discovered**: Number of assets that are discovered from the source. For both full and incremental scan, it includes all the assets being enumerated from the source under the configured scope, regardless of whether they're existing assets or newly created/updated assets since last scan run.
     - **Assets classified**: Number of assets that are used for classifying the data, regardless of whether the result has any matching classification or not. It's a subset of the discovered assets based on the [sampling mechanism](microsoft-purview-connector-overview.md#sampling-data-for-classification).
-    - **Duration**: The scan phase duration and its start/end time.
+    - **Duration**: The scan phase duration and the start/end time.
 
 - **Data ingestion** section summarizes the metrics for ingestion phase that Purview populates the data map with the identified metadata and lineage.
 
     - **Ingestion status**:
 
         | Status              | Description                                                  |
         | ------------------- | ------------------------------------------------------------ |
-        | Completed           | All of the assets and relationship are ingested into the data map successfully. |
-        | Partially completed | Partial of the assets and relationship are ingested into the data map successfully, while some fail. |
+        | Completed           | All of the assets and relationships are ingested into the data map successfully. |
+        | Partially completed | Partial of the assets and relationships are ingested into the data map successfully, while some fail. |
         | Failed              | The ingestion phase fails.                                   |
-        | Cancelled           | The scan run is cancelled by user, thus the ingestion is cancelled along. |
+        | Canceled            | The scan run is canceled by user, thus the ingestion is canceled along. |
         | In Progress         | The ingestion is running in progress.                        |
         | Queued              | The ingestion is waiting for available service resource or waiting for scan to discover metadata. |
 
-    - **Assets ingested**: Number of assets that are ingested into the data map. In case of full scan, the number is equal to the "assets discovered" count; for incremental scan, it only includes the newly created or updated assets, in which case less than the "assets discovered" count. When scanning file-based source, it is the raw assets count before resource set aggregation.
+    - **Assets ingested**: Number of assets that are ingested into the data map. For full scan, the number is equal to the "assets discovered" count; for incremental scan, it only includes the newly created or updated assets, in which case less than the "assets discovered" count. When scanning file-based source, it's the raw assets count before resource set aggregation.
 
-    - **Relationships ingested**: Number of relationship that are ingested into the data map. It includes static lineage and other relationship like foreign key relationship.
+    - **Relationships ingested**: Number of relationships that are ingested into the data map. It includes lineage and other relationships like foreign key relationships.
 
-    - **Duration**: The ingestion duration and its start/end time.
+    - **Duration**: The ingestion duration and the start/end time.
 
 ## Scans no longer run
 

articles/purview/includes/view-and-manage-scans.md

@@ -15,7 +15,7 @@ To view existing scans:
 1. Go to the [Microsoft Purview governance portal](https://web.purview.azure.com/resource/). Select the **Data map** tab on the left pane.
 1. Select the desired data source. You can view a list of existing scans on that data source under **Recent scans**, or you can view all scans on the **Scans** tab.
 1. Select the scan that has results you want to view. The page shows you all of the previous scan runs, along with the status and metrics for each scan run. 
-1. Click the **run ID** to check more about the [scan run details](how-to-monitor-scan-runs.md#scan-run-details).
+1. Click the **run ID** to check more about the [scan run details](../how-to-monitor-scan-runs.md#scan-run-details).
 
 ### Manage your scans - edit, delete, or cancel