Merge pull request #188494 from whhender/catalog-updates-2

Updating author, date, images, Acrolinx

Author: laurabren

articles/data-catalog/data-catalog-how-to-big-data.md

@@ -1,19 +1,19 @@
 ---
 title: How to catalog big data in Azure Data Catalog
 description: How-to article highlighting patterns for using Azure Data Catalog  with 'big data' data sources, including Azure Blob Storage, Azure Data Lake, and Hadoop HDFS.
-author: JasonWHowell
-ms.author: jasonh
+author: ChandraKavya
+ms.author: kchandra
 ms.service: data-catalog
 ms.topic: how-to
-ms.date: 08/01/2019
+ms.date: 02/14/2022
 ---
 # How to catalog big data in Azure Data Catalog
 
 [!INCLUDE [Azure Purview redirect](../../includes/data-catalog-use-purview.md)]
 
 ## Introduction
 
-**Microsoft Azure Data Catalog** is a fully managed cloud service that serves as a system of registration and system of discovery for enterprise data sources. It is all about helping people discover, understand, and use data sources, and helping organizations to get more value from their existing data sources, including big data.
+**Microsoft Azure Data Catalog** is a fully managed cloud service that serves as a system of registration and system of discovery for enterprise data sources. It's all about helping people discover, understand, and use data sources, and helping organizations to get more value from their existing data sources, including big data.
 
 **Azure Data Catalog** supports the registration of Azure Storage blobs and directories as well as Hadoop HDFS files and directories. The semi-structured nature of these data sources provides great flexibility. However, to get the most value from registering them with **Azure Data Catalog**, users must consider how the data sources are organized.
 
@@ -40,7 +40,7 @@ An example of this pattern might be:
 
 In this example, vehicle_maintenance_events and location_tracking_events represent logical data sets. Each of these folders contains data files that are organized by year and month into subfolders. Each of these folders could potentially contain hundreds or thousands of files.
 
-In this pattern, registering individual files with **Azure Data Catalog** probably does not make sense. Instead, register the directories that represent the data sets that be meaningful to the users working with the data.
+In this pattern, registering individual files with **Azure Data Catalog** probably doesn't make sense. Instead, register the directories that represent the data sets that be meaningful to the users working with the data.
 
 ## Reference data files
 
@@ -60,7 +60,7 @@ In this pattern, it makes sense to register the individual reference data files
 
 ## Alternate patterns
 
-The patterns described in the preceding section are just two possible ways a big data store may be organized, but each implementation is different. Regardless of how your data sources are structured, when registering big data sources with **Azure Data Catalog**, focus on registering the files and directories that represent the data sets that are of value to others within your organization. Registering all files and directories can clutter the catalog, making it harder for users to find what they need.
+The patterns described in the preceding sections are two possible ways a big data store may be organized, but each implementation is different. Regardless of how your data sources are structured, when registering big data sources with **Azure Data Catalog**, focus on registering the files and directories that represent the data sets that are of value to others within your organization. Registering all files and directories can clutter the catalog, making it harder for users to find what they need.
 
 ## Summary
 

articles/data-catalog/data-catalog-how-to-secure-catalog.md

@@ -1,11 +1,11 @@
 ---
 title: How to secure access to Azure Data Catalog
 description: This article explains how to secure a data catalog and its data assets in Azure Data Catalog.
-author: JasonWHowell
-ms.author: jasonh
+author: ChandraKavya
+ms.author: kchandra
 ms.service: data-catalog
 ms.topic: how-to
-ms.date: 08/01/2019
+ms.date: 02/14/2022
 ---
 # How to secure access to data catalog and data assets
 
@@ -20,43 +20,43 @@ Azure Data Catalog allows you to specify who can access the data catalog and wha
 
 To give a user or a group the access to a data catalog and set permissions:
 
