Resolving image naming convention

Author: whhender

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/2-exercise-deploy-configure-environment.md

@@ -25,7 +25,7 @@ You'll need to bring your own Microsoft Purview instance to the learning module,
 
 1. On the new Create Microsoft Purview account page under the **Basics** tab, select your Azure subscription, resource group, enter a name, and choose a location.
 
-    :::image type="content" source="../media/Create-Purview-Account-Azure-Portal.png" alt-text="Screenshot of the Create Microsoft Purview account page in the Azure portal.":::
+    :::image type="content" source="../media/create-microsoft-purview-account-azure-portal.png" alt-text="Screenshot of the Create Microsoft Purview account page in the Azure portal.":::
 
     >[!TIP]
     > The list shows only locations that support the Microsoft Purview governance portal. The location you choose will be the region where your Microsoft Purview account and metadata will be stored. Sources can be housed in other regions.
@@ -100,7 +100,7 @@ To create a CluedIn instance, go to the Azure portal and follow the steps below:
 
 1. This will take you to a form where you'll be asked to choose the type of plan. CluedIn provides a seven-day trial that is cost-free from CluedIn, but will charge for the underlying Azure infrastructure used to install within your environment. You can also choose the **CluedIn Platform** plan that is hourly based pricing. In this module, we'll walk you through using the CluedIn seven-day trial.
 
-    :::image type="content" source="../media/Choose_CluedIn_Instance.png" alt-text="Screenshot of CluedIn Master Data Management Page, showing the CluedIn Platform option.":::
+    :::image type="content" source="../media/choose-cluedin-instance.png" alt-text="Screenshot of CluedIn Master Data Management Page, showing the CluedIn Platform option.":::
 
 1. Choose **Trial Version** from the dropdown and select **Create**.
 
@@ -109,18 +109,18 @@ To create a CluedIn instance, go to the Azure portal and follow the steps below:
     >[!NOTE]
     >The Managed Resource Group name is autogenerated for you, there is no need to rename this. Call your Installation Name something that will be easy for you to remember through the rest of the module.
 
-    :::image type="content" source="../media/Fill_CluedIn_Trial_Forn.png" alt-text="Screenshot of CluedIn Master Data Management Page creation form, showing some generic options.":::
+    :::image type="content" source="../media/fill-cluedin-trial-form.png" alt-text="Screenshot of CluedIn Master Data Management Page creation form, showing some generic options.":::
 
 1. Select **Next : CluedIn - Organization Setup >** to set the Organization Name, Administrator Email Address, CluedIn Administrator Password, and Confirm Password. The Organization Name will be the name for your new instance of CluedIn and the subdomain that will be used to access your CluedIn Studio in the browser. Provide an email address that is valid and that you have access to, and provide a strong Password in the CluedIn Administration Password and Confirm password fields.
 
-    :::image type="content" source="../media/Fill_CluedIn_Organization_Details.png" alt-text="Screenshot of CluedIn Master Data Management Page organization setup page.":::
+    :::image type="content" source="../media/fill-cluedin-organization-details.png" alt-text="Screenshot of CluedIn Master Data Management Page organization setup page.":::
 
     >[!NOTE]
     >If you are required to use Single Sign On for your Learning Module then you will need to use the "CluedIn Platform" plan. The Trial does not support SSO setup and uses simple OAuth 2 / JWT authentication.
 
 1. Select **Next : CluedIn - AKS Setup >** and leave all of the values as the default.
 
-    :::image type="content" source="../media/Fill_CluedIn_AKS_Setup.png" alt-text="Screenshot of CluedIn Master Data Management Page AKS setup page.":::
+    :::image type="content" source="../media/fill-cluedin-aks-setup.png" alt-text="Screenshot of CluedIn Master Data Management Page AKS setup page.":::
 
 1. Select **Next : Review + create >**. On this next page, you'll need to check the checkbox to agree to the terms and conditions.
 

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/4-integrate-deployed-technologies.md

