Validation issues.

Author: TimShererWithAquent

articles/active-directory/azuread-dev/sample-v1-code.md

@@ -49,8 +49,8 @@ The following samples illustrate Web applications signing users. Some of these a
 
  Platform | Only signs in users | Calls Microsoft Graph | Calls another ASP.NET or ASP.NET Core 2.0 Web API
  -------- | ------------------- | --------------------- | -------------------------
-![This image shows the ASP.NET logo](media/sample-v2-code/logo-netcore.png)</p>ASP.NET Core 2.0 | [dotnet-webapp-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect-aspnetcore) | [webapp-webapi-multitenant-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/) </p>(AAD Graph) | [dotnet-webapp-webapi-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-openidconnect-aspnetcore)
-![This image shows the ASP.NET logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 |  </p> [webapp-WSFederation-dotNet](https://github.com/Azure-Samples/active-directory-dotnet-webapp-wsfederation) </p> [dotnet-webapp-webapi-oauth2-useridentity](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-oauth2-useridentity) | [dotnet-webapp-multitenant-openidconnect](https://github.com/Azure-Samples/active-directory-dotnet-webapp-multitenant-openidconnect)</p> (AAD Graph) |
+![This image shows the ASP.NET Core logo](media/sample-v2-code/logo-netcore.png)</p>ASP.NET Core 2.0 | [dotnet-webapp-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect-aspnetcore) | [webapp-webapi-multitenant-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/) </p>(AAD Graph) | [dotnet-webapp-webapi-openidconnect-aspnetcore](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-openidconnect-aspnetcore)
+![This image shows the ASP.NET Framework logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 |  </p> [webapp-WSFederation-dotNet](https://github.com/Azure-Samples/active-directory-dotnet-webapp-wsfederation) </p> [dotnet-webapp-webapi-oauth2-useridentity](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-oauth2-useridentity) | [dotnet-webapp-multitenant-openidconnect](https://github.com/Azure-Samples/active-directory-dotnet-webapp-multitenant-openidconnect)</p> (AAD Graph) |
 ![This image shows the Python logo](media/sample-v2-code/logo-python.png) | | [python-webapp-graphapi](https://github.com/Azure-Samples/active-directory-python-webapp-graphapi)  |
 ![This image shows the Java log](media/sample-v2-code/logo-java.png)  | | [java-webapp-openidconnect](https://github.com/azure-samples/active-directory-java-webapp-openidconnect)  |
 ![This image shows the PHP logo](media/sample-v2-code/logo-php.png) | | [php-graphapi-web](https://github.com/Azure-Samples/active-directory-php-graphapi-web)  |
@@ -61,7 +61,7 @@ The following samples show how to implement role-based access control (RBAC). RB
 
 Platform | Sample |
  -------- | ------------------- |
-![This image shows the ASP.NET logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 | [dotnet-webapp-groupclaims](https://github.com/Azure-Samples/active-directory-dotnet-webapp-groupclaims) </p>  [dotnet-webapp-roleclaims](https://github.com/Azure-Samples/active-directory-dotnet-webapp-roleclaims) | A .NET 4.5 MVC web app that uses Azure AD **roles** for authorization
+![This image shows the ASP.NET Framework logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 | [dotnet-webapp-groupclaims](https://github.com/Azure-Samples/active-directory-dotnet-webapp-groupclaims) </p>  [dotnet-webapp-roleclaims](https://github.com/Azure-Samples/active-directory-dotnet-webapp-roleclaims) | A .NET 4.5 MVC web app that uses Azure AD **roles** for authorization
 
 ## Desktop and mobile public client applications calling Microsoft Graph or a Web API
 
@@ -88,9 +88,9 @@ The following samples show desktop or web applications that access the Microsoft
 
 Client application | Platform | Flow/Grant | Calls an ASP.NET or ASP.NET Core 2.0 Web API
 ------------------ | -------- | ---------- | -------------------- 
-Daemon app (Console)          | ![This image shows the .NET logo](media/sample-v2-code/logo-netframework.png) | Client Credentials with app secret or certificate | [dotnet-daemon](https://github.com/azure-samples/active-directory-dotnet-daemon)</p> [dotnet-daemon-certificate-credential](https://github.com/azure-samples/active-directory-dotnet-daemon-certificate-credential)
-Daemon app (Console)         | ![This image shows the .NET logo](media/sample-v2-code/logo-netcore.png) | Client Credentials with certificate| [dotnetcore-daemon-certificate-credential](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-certificate-credential)
-ASP.NET Web App  | ![This image shows the .NET logo](media/sample-v2-code/logo-netframework.png) | Client credentials | [dotnet-webapp-webapi-oauth2-appidentity](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-oauth2-appidentity)
+Daemon app (Console)          | ![This image shows the .NET Framework logo](media/sample-v2-code/logo-netframework.png) | Client Credentials with app secret or certificate | [dotnet-daemon](https://github.com/azure-samples/active-directory-dotnet-daemon)</p> [dotnet-daemon-certificate-credential](https://github.com/azure-samples/active-directory-dotnet-daemon-certificate-credential)
+Daemon app (Console)         | ![This image shows the .NET Core logo](media/sample-v2-code/logo-netcore.png) | Client Credentials with certificate| [dotnetcore-daemon-certificate-credential](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-certificate-credential)
+ASP.NET Web App  | ![This image shows the .NET Framework logo](media/sample-v2-code/logo-netframework.png) | Client credentials | [dotnet-webapp-webapi-oauth2-appidentity](https://github.com/Azure-Samples/active-directory-dotnet-webapp-webapi-oauth2-appidentity)
 
 ## Web APIs
 
@@ -110,7 +110,7 @@ The following samples demonstrate a web API that calls another web API. The seco
 
 | Platform |  Calls Microsoft Graph | Calls another ASP.NET or ASP.NET Core 2.0 Web API |
 | -------- |  --------------------- | ------------------------- |
-| ![This image shows the ASP.NET logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 | [dotnet-webapi-onbehalfof](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof) </p> [dotnet-webapi-onbehalfof-ca](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof-ca) | [dotnet-webapi-onbehalfof](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof) </p> [dotnet-webapi-onbehalfof-ca](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof-ca) |
+| ![This image shows the ASP.NET Framework logo](media/sample-v2-code/logo-netframework.png)</p> ASP.NET 4.5 | [dotnet-webapi-onbehalfof](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof) </p> [dotnet-webapi-onbehalfof-ca](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof-ca) | [dotnet-webapi-onbehalfof](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof) </p> [dotnet-webapi-onbehalfof-ca](https://github.com/azure-samples/active-directory-dotnet-webapi-onbehalfof-ca) |
 
 ## Other Microsoft Graph samples
 

articles/active-directory/develop/authentication-flows-app-scenarios.md

@@ -214,7 +214,7 @@ Scenarios that involve acquiring tokens also map to OAuth 2.0 authentication flo
  </tr>
 
   <tr>
-   <td><a href="scenario-web-app-call-api-overview.md"><img alt="Web app that signs in users" src="media/scenarios/web-app.svg"></a></td>
+   <td><a href="scenario-web-app-call-api-overview.md"><img alt="Web app that calls web APIs" src="media/scenarios/web-app.svg"></a></td>
    <td><a href="scenario-web-app-call-api-overview.md">Web app that calls web APIs</a></td>
    <td><a href="v2-oauth2-auth-code-flow.md">Authorization code</a></td>
    <td>Work or school accounts, personal accounts, and Azure AD B2C</td>

articles/active-directory/develop/scenario-web-app-sign-user-app-registration.md

@@ -48,13 +48,13 @@ You can use these links to bootstrap the creation of your web application:
    1. Choose the supported account types for your application. (See [Supported account types](./v2-supported-account-types.md).)
    1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app. For example, enter **AspNetCore-WebApp**.
    1. For **Redirect URI**, add the type of application and the URI destination that will accept returned token responses after successful authentication. For example, enter **https://localhost:44321**. Then, select **Register**.
-   ![registration](media/scenario-webapp/scenario-webapp-app-registration-1.png)
+   ![Screenshot shows the Register an application page where you can select Register.](media/scenario-webapp/scenario-webapp-app-registration-1.png)
 1. Select the **Authentication** menu, and then add the following information:
    1. For **Reply URL**, add **https://localhost:44321/signin-oidc** of type **Web**.
    1. In the **Advanced settings** section, set **Logout URL** to **https://localhost:44321/signout-oidc**.
    1. Under **Implicit grant**, select **ID tokens**.
    1. Select **Save**.
-  ![registration](media/scenario-webapp/scenario-webapp-app-registration-2.png)
+  ![Screenshot shows the Authentication options, where you can make the changes described.](media/scenario-webapp/scenario-webapp-app-registration-2.png)
 
 # [ASP.NET](#tab/aspnet)
 

articles/cosmos-db/tutorial-develop-mongodb-nodejs-part4.md

@@ -59,11 +59,11 @@ Once the Azure Cosmos DB account has been created:
 1. Click the Azure Cosmos DB logo :::image type="icon" source="./media/tutorial-develop-mongodb-nodejs-part4/azure-cosmos-db-icon.png"::: on the left bar, and it shows you all the Azure Cosmos DBs you have.
 1. Click on the Azure Cosmos DB account you just created, select the **Overview** tab and scroll down to view the map where the database is located. 
 
-    :::image type="content" source="./media/tutorial-develop-mongodb-nodejs-part4/azure-cosmos-db-angular-portal.png" alt-text="New Azure Cosmos DB account in the Azure portal":::
+    :::image type="content" source="./media/tutorial-develop-mongodb-nodejs-part4/azure-cosmos-db-angular-portal.png" alt-text="Screenshot shows the Overview of an Azure Cosmos D B Account.":::
 
 4. Scroll down on the left navigation and click the **Replicate data globally** tab, this displays a map where you can see the different areas you can replicate into. For example, you can click Australia Southeast or Australia East and replicate your data to Australia. You can learn more about global replication in [How to distribute data globally with Azure Cosmos DB](distribute-data-globally.md). For now, let's just keep the once instance and when we want to replicate, we know how.
 
-    :::image type="content" source="./media/tutorial-develop-mongodb-nodejs-part4/azure-cosmos-db-replicate-portal.png" alt-text="New Azure Cosmos DB account in the Azure portal":::
+    :::image type="content" source="./media/tutorial-develop-mongodb-nodejs-part4/azure-cosmos-db-replicate-portal.png" alt-text="Screenshot shows an Azure Cosmos D B Account with Replicate data globally selected.":::
 
 ## Next steps
 

articles/data-share/how-to-add-datasets.md

@@ -18,11 +18,11 @@ For information on how to add datasets as you create a share, see the [Share dat
 
 In Azure Data Share, navigate to your sent share and select the **Datasets** tab. Click **+ Add Datasets** button to add more datasets.
 
-![Add Datasets](./media/how-to/how-to-add-datasets/add-datasets.png)
+![Screenshot shows Add Datasets selected.](./media/how-to/how-to-add-datasets/add-datasets.png)
 
 In the panel on the right, select the dataset type you would like to add and then click **Next**. Select the subscription and resource group of the data you would like to add. Using the dropdown arrows, find and then check the box next to the data to add.
 
-![Add Datasets](./media/how-to/how-to-add-datasets/add-datasets-side.png)
+![Screenshot shows the Add Blob Storage pane where you can select data.](./media/how-to/how-to-add-datasets/add-datasets-side.png)
 
 Once you click **Add Datasets**, the datasets will be added to your share. 
 Note: A snapshot must be triggered by your consumers in order for them to see the new datasets. If there are snapshot settings configured, consumers will see the new datasets once the next scheduled snapshot completes. 

articles/data-share/how-to-add-recipients.md

@@ -17,11 +17,11 @@ For information on how to add recipients as you create a share, see the [Share d
 
 In Azure Data Share, navigate to your sent share and select the **Invitations** tab. Listed here are all of the recipients of invitations to this data share. To add a new one, click **Add Recipient**.
 
-![Add Recipient](./media/how-to/how-to-add-recipients/add-recipient.png)
+![Screenshot shows Add Recipient selected.](./media/how-to/how-to-add-recipients/add-recipient.png)
 
 A panel will pop out on the right side of the page. Click **Add Recipient** and then fill in the email of your new recipient on the blank line. Add as many recipients as you would like.
 
-![Add Recipient](./media/how-to/how-to-add-recipients/add-recipient-side.png)
+![Screenshot shows the Add Recipient pane where you can Add and send invitation.](./media/how-to/how-to-add-recipients/add-recipient-side.png)
 
 Click **Add and send invitation**. The new recipient(s) will be sent invitation emails to this data share.
 

articles/data-share/how-to-monitor.md

@@ -37,7 +37,7 @@ View the status of your share subscriptions by navigating to Sent Shares -> Shar
 
 In the **History** tab of a share, you are able to view when data is copied from data provider to data consumer's data store. You are able to monitor the frequency, duration and status of each snapshot. 
 
-![Snapshot history](./media/sent-shares.png "Snapshot history") 
+![Screenshot shows Sent Shares in the Azure portal.](./media/sent-shares.png "Snapshot history") 
 
 You can view more details about each snapshot run by clicking on the run start date. Then click on the status for each dataset to view the amount of data transferred, number of files/records copied, duration of the snapshot, number of vCores used and error message if there is any. 
 
@@ -47,7 +47,7 @@ Up to 30 days of snapshot history is displayed. If you need to save and see more
 
 You can configure diagnostic setting to save log data or events. Navigate to Monitoring -> Diagnostic settings and select **Add diagnostic setting**. Select the log data or events that you are interested in, and where you want to store or send them. 
 
-![Snapshot history](./media/diagnostic-settings.png "Diagnostic settings") 
+![Screenshot shows the Diagnostic settings page in the Azure portal.](./media/diagnostic-settings.png "Diagnostic settings") 
 
 ## Next Steps 
 

articles/media-services/previous/media-rest-apis-with-postman.md

@@ -39,22 +39,22 @@ This environment and collection is used in articles that show how to achieve var
 2. Open the **Postman**.
 3. On the right of the screen, select the **Manage environment** option.
 
-    ![Upload a file](./media/media-services-rest-upload-files/postman-create-env.png)
+    ![Screenshot shows the Manage Environment option selected.](./media/media-services-rest-upload-files/postman-create-env.png)
 4. From the **Manage environment** dialog, click **Import**.
 5. Browse and select the **AzureMediaServices.postman_environment.json** file.
 6. The **AzureMedia** environment is added.
 7. Close the dialog.
 8. Select the **AzureMedia** environment.
 
-    ![Upload a file](./media/media-services-rest-upload-files/postman-choose-env.png)
+    ![Screenshot shows the AzureMedia environment selected.](./media/media-services-rest-upload-files/postman-choose-env.png)
 
 ## Configure the collection
 
 1. Create a .json file that contains the **Postman** collection with all the operations that are needed to upload a file to Media Services. Name the file (for example, **AzureMediaServicesOperations.postman_collection.json**). Open the file and paste the code that defines the **Postman** collection from [this code listing](postman-collection.md).
 2. Click **Import** to import the collection file.
 3. Choose the **AzureMediaServicesOperations.postman_collection.json** file.
 
-    ![Upload a file](./media/media-services-rest-upload-files/postman-import-collection.png)
+    ![Screenshot shows the IMPORT dialog box with Choose Files selected.](./media/media-services-rest-upload-files/postman-import-collection.png)
 
 ## Next steps