-1. On the [home page of your data catalog](https://www.azuredatacatalog.com),  click **Settings** on the toolbar.
+1. On the [home page of your data catalog](https://www.azuredatacatalog.com),  select **Settings** on the toolbar.
 
-   ![Azure Data Catalog home page settings button](media/data-catalog-how-to-secure-catalog/data-catalog-settings.png)
+   :::image type="content" source="media/data-catalog-how-to-secure-catalog/data-catalog-settings.png" alt-text="Settings button in the toolbar highlighted.":::
 
 2. In the settings page, expand the **Catalog Users** section.
 
-   ![Azure Data Catalog users Add button](media/data-catalog-how-to-secure-catalog/data-catalog-add-button.png)
+   :::image type="content" source="media/data-catalog-how-to-secure-catalog/data-catalog-add-button.png" alt-text="Catalog Users section is expanded, and the Add button is selected.":::
 
-3. Click **Add**.
+3. Select **Add**.
 
-4. Enter the fully qualified **user name** or name of the **security group** in the Azure Active Directory (AAD) associated with the catalog. Use comma (`,’) as a separator if you are adding more than one user or group.
+4. Enter the fully qualified **user name** or name of the **security group** in the Microsoft Azure Active Directory (Azure AD) associated with the catalog. Use comma (`,’) as a separator if you're adding more than one user or group.
 
-   ![Azure Data Catalog users - users or groups](media/data-catalog-how-to-secure-catalog/data-catalog-users-groups.png)
+   :::image type="content" source="media/data-catalog-how-to-secure-catalog/data-catalog-users-groups.png" alt-text="Example user name and security groups added in the space, with a comma separating the two.":::
 
 5. Press **ENTER** or **TAB** out of the text box. 
 
 6. Confirm that all permissions (**Annotate**, **Register**, and **Take Ownership**) are assigned to these users or groups by default. That is, the user or group can [register data assets]( data-catalog-how-to-register.md), [annotate data assets]( data-catalog-how-to-annotate.md), and [take ownership of data assets]( data-catalog-how-to-manage.md). 
 
-   ![Azure Data Catalog users - default permissions](media/data-catalog-how-to-secure-catalog/data-catalog-default-permissions.png)
+   :::image type="content" source="media/data-catalog-how-to-secure-catalog/data-catalog-default-permissions.png" alt-text="All permissions have been selected for each user.":::
 
-7. To give a user or group only the read access to the catalog, clear the **annotate** option for that user or group. When you do so, the user or group cannot annotate data assets in the catalog but they can view them. 
+7. To give a user or group only the read access to the catalog, clear the **annotate** option for that user or group. Now the user or group can’t annotate data assets in the catalog, but they can view them. 
 
 8. To deny a user or group from registering data assets, clear the **register** option for that user or group.
 
 9. To deny a user from taking ownership of a data asset, clear the **take ownership** option for that user or group. 
 
-10. To delete a user/group from catalog users, click **x** for the user/group at the bottom of the list. 
+10. To delete a user/group from catalog users, select **x** for the user/group at the bottom of the list. 
 
-   ![Azure Data Catalog catalog users - delete user X icon](media/data-catalog-how-to-secure-catalog/data-catalog-delete-user.png)
+   :::image type="content" source="media/data-catalog-how-to-secure-catalog/data-catalog-delete-user.png" alt-text="Users are shown at the bottom of the permissions list, and the x button beside one of the users has been highlighted.":::
 
    > [!IMPORTANT]
    > We recommend that you add security groups to catalog users rather than adding users directly and assign permissions. Then, add users to the security groups that match their roles and their required access to the catalog.
 
 ## Special considerations
 
-- The permissions assigned to security groups are additive. Say, a user is in two groups. One group has annotate permissions and other group does not have annotate permissions. Then, user has annotate permissions. 
-- The permissions assigned explicitly to a user override the permissions assigned to groups to which the user belongs. In the previous example, say, you explicitly added the user to catalog users and do not assign annotate permissions. The user cannot annotate data assets even though the user is a member of a group that does have annotate permissions.
+- The permissions assigned to security groups are additive. For example: a user is in two groups. One group has annotate permissions and other group doesn't have annotate permissions. Then, the user has annotate permissions. 
+- The permissions assigned explicitly to a user override the permissions assigned to groups to which the user belongs. For example: A user is in a group that has annotate permissions. If you explicitly add the user to catalog users and don't assign annotate permissions, then the user can’t annotate data assets. The explicit permission on the user overrides the group permissions.
 
 ## Next steps