Acrolinx

Author: whhender

articles/purview/concept-insights.md

@@ -22,32 +22,32 @@ Data Estate Insights are one of the key pillars of Microsoft Purview. The featur
 
 This report gives a bird's eye view of your data estate, and its distribution by source type, by classification and by file size as some of the dimensions. This report caters to different types of stakeholder in the data governance and cataloging roles, who are interested to know state of their DataMap, by classification and file extensions.
 
-The report provides broad insights through graphs and KPIs and later deep dive into specific anomalies such as misplaced files. The report also supports an end-to-end customer experience, where customer can view count of assets with a specific classification, can breakdown the information by source types and top folders, and can also view the list of assets for further investigation.
+The report provides broad insights through graphs and KPIs and later deep dive into specific anomalies such as misplaced files. The report also supports an end-to-end customer experience, where customer can view count of assets with a specific classification, can break down the information by source types and top folders, and can also view the list of assets for further investigation.
 
 > [!NOTE]
-> File Extension Insights has been merged into Asset Insights with richer trend report showing growth in data size by file extension. Learn more by exploring [Asset Insights](asset-insights.md) 
+> File Extension Insights has been merged into Asset Insights with richer trend report showing growth in data size by file extension. Learn more by exploring [Asset Insights](asset-insights.md).
 
 ## Glossary Insights
 
-This report gives the Data Stewards a status report on glossary. Data Stewards can view this report to understand distribution of glossary terms by status, learn how many glossary terms are attached to assets and how many are not yet attached to any asset. Business users can also learn about completeness of their glossary terms. 
+This report gives the Data Stewards a status report on glossary. Data Stewards can view this report to understand distribution of glossary terms by status, learn how many glossary terms are attached to assets and how many aren't yet attached to any asset. Business users can also learn about completeness of their glossary terms.
 
-This report summarizes top items that a Data Steward needs to focus on, to create a complete and usable glossary for his/her organization. Stewards can also navigate into the "Glossary" experience from "Glossary Insights" experience, to make changes on a specific glossary term.
+This report summarizes top items that a Data Steward needs to focus on, to create a complete and usable glossary for their organization. Stewards can also navigate into the "Glossary" experience from "Glossary Insights" experience, to make changes on a specific glossary term.
 
 ## Classification Insights
 
 This report provides details about where classified data is located, the classifications found during a scan, and a drill-down to the classified files themselves. It enables Stewards, Curators and Security Administrators to understand the types of information found in their organization's data estate. 
 
 In Microsoft Purview, classifications are similar to subject tags, and are used to mark and identify content of a specific type in your data estate.
 
-Use the Classification Insights report to identify content with specific classifications and understand required actions, such as adding additional security to the repositories, or moving content to a more secure location.
+Use the Classification Insights report to identify content with specific classifications and understand required actions, such as adding more security to the repositories, or moving content to a more secure location.
 
 For more information, see [Classification insights about your data from Microsoft Purview](classification-insights.md).
 
 ## Sensitivity Labeling Insights
 
-This report provides details about the sensitivity labels found during a scan, as well as a drill-down to the labeled files themselves. It enables security administrators to ensure the security of information found in their organization's data estate. 
+This report provides details about the sensitivity labels found during a scan, and a drill-down to the labeled files themselves. It enables security administrators to ensure the security of information found in their organization's data estate. 
 
-In Microsoft Purview, sensitivity labels are used to identify classification type categories, as well as the group security policies that you want to apply to each category.
+In Microsoft Purview, sensitivity labels are used to identify classification type categories, and the group security policies that you want to apply to each category.
 
 Use the Labeling Insights report to identify the sensitivity labels found in your content and understand required actions, such as managing access to specific repositories or files.
 

articles/purview/register-scan-amazon-rds.md

@@ -29,9 +29,9 @@ For this service, use Microsoft Purview to provide a Microsoft account with secu
 
 - **Supported database engines**: Amazon RDS structured data storage supports multiple database engines. Microsoft Purview supports Amazon RDS with/based on Microsoft SQL and PostgreSQL.
 
-- **Maximum columns supported**: Scanning RDS tables with more than 300 columns is not supported.
+- **Maximum columns supported**: Scanning RDS tables with more than 300 columns isn't supported.
 