@@ -76,7 +76,7 @@ Once again, if we look at Lorain, we can see that this time her email ends with
 1. Navigate to your Container Storage in the left menu, and either select an existing Container, or create a new one called **cluedintrial**.
 1. Inside the cluedintrial container, create a new directory called **raw** upload the downloaded files one at a time to the container using the **Upload** button.
 
-    :::image type="content" source="../media/Upload_Data_To_Storage_Account.png" alt-text="Screenshot of the sample data being uploaded in ADLS Gen2":::
+    :::image type="content" source="../media/upload-data-to-storage-account.png" alt-text="Screenshot of the sample data being uploaded in ADLS Gen2":::
 
 1. Ones all your files are uploaded, navigate to **Security + networking > Networking** in your ADLS Gen2 account.
 1. Choose **Enabled from selected virtual networks** under **Public network access**.

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/6-stream-data.md

@@ -14,11 +14,11 @@ So let's set up our stream of data back into an ADLS Gen2 folder called **master
 
 1. In CluedIn, navigate to your Export Targets, under the **Consume** menu, and select **Add Export Target** and choose the Azure Data Lake Connector.
 
-    :::image type="content" source="../media/Export_Target_Data_Lake.png" alt-text="Screenshot of the CluedIn Consume window, showing the Azure Data Lake Connector selected.":::
+    :::image type="content" source="../media/export-target-data-lake.png" alt-text="Screenshot of the CluedIn Consume window, showing the Azure Data Lake Connector selected.":::
 
 1. Enter the account details, including the storage account key you copied earlier. The **FileSystemName** will be your container name. You can use an existing container, or enter a new name here and CluedIn will create it for your. For **DirectoryName**, enter **mastered**.
 
-    :::image type="content" source="../media/Export_Target_Details.png" alt-text="Screenshot of the CluedIn Consume window, showing the Azure Data Lake details added.":::
+    :::image type="content" source="../media/export-target-details.png" alt-text="Screenshot of the CluedIn Consume window, showing the Azure Data Lake details added.":::
 
 1. After you've entered your connection information, select **Test Connection**. If you get a green light, you can move on! If not, check these values:
     - Confirm that your container name has no capital characters, special characters, or spaces. (These are limitations on the ADLS Gen2 side).
@@ -27,7 +27,7 @@ So let's set up our stream of data back into an ADLS Gen2 folder called **master
 
 1. Select **Streams** in the Left-Hand Menu of CluedIn and Create a New Stream called **Employees**.
 
-    :::image type="content" source="../media/Employee_Stream.png" alt-text="Screenshot of the CluedIn Create Stream window, with the Stream Name entered as Employees.":::
+    :::image type="content" source="../media/employee-stream.png" alt-text="Screenshot of the CluedIn Create Stream window, with the Stream Name entered as Employees.":::
 
     A Stream in CluedIn allows an end user to set up a push-based delivery of data to a target.
 
@@ -37,12 +37,12 @@ So let's set up our stream of data back into an ADLS Gen2 folder called **master
 
 1. In the value for the Entity Type, choose **Employee** and save.
 
-    :::image type="content" source="../media/Stream_Filter.png" alt-text="Screenshot of the CluedIn stream configuration window, showing the value selector.":::
+    :::image type="content" source="../media/stream-filter.png" alt-text="Screenshot of the CluedIn stream configuration window, showing the value selector.":::
 
 1. In the **Export Target** tab, choose the Azure Data Lake Connector that you just added. Select **Next**.
 1. Add **mastered** as the Target Name. This points the data stream to the folder you created in the first step.
 
-    :::image type="content" source="../media/Choose_Target.png" alt-text="Screenshot of the CluedIn stream Export Target Configuration window, showing the ADLS Gen 2 account selected.":::
+    :::image type="content" source="../media/choose-target.png" alt-text="Screenshot of the CluedIn stream Export Target Configuration window, showing the ADLS Gen 2 account selected.":::
 
 1. For the mode of the stream, choose **Synchronization**.
 
@@ -56,7 +56,7 @@ So let's set up our stream of data back into an ADLS Gen2 folder called **master
     >[!NOTE]
     > You can look at the Data Tab to get a preview of the exact data that will be shared downstream.
 
-    :::image type="content" source="../media/Stream_Setup.png" alt-text="Screenshot of the CluedIn stream Export Target Configuration window, showing the Add Property drop-down menu.":::
+    :::image type="content" source="../media/stream-setup.png" alt-text="Screenshot of the CluedIn stream Export Target Configuration window, showing the Add Property drop-down menu.":::
 
 1. Toggle the **Inactive** button and your stream will be activated.
 

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/7-explore-the-results.md

@@ -2,7 +2,7 @@ With your data now mapped into the CluedIn platform and streaming to ADLS Gen 2,
 
 1. In the search bar up the top of the Studio, search for **Lorain**. CluedIn will provide some autosuggested search results, but you can select the search button or press enter to see the results.
 
-    :::image type="content" source="../media/Auto_Search.png" alt-text="Screenshot of CluedIn showing a search for Lorain in the top search bar.":::
+    :::image type="content" source="../media/auto-search.png" alt-text="Screenshot of CluedIn showing a search for Lorain in the top search bar.":::
 
 1. If you mapped the data like in the previous exercise then you should see one result for Lorain. If you see more than this, please revisit the last part of the exercise as you may be missing an identifier mapped. Most importantly, we don't see three Lorain records from across the three input files, but rather one single record of Lorain. 
 

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/8-exercise-fix-duplicate-records.md

@@ -14,7 +14,7 @@ So far in the exercise, we have found that most our records were able to actuall
 
 1. In the left hand side menu of CluedIn, select **Management** -> **Deduplication**.
 
-    :::image type="content" source="../media/Deduplication_Menu.png" alt-text="Screenshot of CluedIn duplicate management dashboard.":::
+    :::image type="content" source="../media/deduplication-menu.png" alt-text="Screenshot of CluedIn duplicate management dashboard.":::
 
 1. Create a new deduplication project called **Products** and select the Entity Type of **Product**.
 
@@ -24,13 +24,13 @@ So far in the exercise, we have found that most our records were able to actuall
 
 1. Under the tab called **Matching Rules**, create a new rule called **Match on Name**.
 
-    :::image type="content" source="../media/Match_On_Name.png" alt-text="Screenshot of the Add Matching Rule page.":::
+    :::image type="content" source="../media/match-on-name.png" alt-text="Screenshot of the Add Matching Rule page.":::
 
 1. When prompted to provide input, choose the radio button for **Property** to choose the name of the record.
 
 1. It will ask you to choose a comparator, in which we can keep it simple for now and use the Equals comparator.
 
-    :::image type="content" source="../media/Simple_Matching_Rule.png" alt-text="Screenshot showing the Equals comparator showing in the matching function.":::
+    :::image type="content" source="../media/simple-matching-rule.png" alt-text="Screenshot showing the Equals comparator showing in the matching function.":::
 
 1. Complete the project creator and then select **Generate Results** on the page.
 

learn-pr/azure/building-end-to-end-data-governance-master-data-stack-with-microsoft-purview-cluedin/includes/9-exercise-validate-microsoft-purview-scan.md

@@ -12,4 +12,4 @@ Because we only ran our scan in Microsoft Purview once, let's run it again.
 
 1. Select the **Employees.csv** file first, and select the **Lineage**. Here we can see that Employees.csv was mapped into an entity type called Employee and that it was also exported out to the same container that it came from in a folder called mastered.
 
-:::image type="content" source="../media/Purview_Employees.png" alt-text="Screenshot of the lineage page for Employees.csv in Microsoft Purview.":::
+:::image type="content" source="../media/purview-employees.png" alt-text="Screenshot of the lineage page for Employees.csv in Microsoft Purview.":::