Fixing alt text

Author: v-dirichards

articles/app-service/environment/how-to-migrate.md

@@ -201,17 +201,17 @@ App Service Environment v3 requires the subnet it's in to have a single delegati
 
 You can make your new App Service Environment v3 zone redundant if your existing environment is in a [region that supports zone redundancy](./overview.md#regions). Zone redundancy is an optional configuration. This configuration can only be set during the creation of your new App Service Environment v3 and can't be removed at a later time. For more information, see [Choose your App Service Environment v3 configurations](./migrate.md#choose-your-app-service-environment-v3-configurations). Select **Enabled** if you'd like to configure zone redundancy.
 
-:::image type="content" source="./media/migration/zone-redundancy-supported.png" alt-text="Sample that shows how to enable zone redundancy for App Service Environment in a supported region.":::
+:::image type="content" source="./media/migration/zone-redundancy-supported.png" alt-text="Screenshot that shows how to enable zone redundancy for App Service Environment in a supported region.":::
 
 If your environment is in a region that doesn't support zone redundancy, the checkbox will be disabled. If you need a zone redundant App Service Environment v3, use one of the manual migration options and create your new App Service Environment v3 in one of the regions that supports zone redundancy.
 
 If your existing App Service Environment uses a [custom domain suffix](./migrate.md#choose-your-app-service-environment-v3-configurations), you'll be required to configure one for your new App Service Environment v3. You'll be shown the custom domain suffix configuration options if this situation applies to you. You won't be able to migrate until you provide the required information. If you'd like to use a custom domain suffix but don't currently have one configured, you can configure one once migration is complete. For more information on App Service Environment v3 custom domain suffix including requirements, step-by-step instructions, and best practices, see [Configure custom domain suffix for App Service Environment](./how-to-custom-domain-suffix.md).
 
-:::image type="content" source="./media/migration/input-custom-domain-suffix.png" alt-text="Sample that shows how to add a custom domain suffix configuration.":::
+:::image type="content" source="./media/migration/input-custom-domain-suffix.png" alt-text="Screenshot that shows how to add a custom domain suffix configuration.":::
 
 After you add your custom domain suffix details, the "Migrate" button will be enabled.
 
-:::image type="content" source="./media/migration/custom-domain-suffix.png" alt-text="Sample that shows the configuration details have been added and environment is ready for migration.":::
+:::image type="content" source="./media/migration/custom-domain-suffix.png" alt-text="Screenshot that shows the configuration details have been added and environment is ready for migration.":::
 
 ## 6. Migrate to App Service Environment v3
 
@@ -221,7 +221,7 @@ When migration is complete, you'll have an App Service Environment v3, and all o
 
 If your migration included a custom domain suffix, for App Service Environment v3, the custom domain will no longer be shown in the **Essentials** section of the **Overview** page of the portal as it is for App Service Environment v1/v2. Instead, for App Service Environment v3, go to the **Custom domain suffix** page where you can confirm your custom domain suffix is configured correctly. You can also remove the configuration if you no longer need it or configure one if you didn't have one previously. 
 
-:::image type="content" source="./media/migration/custom-domain-suffix-app-service-environment-v3.png" alt-text="Sample that shows how to access custom domain suffix configuration for App Service Environment v3.":::
+:::image type="content" source="./media/migration/custom-domain-suffix-app-service-environment-v3.png" alt-text="Screenshot that shows how to access custom domain suffix configuration for App Service Environment v3.":::
 
 ::: zone-end
 

articles/app-service/environment/migration-alternatives.md

@@ -41,7 +41,7 @@ The [back up and restore](../manage-backup.md) feature allows you to keep your a
 
 The step-by-step instructions in the current documentation for [backup and restore](../manage-backup.md) should be sufficient to allow you to use this feature. You can select a backup and use that to restore the app to an App Service in your App Service Environment v3.
 
-:::image type="content" source="./media/migration/back-up-restore-sample.png" alt-text="Example showing how to use backup to restore App Service in App Service Environment v3.":::
+:::image type="content" source="./media/migration/back-up-restore-sample.png" alt-text="Screenshot that shows how to use backup to restore App Service in App Service Environment v3.":::
 
 |Benefits     |Limitations    |
 |---------|---------|
@@ -71,7 +71,7 @@ To clone an app using the [Azure portal](https://www.portal.azure.com), navigate
 1. You can use an existing Windows **App Service plan** from your new environment if you created one already, or create a new one. The available Windows App Service plans in your new App Service Environment v3, if any, will be listed in the dropdown.
 1. Modify **SKU and size** as needed using one of the Isolated v2 options if creating a new App Service plan. Note App Service Environment v3 uses Isolated v2 plans, which have more memory and CPU per corresponding instance size compared to the Isolated plan. For more information, see [App Service Environment v3 SKU details](overview.md#pricing).
 
-:::image type="content" source="./media/migration/portal-clone-sample.png" alt-text="Example that shows how to clone an app to App Service Environment v3 using the portal.":::
+:::image type="content" source="./media/migration/portal-clone-sample.png" alt-text="Screenshot that shows how to clone an app to App Service Environment v3 using the portal.":::
 
 |Benefits     |Limitations     |
 |---------|---------|
@@ -85,11 +85,11 @@ If the above features don't support your apps or you're looking to take a more m
 
 You can export [Azure Resource Manager (ARM) templates](../../azure-resource-manager/templates/overview.md) of your existing apps, App Service plans, and any other supported resources and deploy them in or with your new environment. To export a template for just your app, navigate to your App Service and go to **Export template** under **Automation**.
 
-:::image type="content" source="./media/migration/export-toc.png" alt-text="Demonstration of how to export App Service template from TOC.":::
+:::image type="content" source="./media/migration/export-toc.png" alt-text="Screenshot of how to export App Service template from TOC.":::
 
 You can also export templates for multiple resources directly from your resource group by going to your resource group, selecting the resources you want a template for, and then selecting **Export template**.
 
-:::image type="content" source="./media/migration/export-template-sample.png" alt-text="Demonstration of how to export template for resources from a resource group.":::
+:::image type="content" source="./media/migration/export-template-sample.png" alt-text="Screenshot of how to export template for resources from a resource group.":::
 
 The following initial changes to your Azure Resource Manager templates are required to get your apps onto your App Service Environment v3: