Edit review

v-phoebh · web-flow · commit 2fe9aa8cfc6b · 2025-01-10T16:03:05.000+08:00
diff --git a/support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md b/support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md
@@ -254,9 +254,9 @@ You can also try the [monitoring solutions for Java native](/azure/azure-monitor
 - With Quarkus, the Quarkus Opentelemetry Exporter for Microsoft Azure.
 
 
-## Understand duplicated operation ID
+## Understand duplicated operation IDs
 
-Application logic can result in the operation ID to be reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, use one of the following methods:
+Application logic can result in an operation ID being reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, use one of the following methods:
 
 * Enable the capture of the `traceparent` header in the **applicationinsigths.json** file as follows:
 
@@ -271,7 +271,7 @@ Application logic can result in the operation ID to be reused by multiple teleme
         }
       }
     ```
-* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and then restart the application.
+* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and restart the application.
 
     In the following log example, the operation ID comes from an incoming request, not Application Insights:
 

Original file line number	Diff line number	Diff line change
`@@ -254,9 +254,9 @@ You can also try the [monitoring solutions for Java native](/azure/azure-monitor`
`254`	`254`	`- With Quarkus, the Quarkus Opentelemetry Exporter for Microsoft Azure.`
`255`	`255`
`256`	`256`
`257`		`-## Understand duplicated operation ID`
	`257`	`+## Understand duplicated operation IDs`
`258`	`258`
`259`		`-Application logic can result in the operation ID to be reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, use one of the following methods:`
	`259`	`+Application logic can result in an operation ID being reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, use one of the following methods:`
`260`	`260`
`261`	`261`	* Enable the capture of the `traceparent` header in the applicationinsigths.json file as follows:
`262`	`262`
`@@ -271,7 +271,7 @@ Application logic can result in the operation ID to be reused by multiple teleme`
`271`	`271`	`}`
`272`	`272`	`}`
`273`	`273`	```
`274`		`-* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and then restart the application.`
	`274`	`+* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and restart the application.`
`275`	`275`
`276`	`276`	`In the following log example, the operation ID comes from an incoming request, not Application Insights:`
`277`	`277`