Merge pull request #268616 from ktoliver/219874

[AQ] edit pass: Raise Acrolinx scores in 9 azure-monitor/app articles (work item 219874)

Author: ShawnJackson

articles/azure-monitor/app/java-get-started-supplemental.md

@@ -1,6 +1,6 @@
 ---
 title: Application Insights with containers
-description: This article shows you how to set-up Application Insights
+description: This article shows you how to set up Application Insights.
 ms.topic: conceptual
 ms.date: 03/12/2024
 ms.devlang: java
@@ -10,7 +10,7 @@ ms.reviewer: mmcc
 
 # Get Started (Supplemental)
 
-In the following sections, you will find information on how to get Java autoinstrumentation for specific technical environments.
+In the following sections, learn how to get Java autoinstrumentation for specific technical environments.
 
 ## Azure App Service
 
@@ -37,7 +37,7 @@ If you're using the *exec* form, add the parameter `-javaagent:"path/to/applicat
 ENTRYPOINT ["java", "-javaagent:path/to/applicationinsights-agent-3.5.1.jar", "-jar", "<myapp.jar>"]
 ```
 
-If you're using the *shell* form, add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.5.1.jar"` somewhere before `-jar`, for example:
+If you're using the *shell* form, add the Java Virtual Machine (JVM) arg `-javaagent:"path/to/applicationinsights-agent-3.5.1.jar"` somewhere before `-jar`, for example:
 
 ```
 ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.5.1.jar" -jar <myapp.jar>
@@ -62,11 +62,11 @@ ENV APPLICATIONINSIGHTS_CONNECTION_STRING="CONNECTION-STRING"
 ENTRYPOINT["java", "-javaagent:applicationinsights-agent-3.5.1.jar", "-jar", "app.jar"]
 ```
 
-In this example we have copied the `applicationinsights-agent-3.5.1.jar` and `applicationinsights.json` files from an `agent` folder (you can choose any folder of your machine). These two files have to be in the same folder in the Docker container.
+In this example, you copy the `applicationinsights-agent-3.5.1.jar` and `applicationinsights.json` files from an `agent` folder (you can choose any folder of your machine). These two files have to be in the same folder in the Docker container.
 
-### Third-party container images
+### Partner container images
 
-If you're using a third-party container image that you can't modify, mount the Application Insights Java agent jar into the container from outside. Set the environment variable for the container
+If you're using a partner container image that you can't modify, mount the Application Insights Java agent jar into the container from outside. Set the environment variable for the container
 `JAVA_TOOL_OPTIONS=-javaagent:/path/to/applicationinsights-agent.jar`.
 
 ## Spring Boot
