Making updates to resolve blocking issues

Author: v-jbasden

articles/app-service/configure-language-java.md

@@ -104,7 +104,7 @@ Here is a sample configuration in `pom.xml`:
 
 #### Gradle
 
-1. Setup the [Gradle Plugin for Azure Web Apps](https://github.com/microsoft/azure-gradle-plugins/tree/master/azure-webapp-gradle-plugin) by adding the plugin to your `build.gradle`:
+1. Set up the [Gradle Plugin for Azure Web Apps](https://github.com/microsoft/azure-gradle-plugins/tree/master/azure-webapp-gradle-plugin) by adding the plugin to your `build.gradle`:
 
     ```groovy
     plugins {
@@ -169,7 +169,7 @@ To deploy .war files to Tomcat, use the `/api/wardeploy/` endpoint to POST your
 
 To deploy .war files to JBoss, use the `/api/wardeploy/` endpoint to POST your archive file. For more information on this API, see [this documentation](./deploy-zip.md#deploy-warjarear-packages).
 
-To deploy .ear files, [use FTP](deploy-ftp.md). Your .ear application will be deployed to the context root defined in your application's configuration. For example, if the context root of your app is `<context-root>myapp</context-root>`, then you can browse the site at the `/myapp` path: `http://my-app-name.azurewebsites.net/myapp`. If you want you web app to be served in the root path, ensure that your app sets the context root to the root path: `<context-root>/</context-root>`. For more information, see [Setting the context root of a web application](https://docs.jboss.org/jbossas/guides/webguide/r2/en/html/ch06.html).
+To deploy .ear files, [use FTP](deploy-ftp.md). Your .ear application will be deployed to the context root defined in your application's configuration. For example, if the context root of your app is `<context-root>myapp</context-root>`, then you can browse the site at the `/myapp` path: `http://my-app-name.azurewebsites.net/myapp`. If you want your web app to be served in the root path, ensure that your app sets the context root to the root path: `<context-root>/</context-root>`. For more information, see [Setting the context root of a web application](https://docs.jboss.org/jbossas/guides/webguide/r2/en/html/ch06.html).
 
 ::: zone-end
 
@@ -474,7 +474,7 @@ This section shows how to connect Java applications deployed on Azure App Servic
 
 ### Configure Application Insights
 
-Azure Monitor application insights is a cloud native application monitoring service that enables customers to observe failures, bottlenecks, and usage patterns to improve application performance and reduce mean time to resolution (MTTR). With a few clicks or CLI commands, you can enable monitoring for your Node.js or Java apps, auto-collecting logs, metrics, and distributed traces, eliminating the need for including an SDK in your app. See the [Application Insights documentation](../azure-monitor/app/java-standalone-config.md) for more information about the available app settings for configuring the agent.
+Azure Monitor Application Insights is a cloud native application monitoring service that enables customers to observe failures, bottlenecks, and usage patterns to improve application performance and reduce mean time to resolution (MTTR). With a few clicks or CLI commands, you can enable monitoring for your Node.js or Java apps, auto-collecting logs, metrics, and distributed traces, eliminating the need for including an SDK in your app. See the [Application Insights documentation](../azure-monitor/app/java-standalone-config.md) for more information about the available app settings for configuring the agent.
 
 #### Azure portal
 
@@ -1126,14 +1126,14 @@ If you choose to pin the minor version, you will need to periodically update the
 
 ### Clustering in JBoss EAP
 
-App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, the web app will restart and JBoss EAP will automatically startup with a clustered configuration. The JBoss EAP instances will communicate over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
+App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, the web app will restart and JBoss EAP will automatically start up with a clustered configuration. The JBoss EAP instances will communicate over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
 
 > [!NOTE]
 > If you are enabling your virtual network integration with an ARM template, you will need to manually set the property `vnetPrivatePorts` to a value of `2`. If you enable virtual network integration from the CLI or Portal, this property will be set for you automatically.  
 
 When clustering is enabled, the JBoss EAP instances use the FILE_PING JGroups discovery protocol to discover new instances and persist the cluster information like the cluster members, their identifiers, and their IP addresses. On App Service, these files are under `/home/clusterinfo/`. The first EAP instance to start will obtain read/write permissions on the cluster membership file. Other instances will read the file, find the primary node, and coordinate with that node to be included in the cluster and added to the file.
 
-The Premium V3 and Isolated V2 App Service Plan types can optionally be distributed across Availability Zones to improve resiliency and reliability for your business-critical workloads. This architecture is also known as [zone redundancy](../availability-zones/migrate-app-service.md). The JBoss EAP clustering feature is compatabile with the zone redundancy feature. 
+The Premium V3 and Isolated V2 App Service Plan types can optionally be distributed across Availability Zones to improve resiliency and reliability for your business-critical workloads. This architecture is also known as [zone redundancy](../availability-zones/migrate-app-service.md). The JBoss EAP clustering feature is compatible with the zone redundancy feature. 
 
 #### Auto-Scale Rules
 
@@ -1157,7 +1157,7 @@ JBoss EAP is only available on the Premium v3 and Isolated v2 App Service Plan t
 
 ### JDK versions and maintenance
 
-Microsoft and Adoptium builds of OpenJDK are provided and supported on App Service for Java 8, 11, and 17. These binaries are provided as a no-cost, multi-platform, production-ready distribution of the OpenJDK for Azure. They contain all the components for building and runnning Java SE applications. For local development or testing, you can install the Microsoft build of OpenJDK from the [downloads page](/java/openjdk/download). The table below describes the new Java versions included in the January 2022 App Service platform release:
+Microsoft and Adoptium builds of OpenJDK are provided and supported on App Service for Java 8, 11, and 17. These binaries are provided as a no-cost, multi-platform, production-ready distribution of the OpenJDK for Azure. They contain all the components for building and running Java SE applications. For local development or testing, you can install the Microsoft build of OpenJDK from the [downloads page](/java/openjdk/download). The table below describes the new Java versions included in the January 2022 App Service platform release:
 
 | Java Version | Linux            | Windows              |
 |--------------|------------------|----------------------|
@@ -1179,7 +1179,7 @@ Patches and fixes for major security vulnerabilities will be released as soon as
 
 Tomcat 8.0 has reached [End of Life (EOL) as of September 30, 2018](https://tomcat.apache.org/tomcat-80-eol.html). While the runtime is still available on Azure App Service, Azure will not apply security updates to Tomcat 8.0. If possible, migrate your applications to Tomcat 8.5 or 9.0. Both Tomcat 8.5 and 9.0 are available on Azure App Service. See the [official Tomcat site](https://tomcat.apache.org/whichversion.html) for more information.
 
-Community support for Java 7 will terminate on July 29th, 2022 and [Java 7 will be retired from App Service](https://azure.microsoft.com/updates/transition-to-java-11-or-8-by-29-july-2022/) at that time. If you have a web app runnning on Java 7, please upgrade to Java 8 or 11 before July 29th.
+Community support for Java 7 will terminate on July 29th, 2022 and [Java 7 will be retired from App Service](https://azure.microsoft.com/updates/transition-to-java-11-or-8-by-29-july-2022/) at that time. If you have a web app running on Java 7, please upgrade to Java 8 or 11 before July 29th.
 
 ### Deprecation and retirement
 

articles/azure-monitor/app/deprecated-java-2x.md

@@ -44,7 +44,7 @@ Application Insights is an extensible analytics service for web developers that
 
 3. Find the instrumentation key of the new resource. You'll need to paste this key into your code project shortly.
 
-    :::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="In the new resource overview, click Properties and copy the Instrumentation Key." lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
+    :::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="Screenshot of the Overview pane for an Application Insights resource in the Azure portal. The screenshot shows the instrumentation key highlighted." lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
 
 ### Add the Application Insights SDK for Java to your project
 
@@ -170,17 +170,17 @@ HTTP requests data appears on the overview pane. (If it isn't there, wait a few
 
 Click through any chart to see more detailed aggregated metrics.
 
-:::image type="content" source="./media/deprecated-java-2x/006-barcharts.png" alt-text="Application Insights failures pane with charts." lightbox="./media/deprecated-java-2x/006-barcharts.png":::
+:::image type="content" source="./media/deprecated-java-2x/006-barcharts.png" alt-text="Screenshot that shows Application Insights failures pane with charts." lightbox="./media/deprecated-java-2x/006-barcharts.png":::
 
 #### Instance data
 Click through a specific request type to see individual instances.
 
-:::image type="content" source="./media/deprecated-java-2x/007-instance.png" alt-text="Drill into a specific sample view" lightbox="./media/deprecated-java-2x/007-instance.png":::
+:::image type="content" source="./media/deprecated-java-2x/007-instance.png" alt-text="Screenshot that shows drilling into a specific sample view." lightbox="./media/deprecated-java-2x/007-instance.png":::
 
 #### Analytics: Powerful query language
 As you accumulate more data, you can run queries both to aggregate data and to find individual instances.  [Analytics](../logs/log-query-overview.md) is a powerful tool for both for understanding performance and usage, and for diagnostic purposes.
 
-:::image type="content" source="./media/deprecated-java-2x/0025.png" alt-text="Example of Analytics." lightbox="./media/deprecated-java-2x/0025.png":::
+:::image type="content" source="./media/deprecated-java-2x/0025.png" alt-text="Screenshot that shows an example of Analytics in the Azure portal." lightbox="./media/deprecated-java-2x/0025.png":::
 
 ### Install your app on the server
 Now publish your app to the server, let people use it, and watch the telemetry show up on the portal.
@@ -225,7 +225,7 @@ Outgoing SDK configuration is defined in the [AI-Agent.xml](#monitor-dependencie
 ### Performance counters
 Open **Investigate**, **Metrics**, to see a range of performance counters.
 
-:::image type="content" source="./media/deprecated-java-2x/011-perf-counters.png" alt-text="Screenshot of metrics pane with process private bytes selected." lightbox="./media/deprecated-java-2x/011-perf-counters.png":::
+:::image type="content" source="./media/deprecated-java-2x/011-perf-counters.png" alt-text="Screenshot of the Metrics pane for an Application Insights resource in the Azure portal. The screenshot shows process private bytes selected." lightbox="./media/deprecated-java-2x/011-perf-counters.png":::
 
 #### Customize performance counter collection
 To disable collection of the standard set of performance counters, add the following code under the root node of the *ApplicationInsights.xml* file:
@@ -478,7 +478,7 @@ Now that you've configured your project to send traces to Application Insights,
 
 Exceptions submitted via loggers will be displayed on the portal as Exception Telemetry.
 
-:::image type="content" source="./media/deprecated-java-2x/01-diagnostics.png" alt-text="In the Application Insights portal, open Search" lightbox="./media/deprecated-java-2x/01-diagnostics.png":::
+:::image type="content" source="./media/deprecated-java-2x/01-diagnostics.png" alt-text="Screenshot of the Search pane for an Application Insights resource in the Azure portal." lightbox="./media/deprecated-java-2x/01-diagnostics.png":::
 
 ## Monitor dependencies, caught exceptions, and method execution times in Java web apps
 
@@ -856,7 +856,7 @@ In the [Microsoft Azure portal](https://portal.azure.com), open the [Application
 
 Take a copy of the instrumentation key, which identifies the resource.
 
-:::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="Browse all, open your resource, and then in the Essentials drop-down, select, and copy the Instrumentation Key" lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
+:::image type="content" source="./media/deprecated-java-2x/instrumentation-key-001.png" alt-text="Screenshot of the Overview pane for an Application Insights resource in the Azure portal. The screenshot shows the instrumentation key highlighted." lightbox="./media/deprecated-java-2x/instrumentation-key-001.png":::
 
 ### Install collectd and the plug-in
 On your Linux server machines: