Merge pull request #17663 from john-par/1783001-fix-validation-suggestion-10-22

Message fixes: Bulk update fixed duplicated alt-text validation issues 10-22

Author: v-shils

docs/analytics-platform-system/import-the-scom-management-pack-for-pdw.md

@@ -45,7 +45,7 @@ The management packs must be installed. See [Install the SCOM Management Packs &
 
 7.  Click **Install**.  
 
-    ![Click Install](./media/import-the-scom-management-pack-for-pdw/SCOM_IMP5.png "SCOM_IMP5")  
+    ![Screenshot showing the Import Management Packs wizard on the Select Management Packs step with the Install option circled in red.](./media/import-the-scom-management-pack-for-pdw/SCOM_IMP5.png "SCOM_IMP5")  
 
 8.  Once Complete, click **Close**.  
 
@@ -65,7 +65,7 @@ The management packs must be installed. See [Install the SCOM Management Packs &
 
 4.  Click **Install**.  
 
-    ![Click Install](./media/import-the-scom-management-pack-for-pdw/SCOM_PDW3.png "SCOM_PDW3")  
+    ![Another screenshot of the Import Management Packs wizard on the Select Management Packs step with the Install option circled in red.](./media/import-the-scom-management-pack-for-pdw/SCOM_PDW3.png "SCOM_PDW3")  
 
 5.  Click **Close**.  
 

docs/analytics-platform-system/install-the-scom-management-packs.md

@@ -44,7 +44,7 @@ For older versions of PDW without APS, download the[System Center Monitoring Pac
 
 4.  Click **Install**.  
 
-    ![Confirm installation](./media/install-the-scom-management-packs/SCOM_licnse_agrmt3.png "SCOM_licnse_agrmt3")  
+    ![Screenshot of the SQL Server Appliance Base Monitoring MP Installer wizard on the Confirm Installation step with the Install option circled in red.](./media/install-the-scom-management-packs/SCOM_licnse_agrmt3.png "SCOM_licnse_agrmt3")  
 
 5.  Click **Close**.  
 
@@ -64,7 +64,7 @@ For older versions of PDW without APS, download the[System Center Monitoring Pac
 
 4.  Click **Install**.  
 
-    ![Confirm installation](./media/install-the-scom-management-packs/SCOM_licnse_agmtB2.png "SCOM_licnse_agmtB2")  
+    ![Screenshot of the PDWMP Installer wizard on the Confirm Installation step with the Install option circled in red.](./media/install-the-scom-management-packs/SCOM_licnse_agmtB2.png "SCOM_licnse_agmtB2")  
 
 5.  Click **Close**.  
 

docs/big-data-cluster/data-virtualization-csv.md

@@ -66,15 +66,15 @@ Click **Next**.
 
 Azure Data Studio provides a preview of the imported data.
 
-![External Data Source credentials](media/data-virtualization/130-csv-preview-data.png)
+![Screenshot showing the Create External Table From CSV window with a preview of imported data.](media/data-virtualization/130-csv-preview-data.png)
 
 Once done viewing the preview, click **Next** to continue
 
 ## Modify Columns
 
 In the next window, you may modify the columns of the external table you intend to create. You are able to alter the column name, change the data type and allow for nullable rows. 
 
-![External Data Source credentials](media/data-virtualization/140-csv-modify-columns.png)
+![Screenshot of the Create External Table From CSV window showing Step 3 Modify Columns.](media/data-virtualization/140-csv-modify-columns.png)
 
 After you verify the destination columns, click **Next**.
 

docs/dma/dma-assess-sql-data-estate-to-sqldb.md

@@ -126,11 +126,11 @@ After you successfully create a migration project, under **Assessment tools**, i
 
 5. After the assessment completes, select **Upload to Azure Migrate**.
 
-   ![Azure Migrate - Data Migration Assistant - review results screen](../dma/media//dma-assess-sql-data-estate-to-sqldb/dms-dma-review-results-screen.png)
+   ![Screenshot showing the Data Migration Assistant with the Upload to Azure Migrate option called out.](../dma/media//dma-assess-sql-data-estate-to-sqldb/dms-dma-review-results-screen.png)
 
 6. Sign in to the Azure portal.
 
-   ![Azure Migrate - Data Migration Assistant - review results screen](../dma/media//dma-assess-sql-data-estate-to-sqldb/dms-azure-migrate-portal-signin.png)
+   ![Screenshot of the Data Migration Assistant showing the Azure portal sign in window.](../dma/media//dma-assess-sql-data-estate-to-sqldb/dms-azure-migrate-portal-signin.png)
 
 7. Select the subscription and Azure Migrate project into which you want to upload the assessment results, and then select **Upload**.
 

docs/dma/dma-consolidatereports.md

@@ -91,7 +91,7 @@ Create a database called **EstateInventory** and a table called **DatabaseInvent
 - DatabaseName
 - AssessmentFlag
 
-![SQL Server table contents](../dma/media//dma-consolidatereports/dma-sql-server-table-contents-database-inventory.png)
+![Screenshot of a SQL Server table contents if you're using a SQL Server table.](../dma/media//dma-consolidatereports/dma-sql-server-table-contents-database-inventory.png)
 
 If this database isn't on the tools computer, ensure that the tools computer has network connectivity to this SQL Server instance.
 
@@ -108,7 +108,7 @@ Create a database called **EstateInventory** and a table called **InstanceInvent
 - Port
 - AssessmentFlag
 
-![SQL Server table contents](../dma/media//dma-consolidatereports/dma-sql-server-table-contents-instance-inventory.png)
+![Screenshot of a SQL Server table contents if using an Instance Inventory.](../dma/media//dma-consolidatereports/dma-sql-server-table-contents-instance-inventory.png)
 
 ## Running a scaled assessment
 

docs/integration-services/change-data-capture/known-issues-resolutions-with-cdc-for-oracle-attunity.md

@@ -101,27 +101,27 @@ You can query the trace table in the CDC database within SQL Server to see logge
 
 To capture diagnostics, select **Collect Diagnostics** on the status tab in the Oracle Change Data Capture management console. 
 
-![Collect diagnostics link](media/known-issues-resolutions-with-cdc-for-oracle-attunity/collect-diagnostics.png)
+![Screenshot showing the Status tab in the Oracle Change Data Capture management console with the Collect Diagnostics option called out.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/collect-diagnostics.png)
 
 Choose a start time and select a location for the log file. Then select **Create** to start the diagnostics collection. 
 
-![Collect diagnostics link](media/known-issues-resolutions-with-cdc-for-oracle-attunity/start-diagnostics.png)
+![Screenshot of the Collect Diagnostics for testTA dialog box.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/start-diagnostics.png)
 
 ### Detailed errors
 
 You can increase the level of tracing collected by the instance and repeat the scenario to gather more detailed logging. To do so, select **Properties** under **Actions** and then add a new property in the **Advanced Settings** grid on the **Advanced** tab. Set the name of the property to `trace` and then set the value to `SOURCE`. 
 
-![Collect diagnostics link](media/known-issues-resolutions-with-cdc-for-oracle-attunity/properties.png)
+![Screenshot showing the Properties option under Actions.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/properties.png)
 
 Reproduce the error and then select the **Collect diagnostics** option to gather logs. 
 
-![Collect diagnostics link](media/known-issues-resolutions-with-cdc-for-oracle-attunity/collect-diagnostics.png)
+![Another screenshot of the Status tab in the Oracle Change Data Capture management console with the Collect Diagnostics option called out.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/collect-diagnostics.png)
 
 ## ORA-00942 Table of view does not exist 
 
 This is a common error displayed in the **Status** message field of the CDC Instance. The instance retries numerous times, so the status icon will change to green momentarily, but then it will fail with the red exclamation and UNEXPECTED status. 
 
-![Oracle error](media/known-issues-resolutions-with-cdc-for-oracle-attunity/oracle-error.png)
+![Screenshot showing the common error displayed in the Status message field of the CDC Instance.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/oracle-error.png)
 
 ```
 "ERROR","computername","ERROR","UNEXPECTED",
@@ -147,7 +147,7 @@ The list of all the necessarily permissions is detailed in the help file include
 
 You can set the user account by selecting the CDCInstance from the left pane and selecting the Properties button in the Actions right-most pane within the **CDC Designer** window. You can change the Oracle log mining authentication account from the properties dialogue page.
 
-![Oracle error](media/known-issues-resolutions-with-cdc-for-oracle-attunity/oracle-connection.png)
+![Screenshot showing the Oracle tab of the testTA Properties dialog box.](media/known-issues-resolutions-with-cdc-for-oracle-attunity/oracle-connection.png)
 
 
 

docs/linux/sql-server-linux-availability-group-cross-platform.md

@@ -63,7 +63,7 @@ The steps to create the AG are the same as the steps to create an AG for read-sc
 
    The following image shows this complete step.
 
-   ![Enable Availability Groups Linux](./media/sql-server-linux-availability-group-cross-platform/2-sqlserver-linux-set-hadr.png)
+   ![Screenshot of a Git Bash window showing the command.](./media/sql-server-linux-availability-group-cross-platform/2-sqlserver-linux-set-hadr.png)
 
 1. Configure hosts file on both servers or register the server names with DNS.
 
@@ -104,7 +104,7 @@ The steps to create the AG are the same as the steps to create an AG for read-sc
 
    In the following diagram, ownership and group are set correctly for the certificate and key.
 
-   ![Enable Availability Groups Linux](./media/sql-server-linux-availability-group-cross-platform/3-cert-key-owner-group.png)
+   ![Screenshot of a Git Bash window showing the .cer and the .pvk in the /var/opt/mssql/data folder.](./media/sql-server-linux-availability-group-cross-platform/3-cert-key-owner-group.png)
 
 
 1. On the secondary replica, create a database login and password and create a master key.

docs/linux/sql-server-linux-develop-use-ssdt.md

@@ -42,13 +42,13 @@ SQL Server on Linux is supported by SSDT version 17.0 RC or later.
 
 3. Click **New** in **Local Git Repository** section on the **Connect** page.
 
-   <img src="./media/sql-server-linux-develop-use-ssdt/git-repository.png" alt="local repository" style="width: 300px;"/>
+   <img src="./media/sql-server-linux-develop-use-ssdt/git-repository.png" alt="Screenshot of the Local Git Repository section with the New option called out." style="width: 300px;"/>
 
 4. Click **Create**. After the local Git repository is created, double-click **SSDTRepo**.
 
 5. Click **New** in the **Solutions** section. Select **SQL Server** under **Other Languages** node in the **New Project** dialog.
 
-   <img src="./media/sql-server-linux-develop-use-ssdt/new-project.png" alt="local repository" style="width: 480px;"/>
+   <img src="./media/sql-server-linux-develop-use-ssdt/new-project.png" alt="Screenshot of the Solutions section with the New option and SQL Server option called out." style="width: 480px;"/>
 
 6. Type in **TutorialDB** for the name and click **OK** to create a new database project.
 
@@ -64,15 +64,15 @@ SQL Server on Linux is supported by SSDT version 17.0 RC or later.
 
 4. Using table designer, add two columns, Name `nvarchar(50)` and Location `nvarchar(50)`, as shown in the picture. SSDT generates the `CREATE TABLE` script as you add the columns in the designer.
 
-   <img src="./media/sql-server-linux-develop-use-ssdt/add-columns.png" alt="add columns" style="width: 480px;"/>
+   <img src="./media/sql-server-linux-develop-use-ssdt/add-columns.png" alt="Screenshot of the table designer with the Name and Location values called out." style="width: 480px;"/>
 
 5. Save the **Table1.sql** file.
 
 ## Build and validate the database
 
 1. Open the database project menu on **TutorialDB** and select **Build**. SSDT compiles .sql source code files in your project and builds a Data-tier Application package (dacpac) file. This can be used to publish a database to your SQL Server instance on Linux. 
 
-   <img src="./media/sql-server-linux-develop-use-ssdt/build.png" alt="add columns" style="width: 400px;"/>
+   <img src="./media/sql-server-linux-develop-use-ssdt/build.png" alt="Screenshot showing the TutorialDB with the Build option called out." style="width: 400px;"/>
 
 2. Check the build success message in **Output** window in Visual Studio. 
 

docs/linux/sql-server-linux-run-sql-server-agent-job.md

@@ -173,9 +173,9 @@ You can also create and manage jobs remotely using SQL Server Management Studio
 
 1. Create a new job schedule.
 
-   ![Job schedule](./media/sql-server-linux-run-sql-server-agent-job/ssms-agent-6.png)
+   ![Screenshot of the New Job dialog box with the Schedules option highlighted and the New option called out.](./media/sql-server-linux-run-sql-server-agent-job/ssms-agent-6.png)
 
-   ![Job schedule](./media/sql-server-linux-run-sql-server-agent-job/ssms-agent-8.png)
+   ![Screenshot of the New Job dialog box with the OK option called out.](./media/sql-server-linux-run-sql-server-agent-job/ssms-agent-8.png)
 
 1. Start your job.
 

docs/relational-databases/extended-events/advanced-viewing-of-target-data-from-extended-events-in-sql-server.md

@@ -284,7 +284,7 @@ Grouping rows together by matching values in a given column, is the first step t
 
 On the extended events toolbar, the **Grouping** button starts a dialog you can use to group the displayed data by a given column. The next screenshot shows a dialog being used to group by the *name* column.
 
-![Toolbar > Grouping button, then the Grouping dialog](../../relational-databases/extended-events/media/xevents-ssms-ui53-grouping.png)
+![Screenshot showing the toolbar with Grouping selected and the Grouping dialog box.](../../relational-databases/extended-events/media/xevents-ssms-ui53-grouping.png)
 
 After the grouping is achieved, the display has a new look, as shown next.
 
@@ -297,11 +297,11 @@ After the grouping is achieved, the display has a new look, as shown next.
 
 After the displayed data has been grouped, you can proceed to aggregate data in other columns.  The next screenshot shows the grouped data is being aggregated by *count*.
 
-![Toolbar > Aggregation button, then the Aggregation dialog](../../relational-databases/extended-events/media/xevents-ssms-ui51-aggregdialogcount.png)
+![Screenshot showing the toolbar with Aggregation selected and the Aggregation dialog box.](../../relational-databases/extended-events/media/xevents-ssms-ui51-aggregdialogcount.png)
 
 After the aggregation is achieved, the display has a new look, as shown next.
 
-![Toolbar > Aggregation button, then the Aggregation dialog](../../relational-databases/extended-events/media/xevents-ssms-ui52-aggregnewdisplay.png)
+![Screenshot of the display showing that a COUNT value has been added.](../../relational-databases/extended-events/media/xevents-ssms-ui52-aggregnewdisplay.png)