@@ -75,7 +75,7 @@ For more information, see [Using Azure Monitor Application Insights with Spring
 
 ## Java Application servers
 
-For information on setting up the Application Insights Java agent, see [Enabling Azure Monitor OpenTelemetry for Java](./opentelemetry-enable.md?tabs=java). The following sections provide additional details which may be helpful when configuring the `-javaagent:...` JVM arg on different application servers.
+For information on setting up the Application Insights Java agent, see [Enabling Azure Monitor OpenTelemetry for Java](./opentelemetry-enable.md?tabs=java). The following sections provide details that might be helpful when configuring the `-javaagent:...` JVM arg on different application servers.
 
 ### Tomcat 8 (Linux)
 
@@ -119,7 +119,9 @@ If the file `<tomcat>/bin/setenv.bat` already exists, modify that file and add `
 
 Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.5.1.jar` to the `Java Options` under the `Java` tab.
 
-### JBoss EAP 7
+### JBoss Enterprise Application Platform 7
+
+In Red Hat JBoss Enterprise Application Platform (EAP) 7, you can set up a standalone server or a domain server.
 
 #### Standalone server
 
@@ -151,7 +153,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.5.1.jar` to the existing `jv
 ...
 ```
 
-If you're running multiple managed servers on a single host, you'll need to add `applicationinsights.agent.id` to the `system-properties` for each `server`:
+If you're running multiple managed servers on a single host, you need to add `applicationinsights.agent.id` to the `system-properties` for each `server`:
 
 ```xml
 ...
@@ -173,7 +175,7 @@ If you're running multiple managed servers on a single host, you'll need to add
 ...
 ```
 
-The specified `applicationinsights.agent.id` value must be unique. It's used to create a subdirectory under the Application Insights directory. Each JVM process needs its own local Application Insights config and local Application Insights log file. Also, if reporting to the central collector, the `applicationinsights.properties` file is shared by the multiple managed servers, so the specified `applicationinsights.agent.id` is needed to override the `agent.id` setting in that shared file. The `applicationinsights.agent.rollup.id` can be similarly specified in the server's `system-properties` if you need to override the `agent.rollup.id` setting per managed server.
+The specified `applicationinsights.agent.id` value must be unique. You use the value to create a subdirectory under the Application Insights directory. Each JVM process needs its own local Application Insights config and local Application Insights log file. Also, if reporting to the central collector, multiple managed servers share the `applicationinsights.properties` file, so the specified `applicationinsights.agent.id` is needed to override the `agent.id` setting in that shared file. The `applicationinsights.agent.rollup.id` can be similarly specified in the server's `system-properties` if you need to override the `agent.rollup.id` setting per managed server.
 
 ### Jetty 9
 
@@ -203,13 +205,9 @@ Add `-javaagent:path/to/applicationinsights-agent-3.5.1.jar` to the existing `jv
 ### WebSphere 8
 
 1. Open Management Console.
-1. Go to **Servers** > **WebSphere application servers** > **Application servers**. Choose the appropriate application servers and select:
-
-    ```
-    Java and Process Management > Process definition >  Java Virtual Machine
-    ```
+1. Go to **Servers** > **WebSphere application servers** > **Application servers**. Choose the appropriate application servers and select **Java and Process Management** > **Process definition** > **Java Virtual Machine**.
 
-1. In `Generic JVM arguments`, add the following JVM argument:
+1. In `Generic JVM arguments`, add the following JVM argument.
 
     ```
     -javaagent:path/to/applicationinsights-agent-3.5.1.jar
@@ -227,4 +225,4 @@ Create a new file `jvm.options` in the server directory (for example, `<openlibe
 
 ### Others
 
-See your application server documentation on how to add JVM args.
+See your application server documentation on how to add JVM args.

articles/azure-monitor/app/java-jmx-metrics-configuration.md

@@ -1,6 +1,6 @@
 ---
 title: How to configure JMX metrics - Azure Monitor application insights for Java
-description: Configure extra JMX metrics collection for Azure Monitor Application Insights Java agent
+description: Configure extra Java Management Extensions (JMX) metrics collection for Azure Monitor Application Insights Java agent.
 ms.topic: conceptual
 ms.date: 12/15/2023
 ms.devlang: java
@@ -10,11 +10,11 @@ ms.reviewer: mmcc
 
 # Configuring JMX metrics
 
-Application Insights Java 3.x collects some of the JMX metrics by default, but in many cases it isn't enough. This document describes the JMX configuration option in details.
+Application Insights Java 3.x collects some of the Java Management Extensions (JMX) metrics by default, but in many cases it isn't enough. This document describes the JMX configuration option in details.
 
 ## How do I collect extra JMX metrics?
 
-JMX metrics collection can be configured by adding a ```"jmxMetrics"``` section to the applicationinsights.json file. You can specify the name of the metric the way you want it to appear in Azure portal in application insights resource. Object name and attribute are required for each of the metrics you want collected.
+JMX metrics collection can be configured by adding a ```"jmxMetrics"``` section to the applicationinsights.json file. Enter a name for the metric as you want it to appear in Azure portal in application insights resource. Object name and attribute are required for each of the metrics you want collected.
 
 ## How do I know what metrics are available to configure?
 

articles/azure-monitor/app/java-spring-boot.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 > [!NOTE]
 > With _Spring Boot native image applications_, you can use [this project](https://aka.ms/AzMonSpringNative).
 
-There are two options for enabling Application Insights Java with Spring Boot: JVM argument and programmatically.
+There are two options for enabling Application Insights Java with Spring Boot: Java Virtual Machine (JVM) argument and programmatically.
 
 ## Enabling with JVM argument 
 
@@ -42,8 +42,7 @@ To enable Application Insights Java programmatically, you must add the following
 </dependency>
 ```
 
-And invoke the `attach()` method of the `com.microsoft.applicationinsights.attach.ApplicationInsights` class
-in the first line of your `main()` method.
+And invoke the `attach()` method of the `com.microsoft.applicationinsights.attach.ApplicationInsights` class that's in the beginning line of your `main()` method.
 
 > [!WARNING]
 >
@@ -73,15 +72,15 @@ public class SpringBootApp {
 ### Configuration
 
 Programmatic enablement supports all the same [configuration options](./java-standalone-config.md)
-as the JVM argument enablement, with the following differences below.
+as the JVM argument enablement, with the differences that are described in the next sections.
 
 #### Configuration file location
 
 By default, when enabling Application Insights Java programmatically, the configuration file `applicationinsights.json`
-will be read from the classpath (`src/main/resources`, `src/test/resources`).
+is read from the classpath (`src/main/resources`, `src/test/resources`).
 
 From 3.4.3, you can configure the name of a JSON file in the classpath with the `applicationinsights.runtime-attach.configuration.classpath.file` system property.
-For example, with `-Dapplicationinsights.runtime-attach.configuration.classpath.file=applicationinsights-dev.json`, Application Insights will use `applicationinsights-dev.json` file for configuration. To programmatically configure another file in the classpath:
+For example, with `-Dapplicationinsights.runtime-attach.configuration.classpath.file=applicationinsights-dev.json`, Application Insights uses the `applicationinsights-dev.json` file for configuration. To programmatically configure another file in the classpath:
 
 ```java
 public static void main(String[] args) {
@@ -141,6 +140,6 @@ Enable connection string configured at runtime:
 #### Self-diagnostic log file location
 
 By default, when enabling Application Insights Java programmatically, the `applicationinsights.log` file containing
-the agent logs will be located in the directory from where the JVM is launched (user directory).
+the agent logs are located in the directory from where the JVM is launched (user directory).
 
-See [self-diagnostic configuration options](./java-standalone-config.md#self-diagnostics) to change this location.
+To learn how to change this location, see your [self-diagnostic configuration options](./java-standalone-config.md#self-diagnostics).

articles/azure-monitor/app/java-standalone-config.md

@@ -72,7 +72,7 @@ The file should contain only the connection string and nothing else.
 
 Not setting the connection string disables the Java agent.
 
-If you have multiple applications deployed in the same JVM and want them to send telemetry to different connection strings, see [Connection string overrides (preview)](#connection-string-overrides-preview).
+If you have multiple applications deployed in the same Java Virtual Machine (JVM) and want them to send telemetry to different connection strings, see [Connection string overrides (preview)](#connection-string-overrides-preview).
 
 ## Cloud role name
 
@@ -185,9 +185,9 @@ Sampling overrides allow you to override the [default sampling percentage](#samp
 
 For more information, see the [Sampling overrides](./java-standalone-sampling-overrides.md) documentation.
 
-## JMX metrics
+## Java Management Extensions metrics
 
-If you want to collect some other JMX metrics:
+If you want to collect some other Java Management Extensions (JMX) metrics:
 
 ```json
 {
@@ -209,12 +209,12 @@ If you want to collect some other JMX metrics:
 In the preceding configuration example:
 
 * `name` is the metric name that is assigned to this JMX metric (can be anything).
-* `objectName` is the [Object Name](https://docs.oracle.com/javase/8/docs/api/javax/management/ObjectName.html) of the `JMX MBean` that you want to collect.  Wildcard character asterisk (*) is supported.
+* `objectName` is the [Object Name](https://docs.oracle.com/javase/8/docs/api/javax/management/ObjectName.html) of the `JMX MBean` that you want to collect. Wildcard character asterisk (*) is supported.
 * `attribute` is the attribute name inside of the `JMX MBean` that you want to collect.
 
 Numeric and Boolean JMX metric values are supported. Boolean JMX metrics are mapped to `0` for false and `1` for true.
 
-See the [JMX metrics](./java-jmx-metrics-configuration.md) documentation for more details.
+For more information, see the [JMX metrics](./java-jmx-metrics-configuration.md) documentation.
 
 ## Custom dimensions
 
@@ -251,7 +251,7 @@ Starting with version 3.2.0, you can set a custom dimension programmatically on
 }
 ```
 
-and then at the beginning of each request, call:
+And then at the beginning of each request, call:
 
 ```java
 Span.current().setAttribute("mycustomer", "xyz");
@@ -322,7 +322,7 @@ add this property to your json configuration:
 }
 ```
 
-and add `applicationinsights-core` to your application:
+Add `applicationinsights-core` to your application:
 
 ```xml
 <dependency>
@@ -332,7 +332,7 @@ and add `applicationinsights-core` to your application:
 </dependency>
 ```
 
-and use the static `configure(String)` method in the class
+Use the static `configure(String)` method in the class
 `com.microsoft.applicationinsights.connectionstring.ConnectionString`.
 
 > [!NOTE]
@@ -387,7 +387,7 @@ It automatically modifies to return:
 </html>
 ```
 
-The script is aiming at helping customers to track the web user data, and sent the collecting server-side telemetry back to users' Azure portal. Details can be found at [ApplicationInsights-JS](https://github.com/microsoft/ApplicationInsights-JS)
+The script is aiming at helping customers to track the web user data, and sent the collecting server-side telemetry back to users' Azure portal. Details can be found at [ApplicationInsights-JS](https://github.com/microsoft/ApplicationInsights-JS).
 
 If you want to enable this feature, add the below configuration option:
 
@@ -424,8 +424,8 @@ Logging is only captured if it:
 * Meets the configured level for the logging framework.
 * Also meets the configured level for Application Insights.
 
-For example, if your logging framework is configured to log `WARN` (and aforementioned) from the package `com.example`,
-and Application Insights is configured to capture `INFO` (and aforementioned), Application Insights only captures `WARN` (and more severe) from the package `com.example`.
+For example, if your logging framework is configured to log `WARN` (and you configured it as described earlier) from the package `com.example`,
+and Application Insights is configured to capture `INFO` (and you configured as described), Application Insights only captures `WARN` (and more severe) from the package `com.example`.
 
 The default level configured for Application Insights is `INFO`. If you want to change this level:
 
@@ -515,7 +515,7 @@ Also, if your application uses [Spring Boot Actuator](https://docs.spring.io/spr
 
 To send custom metrics using micrometer:
 
-1. Add Micrometer to your application:
+1. Add Micrometer to your application as shown in the following example.
 
     ```xml
     <dependency>
@@ -525,13 +525,13 @@ To send custom metrics using micrometer:
     </dependency>
     ```
 
-1. Use the Micrometer [global registry](https://micrometer.io/?/docs/concepts#_global_registry) to create a meter:
+1. Use the Micrometer [global registry](https://micrometer.io/?/docs/concepts#_global_registry) to create a meter as shown in the following example.
 
     ```java
     static final Counter counter = Metrics.counter("test.counter");
     ```
 
-1. Use the counter to record metrics:
+1. Use the counter to record metrics by using the following command.
 
     ```java
     counter.increment();
@@ -560,9 +560,9 @@ To disable autocollection of Micrometer metrics and Spring Boot Actuator metrics
 }
 ```
 
-## JDBC query masking
+## Java Database Connectivity query masking
 
-Literal values in JDBC queries are masked by default to avoid accidentally capturing sensitive data.
+Literal values in Java Database Connectivity (JDBC) queries are masked by default to avoid accidentally capturing sensitive data.
 
 Starting from 3.4.0, this behavior can be disabled. For example:
 
@@ -774,7 +774,7 @@ The setting applies to the following metrics:
 
 * **Default performance counters**: For example, CPU and memory
 * **Default custom metrics**: For example, garbage collection timing
-* **Configured JMX metrics**: [See the JMX metric section](#jmx-metrics)
+* **Configured JMX metrics**: [See the JMX metric section](#java-management-extensions-metrics)
 * **Micrometer metrics**: [See the Autocollected Micrometer metrics section](#autocollected-micrometer-metrics-including-spring-boot-actuator-metrics)
 
 ## Heartbeat