edit pass: purview-how-to

Author: ShawnJackson

articles/purview/how-to-create-import-export-glossary.md

@@ -23,7 +23,7 @@ To create a glossary term, follow these steps:
 
 2. On the **Glossary terms** page, select **+ New term**. 
 
-   A pane opens with the **System Default** template selected. Choose the template that you want to use to create a glossary term, and then select **Continue**.
+   A pane opens with the **System default** template selected. Choose the template that you want to use to create a glossary term, and then select **Continue**.
 
    :::image type="content" source="media/how-to-create-import-export-glossary/new-term-with-default-template.png" alt-text="Screenshot of the button and pane for creating a new term." border="true":::
 
@@ -61,7 +61,7 @@ To create a glossary term, follow these steps:
    | Redo | Redo changes that you made to the content. | Ctrl+Y | 
 
    > [!NOTE]
-   > Updating a definition with the rich text editor adds the attribute `microsoft_isDescriptionRichText": "true"` in the term payload. This attribute is not visible on the user experience and is automatically populated when you take any rich text action. The right text definition is populated in the following snippet of a term's JSON message:
+   > Updating a definition with the rich text editor adds the attribute `"microsoft_isDescriptionRichText": "true"` in the term payload. This attribute is not visible on the user experience and is automatically populated when you take any rich text action. The right text definition is populated in the following snippet of a term's JSON message:
    >
    >```json
    >   {
@@ -75,7 +75,7 @@ To create a glossary term, follow these steps:
 
    :::image type="content" source="media/how-to-create-import-export-glossary/overview-tab.png" alt-text="Screenshot of the status choices.":::
 
-   These status markers are metadata associated with the term. Currently, you can set the following status on each term:
+   Status markers are metadata associated with the term. Currently, you can set the following status on each term:
 
    - **Draft**: This term isn't yet officially implemented.
    - **Approved**: This term is officially approved.
@@ -87,7 +87,7 @@ To create a glossary term, follow these steps:
                                                                           
 6. Add **Resources** and **Acronym** information. If the term is part of a hierarchy, you can add parent terms at **Parent** on the **Overview** tab.
 
-7. Add **Synonyms** and **Related terms** information on the **Related** tab.
+7. Add **Synonyms** and **Related terms** information on the **Related** tab, and then select **Apply**.
 
    :::image type="content" source="media/how-to-create-import-export-glossary/related-tab.png" alt-text="Screenshot of tab for related terms and the box for adding synonyms." border="true":::
 
@@ -115,11 +115,11 @@ The Microsoft Purview data catalog provides a template .csv file for you to impo
    Give your template file a name that starts with a letter and includes only letters, numbers, spaces, an underscore (_), or other non-ASCII Unicode characters. Special characters in the file name will create an error.
 
    > [!Important]
-   > The system supports only importing columns that are available in the template. The **System Default** template will have all the default attributes.
+   > The system supports only importing columns that are available in the template. The **System default** template will have all the default attributes.
    >
    > Custom term templates define out-of-the box attributes and additional custom attributes. Therefore, the .csv file differs in the total number of columns and the column names, depending on the term template that you select. You can also review the file for problems after upload.
    >
-   > If you want to upload a file with a rich text definition, be sure to enter the definition with markup tags and populate the column **IsDefinitionRichText** to **true** in the .csv file.
+   > If you want to upload a file with a rich text definition, be sure to enter the definition with markup tags and populate the column `IsDefinitionRichText` to `true` in the .csv file.
 
    :::image type="content" source="media/how-to-create-import-export-glossary/select-file-for-import.png" alt-text="Screenshot of the button for downloading a sample template file.":::
 
@@ -141,7 +141,7 @@ Select **Export terms** to download the selected terms.
 :::image type="content" source="media/how-to-create-import-export-glossary/select-term-template-for-export.png" lightbox="media/how-to-create-import-export-glossary/select-term-template-for-export.png" alt-text="Screenshot of the button to export terms on the glossary terms page.":::
 
 > [!Important]
-> If the terms in a hierarchy belong to different term templates, you need to split them into different .csv files for import. Also, updating a parent of a term is currently not supported in the import process.
+> If the terms in a hierarchy belong to different term templates, you need to split them into different .csv files for import. Also, the import process currently doesn't support updating the parent of a term.
 
 ## Delete terms
 
@@ -171,11 +171,9 @@ Select **Export terms** to download the selected terms.
 1. The **Approval needed** column shows which terms require an approval process. If the value is **Yes**, the term will go through an approval workflow before deletion. If the value is **No**, the term will be deleted without any approvals.
 
    > [!NOTE]
-   > If a parent has an associated approval process but its child doesn't, the workflow for deleting the parent term will be triggered. This is because the selection is done on the parent, and you're acknowledging to delete child terms along with parent.
+   > If a parent has an associated approval process but its child doesn't, the workflow for deleting the parent term will be triggered. This is because the selection is done on the parent, and you're acknowledging the deletion of child terms along with parent.
 
-   :::image type="content" source="media/how-to-create-import-export-glossary/approval-needed.png" alt-text="Screenshot of the window for deleting glossary terms, with the column that shows which terms need approval to be deleted." border="true":::
-
-1. If at least one term needs to be approved, **Submit for approval** and **Cancel** buttons appear. Selecting **Submit for approval** will delete all the terms where approval isn't needed and will trigger approval workflows for terms that require it.
+   If at least one term needs to be approved, **Submit for approval** and **Cancel** buttons appear. Selecting **Submit for approval** will delete all the terms where approval isn't needed and will trigger approval workflows for terms that require it.
 
    :::image type="content" source="media/how-to-create-import-export-glossary/yes-approval-needed.png" alt-text="Screenshot of the window for deleting glossary terms, which shows terms that need approval and includes the button for submitting them for approval." border="true":::
 

articles/purview/how-to-workflow-self-service-data-access-hybrid.md

@@ -24,10 +24,10 @@ The data analyst notices that one of the Azure Data Lake Storage Gen2 accounts s
 
 You can create these workflows for any of your resources across your data estate to automate the access request process. Workflows are assigned at the [collection](reference-azure-purview-glossary.md#collection) level, so they automate business processes along the same organizational lines as your permissions.
 
-This guide will show you how to create and manage self-service access workflows in Microsoft Purview.
+This guide shows you how to create and manage self-service access workflows in Microsoft Purview.
 
 >[!NOTE]
-> To create or edit a workflow, you'll need the [workflow admin role](catalog-permissions.md) in Microsoft Purview. You can also contact the workflow admin in your collection, or reach out to your collection administrator, for permissions.
+> To create or edit a workflow, you need the [workflow admin role](catalog-permissions.md) in Microsoft Purview. You can also contact the workflow admin in your collection, or reach out to your collection administrator, for permissions.
 
 ## Create and enable the self-service access workflow
 
@@ -69,14 +69,14 @@ This guide will show you how to create and manage self-service access workflows
    Assign data owners as approvers. Using the dynamic variable **Asset.Owner** as approvers in the approval connector will send approval requests to the data owners on the entity. 
 
     >[!Note]
-    > Because entities might not have the data owner field populated, using the **Asset.Owner** variable might result in errors if no data owner is found. 
+    > Using the **Asset.Owner** variable might result in errors if an entity doesn't have a data owner. 
     
 1. If the condition to check approval status is approved, take the following steps: 
 
     * If a data source is registered for [data use management](how-to-enable-data-use-governance.md) with the policy:
        1. Create a [self-service policy](concept-self-service-data-access-policy.md). 
        1. Send email to the requestor that confirms access. 
-    * If a data source isn't registered with policy:
+    * If a data source isn't registered with the policy:
        1. Use a connector to assign [a task](how-to-workflow-manage-requests-approvals.md#tasks) to a user or an Azure Active Directory (Azure AD) group to manually provide access to the requestor. 
        1. Send an email to requestor to explain that access is provided after the task is marked as complete. 
 
@@ -109,23 +109,24 @@ This guide will show you how to create and manage self-service access workflows
 1. Make sure that the **Enable** toggle is on. The workflow should be enabled by default.
 1. Select **Save and close** to create and enable the workflow.
 
+   Your new workflow now appears in the list of workflows.
+
     :::image type="content" source="./media/how-to-workflow-self-service-data-access-hybrid/completed-workflows.png" alt-text="Screenshot that shows the workflow authoring page with the newly created workflow listed among the other workflows.":::
 
 ## Edit an existing workflow
 
-To modify an existing workflow, select the workflow and then select the **Edit** button. You're presented with the canvas that contains the workflow definition. Modify the workflow and select **Save** to commit the changes.
+To modify an existing workflow, select the workflow and then select the **Edit** button. You're presented with the canvas that contains the workflow definition. Modify the workflow and then select **Save** to commit the changes.
 
 :::image type="content" source="./media/how-to-workflow-self-service-data-access-hybrid/select-edit.png" alt-text="Screenshot that shows the workflow authoring page, with the Edit button highlighted on the top menu.":::
 
 ## Disable a workflow
 
-To disable a workflow, you can use either of these methods:
-
-- Select the workflow, and then select **Disable**.
-- Select the workflow, select **Edit**, turn off the **Enable** toggle in the workflow canvas, and then select **Save and close**.
+To disable a workflow, select the workflow and then select **Disable**.
 
 :::image type="content" source="./media/how-to-workflow-self-service-data-access-hybrid/select-disable.png" alt-text="Screenshot that shows the workflow authoring page, with the Disable button highlighted on the top menu.":::
 
+Another way is to select the workflow, select **Edit**, turn off the **Enable** toggle in the workflow canvas, and then select **Save and close**.
+
 ## Delete a workflow
 
 To delete a workflow, select the workflow and then select **Delete**.