-- **Public access support**: Microsoft Purview supports scanning only with VPC Private Link in AWS, and does not include public access scanning.
+- **Public access support**: Microsoft Purview supports scanning only with VPC Private Link in AWS, and doesn't include public access scanning.
 
 - **Supported regions**: Microsoft Purview only supports Amazon RDS databases that are located in the following AWS regions:
 
@@ -49,7 +49,7 @@ For this service, use Microsoft Purview to provide a Microsoft account with secu
 
 - **IP address requirements**: Your RDS database must have a static IP address. The static IP address is used to configure AWS PrivateLink, as described in this article.
 
-- **Known issues**: The following functionality is not currently supported:
+- **Known issues**: The following functionality isn't currently supported:
 
     - The **Test connection** button. The scan status messages will indicate any errors related to connection setup.
     - Selecting specific tables in your database to scan.
@@ -139,7 +139,7 @@ This CloudFormation template is available for download from the [Azure GitHub re
 
     Define your settings as needed for your environment. For more information, select the **Learn more** links to access the AWS documentation. When you're done, select **Next** to continue.
 
-1. On the **Review** page, check to make sure that the values you selected are correct for your environment. Make any changes needed, and then select **Create stack** when you're done.
+1. On the **Review** page, check to make sure that the values you selected are correct for your environment. Make any changes needed and then select **Create stack** when you're done.
 
 1. Watch for the resources to be created. When complete, relevant data for this procedure is shown on the following tabs:
 
@@ -151,7 +151,7 @@ This CloudFormation template is available for download from the [Azure GitHub re
 
 1. In the **Outputs** tab, copy the **ServiceName** key value to the clipboard.
 
-    You'll use the value of the **ServiceName** key in the Microsoft Purview portal, when [registering your RDS database](#register-an-amazon-rds-data-source) as Microsoft Purview data source. There, enter the **ServiceName** key in the **Connect to private network via endpoint service** field.
+    You'll use the value of the **ServiceName** key in the Microsoft Purview governance portal, when [registering your RDS database](#register-an-amazon-rds-data-source) as Microsoft Purview data source. There, enter the **ServiceName** key in the **Connect to private network via endpoint service** field.
 
 ## Register an Amazon RDS data source
 
@@ -469,7 +469,7 @@ After the [Load Balancer is created](#step-4-create-a-load-balancer) and its Sta
 
 <a name="service-name"></a>**To copy the service name for use in Microsoft Purview**:
 
-After you’ve created your endpoint service, you can copy the **Service name** value in the Microsoft Purview portal, when [registering your RDS database](#register-an-amazon-rds-data-source) as Microsoft Purview data source.
+After you’ve created your endpoint service, you can copy the **Service name** value in the Microsoft Purview governance portal, when [registering your RDS database](#register-an-amazon-rds-data-source) as Microsoft Purview data source.
 
 Locate the **Service name** on the **Details** tab for your selected endpoint service.
 

articles/purview/register-scan-amazon-s3.md

@@ -36,7 +36,7 @@ For this service, use Microsoft Purview to provide a Microsoft account with secu
 
 ## Microsoft Purview scope for Amazon S3
 
-We currently do not support ingestion private endpoints that work with your AWS sources.
+We currently don't support ingestion private endpoints that work with your AWS sources.
 
 For more information about Microsoft Purview limits, see:
 
@@ -45,7 +45,7 @@ For more information about Microsoft Purview limits, see:
 
 ### Storage and scanning regions
 
-The Microsoft Purview connector for the Amazon S3 service is currently deployed in specific regions only. The following table maps the regions where you data is stored to the region where it would be scanned by Microsoft Purview.
+The Microsoft Purview connector for the Amazon S3 service is currently deployed in specific regions only. The following table maps the regions where your data is stored to the region where it would be scanned by Microsoft Purview.
 
 > [!IMPORTANT]
 > Customers will be charged for all related data transfer charges according to the region of their bucket.
@@ -167,7 +167,7 @@ This procedure describes how to create the AWS role, with the required Microsoft
 
 - For buckets that use **AWS-KMS** encryption, [special configuration](#configure-scanning-for-encrypted-amazon-s3-buckets) is required to enable scanning.
 
-- Make sure that your bucket policy does not block the connection. For more information, see:
+- Make sure that your bucket policy doesn't block the connection. For more information, see:
 
     - [Confirm your bucket policy access](#confirm-your-bucket-policy-access)
     - [Confirm your SCP policy access](#confirm-your-scp-policy-access)
@@ -189,7 +189,7 @@ This procedure describes how to create a new Microsoft Purview credential to use
     |Field |Description  |
     |---------|---------|
     |**Name**     |Enter a meaningful name for this credential.        |
-    |**Description**     |Enter a optional description for this credential, such as `Used to scan the tutorial S3 buckets`         |
+    |**Description**     |Enter an optional description for this credential, such as `Used to scan the tutorial S3 buckets`         |
     |**Authentication method**     |Select **Role ARN**, since you're using a role ARN to access your bucket.         |
     |**Role ARN**     | Once you've [created your Amazon IAM role](#create-a-new-aws-role-for-microsoft-purview), navigate to your role in the AWS IAM area, copy the **Role ARN** value, and enter it here. For example: `arn:aws:iam::181328463391:role/S3Role`. <br><br>For more information, see [Retrieve your new Role ARN](#retrieve-your-new-role-arn). |
     | | |
@@ -262,14 +262,14 @@ AWS buckets support multiple encryption types. For buckets that use **AWS-KMS**
 
 ### Confirm your bucket policy access
 
-Make sure that the S3 bucket [policy](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-iam-policies.html) does not block the connection:
+Make sure that the S3 bucket [policy](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-iam-policies.html) doesn't block the connection:
 
 1. In AWS, navigate to your S3 bucket, and then select the **Permissions** tab > **Bucket policy**.
 1. Check the policy details to make sure that it doesn't block the connection from the Microsoft Purview scanner service.
 
 ### Confirm your SCP policy access
 
-Make sure that there is no [SCP policy](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) that blocks the connection to the S3 bucket. 
+Make sure that there's no [SCP policy](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) that blocks the connection to the S3 bucket. 
 
 For example, your SCP policy might block read API calls to the [AWS Region](#storage-and-scanning-regions) where your S3 bucket is hosted.
 
@@ -332,7 +332,7 @@ For example:
 
 ## Add a single Amazon S3 bucket as a Microsoft Purview account
 
-Use this procedure if you only have a single S3 bucket that you want to register to Microsoft Purview as a data source, or if you have multiple buckets in your AWS account, but do not want to register all of them to Microsoft Purview.
+Use this procedure if you only have a single S3 bucket that you want to register to Microsoft Purview as a data source, or if you have multiple buckets in your AWS account, but don't want to register all of them to Microsoft Purview.
 
 **To add your bucket**:
 
@@ -460,7 +460,7 @@ Use the other areas of Microsoft Purview to find out details about the content i
 
 - **View Insight reports** to view statistics for the classification, sensitivity labels, file types, and more details about your content.
 
-    All Microsoft Purview Insight reports include the Amazon S3 scanning results, along with the rest of the results from your Azure data sources. When relevant, an additional **Amazon S3** asset type was added to the report filtering options.
+    All Microsoft Purview Insight reports include the Amazon S3 scanning results, along with the rest of the results from your Azure data sources. When relevant, another **Amazon S3** asset type was added to the report filtering options.
 
     For more information, see the [Understand Data Estate Insights in Microsoft Purview](concept-insights.md).
 
@@ -581,9 +581,9 @@ This is a general error that indicates an issue when using the Role ARN. For exa
 
 - Make sure that the AWS role has the correct Microsoft account ID. In the AWS IAM area, select the **Role > Trust relationships** tab and then follow the steps in [Create a new AWS role for Microsoft Purview](#create-a-new-aws-role-for-microsoft-purview) again to verify your details.
 
-For more information, see [Cannot find the specified bucket](#cannot-find-the-specified-bucket), 
+For more information, see [Can't find the specified bucket](#cannot-find-the-specified-bucket), 
 
-### Cannot find the specified bucket
+### Can't find the specified bucket
 
 Make sure that the S3 bucket URL is properly defined: