Merge pull request #17738 from john-par/1783001-fix-validation-suggestion-10-29

Message fixes: Bulk update fixed alt-text bad value validation issues 10-29

Author: Court72

docs/analytics-platform-system/appliance-topology.md

@@ -15,7 +15,7 @@ Displays summary information on the entire Analytics Platform System.
 
 The page lists a read-only version of all the hosts and fabric nodes in the current appliance including their Ethernet and Infiniband IP addresses.  
 
-![SQL_Server_PDW_DWConfig_ApplTop](./media/appliance-topology/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
+![Screenshot of the Microsoft Analytics Platform System Configuration Manager dialog box showing the Appliance Topology.](./media/appliance-topology/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
 
 ## See Also  
 [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md)  

docs/analytics-platform-system/configure-scom-to-monitor-analytics-platform-system.md

@@ -34,52 +34,52 @@ Here are detailed instructions on how to do the tasks:
 
     1.  Navigate to the **Administration** pane, right-click on **Run As Configuration** -> **Accounts** and select **Create Run As Account...**  
 
-        ![ConfigureScomCreateRunAsAccount](./media/configure-scom-to-monitor-analytics-platform-system/ConfigureScomCreateRunAsAccount.png "ConfigureScomCreateRunAsAccount")  
+        ![Screenshot showing the Create Run As Account option.](./media/configure-scom-to-monitor-analytics-platform-system/ConfigureScomCreateRunAsAccount.png "ConfigureScomCreateRunAsAccount")  
 
     2.  The **Create Run As Account Wizard** dialog will open. On the **Introduction** page, click **Next**.  
 
     3.  On the **General Properties** page, select **Windows** from **Run As Account type** and specify "APS Watcher" as the **Display name**.  
 
-        ![CreateRunAsAccountWizardGeneralProperties](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties.png "CreateRunAsAccountWizardGeneralProperties")  
+        ![Screenshot showing the General Properties page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties.png "CreateRunAsAccountWizardGeneralProperties")  
 
     4.  On the **Credentials** page,
-        ![CreateRunAsAccountWizardCredentials](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials.png "CreateRunAsAccountWizardCredentials")  
+        ![Screenshot showing the Credentials page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials.png "CreateRunAsAccountWizardCredentials")  
 
     5.  On the **Distribution Security** page, select **Less secure** and click the **Create** button to finish.  
 
-        ![CreateRunAsAccountWizardDistributionSecurity](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardDistributionSecurity.png "CreateRunAsAccountWizardDistributionSecurity")  
+        ![Screenshot showing the Distribution Security page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardDistributionSecurity.png "CreateRunAsAccountWizardDistributionSecurity")  
 
         1.  If you decide to use the **More secure** option, you have to manually specify computers to which credentials will be distributed. To do this, after creating the Run As account, right-click on it and select **Properties**.  
 
         2.  Navigate to the **Distribution** tab and **Add** desired computers.  
 
-            ![RunAsAccountProperties](./media/configure-scom-to-monitor-analytics-platform-system/RunAsAccountProperties.png "RunAsAccountProperties")  
+            ![Screenshot showing the Run As Account Properties dialog box.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsAccountProperties.png "RunAsAccountProperties")  
 
 2.  Set the **Microsoft APS Watcher Account** profile to use **APS Watcher** Run As account.  
 
     1.  Navigate to **Administration** -> **Run As Configuration** -> **Profiles**.  
 
-        ![AdministrationRunAsConfigurationProfiles](./media/configure-scom-to-monitor-analytics-platform-system/AdministrationRunAsConfigurationProfiles.png "AdministrationRunAsConfigurationProfiles")  
+        ![Screenshot showing the Profiles option.](./media/configure-scom-to-monitor-analytics-platform-system/AdministrationRunAsConfigurationProfiles.png "AdministrationRunAsConfigurationProfiles")  
 
     2.  Right click on **Microsoft APS Watcher Account** from the list and select **Properties**.  
 
-        ![MicrosoftApsWatcherAccountProperties](./media/configure-scom-to-monitor-analytics-platform-system/MicrosoftApsWatcherAccountProperties.png "MicrosoftApsWatcherAccountProperties")  
+        ![Screenshot showing the Properties option.](./media/configure-scom-to-monitor-analytics-platform-system/MicrosoftApsWatcherAccountProperties.png "MicrosoftApsWatcherAccountProperties")  
 
     3.  The **Run As Profile Wizard** dialog will open. Skip the **Introduction** page by clicking **Next**.  
 
     4.  On the **General Properties** page, click **Next**.  
 
     5.  On the **Run As Accounts** page, click the **Add...** button and select the previously created **APS Watcher** Run As account.  
 
-        ![RunAsProfileWizardAdd](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd.png "RunAsProfileWizardAdd")  
+        ![Screenshot showing the Add a Run As Account dialog box.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd.png "RunAsProfileWizardAdd")  
 
     6.  Click **Save** to finish profile assignment.  
 
 3.  Wait until APS appliances discovery completes.  
 
     1.  Navigate to the **Monitoring** pane and open the **SQL Server Appliance** -> **Microsoft Analytics Platform System** -> **Appliances** state view.  
 
-        ![SqlServerApplianceMicrosoftApsAppliances](./media/configure-scom-to-monitor-analytics-platform-system/SqlServerApplianceMicrosoftApsAppliances.png "SqlServerApplianceMicrosoftApsAppliances")  
+        ![Screenshot showing the Appliances option.](./media/configure-scom-to-monitor-analytics-platform-system/SqlServerApplianceMicrosoftApsAppliances.png "SqlServerApplianceMicrosoftApsAppliances")  
 
     2.  Wait until the appliance appears in the list. The name of the appliance should be equal to one specified in the registry. After discovery completes you should see all appliances listed but not monitored. To enable monitoring, follow the next steps.  
 
@@ -92,11 +92,11 @@ Here are detailed instructions on how to do the tasks:
 
     2.  On the **General Properties** page, select **Basic Authentication** account type.  
 
-        ![CreateRunAsAccountWizardGeneralProperties2](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties2.png "CreateRunAsAccountWizardGeneralProperties2")  
+        ![Screenshot showing the General Properties page of the Create Run As Account Wizard with Basic Authentication selected from the Run As Account type dropdown.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties2.png "CreateRunAsAccountWizardGeneralProperties2")  
 
     3.  On the **Credentials** page, supply valid credentials to access APS health state DMVs.  
 
-        ![CreateRunAsAccountWizardCredentials2](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials2.png "CreateRunAsAccountWizardCredentials2")  
+        ![Screenshot showing the Credentials page of the Create Run As Account Wizard with valid credentials wo access APS health state DMVs.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials2.png "CreateRunAsAccountWizardCredentials2")  
 
 5.  Configure the **Microsoft APS Action Account** profile to use the newly created Run As account for the APS instance.  
 
@@ -105,7 +105,7 @@ Here are detailed instructions on how to do the tasks:
     2.  On the **Run As Accounts** page, click **Add...** and 
     3.  select the newly created Run As account.  
 
-        ![RunAsProfileWizardAdd2](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd2.png "RunAsProfileWizardAdd2")  
+        ![Screenshot showing the Add a Run As Account dialog box with APS Action selected from the Run As account dropdown list.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd2.png "RunAsProfileWizardAdd2")  
 
 ## Next Step  
 Now that you have configured the Management Packs, you are ready to start monitoring the appliance. For more information, see [Monitor the Appliance by Using System Center Operations Manager (Analytics Platform System)](monitor-the-appliance-by-using-system-center-operations-manager.md).  

docs/analytics-platform-system/launch-the-configuration-manager.md

@@ -40,7 +40,7 @@ After the **Configuration Manager** is started, you will see all available funct
 
 To close and exit **Configuration Manager**, click **Exit** in the lower-right corner of any screen.  
 
-![SQL_Server_PDW_DWConfig_ApplTop](./media/launch-the-configuration-manager/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
+![Screenshot of the Microsoft Analytics Platform System Configuration Manager dialog box showing the Appliance Topology.](./media/launch-the-configuration-manager/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
 
 ## See Also  
 [Monitor the Appliance by Using the Admin Console (Analytics Platform System)](monitor-the-appliance-by-using-the-admin-console.md)  

docs/database-engine/availability-groups/windows/monitor-performance-for-always-on-availability-groups.md

@@ -84,7 +84,7 @@ To view the RTO and RPO within the dashboard, do the following:
 1. In SQL Server Management Studio, expand the **Always On High Availability** node, right-click the name of your availability group, and select **Show Dashboard**. 
 1. Select **Add/Remove Columns** under the **Group by** tab. Check both **Estimated Recovery Time(seconds)** [RTO] and **Estimated Data Loss (time)** [RPO]. 
 
-   ![rto-rpo-dashboard.png](media/rto-rpo-dashboard.png)
+   ![Screenshot showing the RTO RPO dashboard.](media/rto-rpo-dashboard.png)
 
 ### Calculation of secondary database RTO 
 The recovery time calculation determines how much time is needed to recover the *secondary database* after a failover happens.  The failover time is usually short and constant. The detection time depends on cluster-level settings and not on the individual availability replicas. 

docs/linux/sql-server-linux-shared-disk-cluster-configure-iscsi.md

@@ -41,7 +41,7 @@ For more information on iSCSI initiator for the supported distributions, consult
     ```bash
     sudo iscsiadm -m iface -I iSCSINIC -o new
     ```
-    ![7-setiscsinetwork][6]
+    ![Screenshot of the iface command and the response to the command.][6]
 
 2.	Edit `/var/lib/iscsi/ifaces/iSCSIIfaceName`. Make sure it has the following values completely filled out:
 
@@ -52,7 +52,7 @@ For more information on iSCSI initiator for the supported distributions, consult
 
     See the following example:
 
-    ![iSCSITargetSettings][2]
+    ![Screenshot of the file with the files completely filled out.][2]
 
 3.	Find the iSCSI target.
 
@@ -62,7 +62,7 @@ For more information on iSCSI initiator for the supported distributions, consult
 
      \<iSCSINetName> is the unique/friendly name for the network, \<TargetIPAddress> is the IP address of the iSCSI target, and \<TargetPort> is the port of the iSCSI target. 
 
-    ![iSCSITargetResults][3]
+    ![Screenshot of the discovery command and the response to the command.][3]
 
 
 4.	Log into the target
@@ -89,7 +89,7 @@ For more information on iSCSI initiator for the supported distributions, consult
     ```bash
     sudo grep "Attached SCSI" /var/log/messages
     ```
-    ![30-iSCSIattachedDisks][7]
+    ![Screenshot of the grep command and the response to the command showing the attached SCSI disks.][7]
 
 7.	Create a physical volume on the iSCSI disk.
 
@@ -191,7 +191,7 @@ For more information on iSCSI initiator for the supported distributions, consult
         ls /var/opt/mssql/data
         ```
 
-        ![45-CopyMove][8]
+        ![Screenshot of the ls command and the response to the command.][8]
 
    * Type `exit` to switch back to the root user.
 
@@ -315,7 +315,7 @@ For more information on iSCSI initiator for the supported distributions, consult
 
    *	To test, create a database in that folder. The example shown below uses sqlcmd to create a database, switch context to it, verify the files exist at the OS level, and then deletes the temporary location. You can use SSMS.
   
-        ![50-ExampleCreateSSMS][9]
+        ![Screenshot of the sqlcmd command and the response to the command.][9]
 
    *	Unmount the share 
 
@@ -349,7 +349,7 @@ For more information on iSCSI initiator for the supported distributions, consult
 
     \<ListOfVGsNotUsedByPacemaker> is the list of volume groups from the output of Step 20 that will not be used by the FCI. Put each one in quotes and separate by a comma. An example is shown below.
 
-    ![55-ListOfVGs][11]
+    ![Screenshot showing an example of a volume_list value.][11]
 
 17.	When Linux starts, it will mount the file system. To ensure that only Pacemaker can mount the iSCSI disk, rebuild the root filesystem image. 
 

docs/linux/sql-server-linux-shared-disk-cluster-configure-nfs.md

@@ -30,7 +30,7 @@ When configuring the folder(s) to be shared on the NFS server, make sure they fo
 
 Ensure that your security standards are enforced for accessing. When configuring the folder, make sure that only the servers participating in the FCI should see the NFS folder. An example of a modified /etc/exports on a Linux-based NFS solution is shown below where the folder is restricted to FCIN1 and FCIN2.
 
-![05-nfsacl][1]
+![Screenshot of an example of a modified /etc/exports on a Linux-based NFS solution is shown below where the folder is restricted to FCIN1 and FCIN2.][1]
 
 ## Instructions
 
@@ -126,7 +126,7 @@ Ensure that your security standards are enforced for accessing. When configuring
     mount
     ```
 
-    ![10-mountnoswitches][2]
+    ![Screenshot of the mount command and the response to the command showing no switches.][2]
 
    * Switch to the mssql user. You will not receive any acknowledgement if successful.
 
@@ -222,7 +222,7 @@ Ensure that your security standards are enforced for accessing. When configuring
 
    * To test, create a database in that folder. The following example uses sqlcmd to create a database, switch context to it, verify the files exist at the OS level, and then deletes the temporary location. You can use SSMS.
 
-    ![15-createtestdatabase][4]
+    ![Screenshot of the sqlcmd command and the response to the command.][4]
  
    * Unmount the share 
 

docs/linux/sql-server-linux-shared-disk-cluster-configure-smb.md

@@ -24,7 +24,7 @@ Here are some tips and notes for successfully using SMB:
 - The SMB share should be highly available.
 - Security must be set properly on the SMB share. Below is an example from /etc/samba/smb.conf, where SQLData1 is the name of the share.
 
-![05-smbsource][1]
+![Screenshot showing that SQLData1 is the name of the share.][1]
 
 ## Instructions
 

docs/relational-databases/graphs/sql-graph-architecture.md

@@ -25,7 +25,7 @@ Learn how SQL Graph is architected. Knowing the basics will make it easier to un
 Users can create one graph per database. A graph is a collection of node and edge tables. Node or edge tables can be created under any schema in the database, but they all belong to one logical graph. A node table is collection of similar type of nodes. For example, a Person node table holds all the Person nodes belonging to a graph. Similarly, an edge table is a collection of similar type of edges. For example, a Friends edge table holds all the edges that connect a Person to another Person. Since nodes and edges are stored in tables, most of the operations supported on regular tables are supported on node or edge tables. 
 
 
-![sql-graph-architecture](../../relational-databases/graphs/media/sql-graph-architecture.png "Sql graph database architecture")   
+![Diagram showing the SQL Graph database architecture.](../../relational-databases/graphs/media/sql-graph-architecture.png "Sql graph database architecture")   
 
 Figure 1: SQL Graph database architecture
 
@@ -50,7 +50,7 @@ Similar to the `$node_id` column, it is recommended that users create a unique i
 
 Figure 2 shows how node and edge tables are stored in the database. 
 
-![person-friends-tables](../../relational-databases/graphs/media/person-friends-tables.png "Person node and friends edge tables")   
+![Diagram showing the Node and edge table representation.](../../relational-databases/graphs/media/person-friends-tables.png "Person node and friends edge tables")   
 
 Figure 2: Node and edge table representation
 

docs/relational-databases/graphs/sql-graph-overview.md

@@ -49,7 +49,7 @@ CREATE TABLE Person (ID INTEGER PRIMARY KEY, Name VARCHAR(100), Age INT) AS NODE
 CREATE TABLE friends (StartDate date) AS EDGE;
 ```   
 
-![person-friends-tables](../../relational-databases/graphs/media/person-friends-tables.png "Person node and friends edge tables")  
+![Diagram showing the Nodes and Edges are stored as tables.](../../relational-databases/graphs/media/person-friends-tables.png "Person node and friends edge tables")  
 Nodes and Edges are stored as tables  
 
 ### Query language extensions  

docs/relational-databases/graphs/sql-graph-sample.md

@@ -27,7 +27,7 @@ This sample provides a [!INCLUDE[tsql-md](../../includes/tsql-md.md)] script to
 
 This sample creates a graph schema, as showed in Figure 1, for a hypothetical social network that has People, Restaurant and City nodes. These nodes are connected to each other using Friends, Likes, LivesIn and LocatedIn edges.
 
-![person-cities-restaurants-tables](../../relational-databases/graphs/media/person-cities-restaurants-tables.png "Sql graph database sample")  
+![Diagram showing a sample schema with restaurant, city, person nodes and LivesIn, LocatedIn, Likes edges.](../../relational-databases/graphs/media/person-cities-restaurants-tables.png "Sql graph database sample")  
 Figure 1: Sample schema with restaurant, city, person nodes and LivesIn, LocatedIn, Likes edges.
 
 ## Sample Script