Update java-standalone-profiler.md

Author: ktoliver

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

@@ -22,7 +22,7 @@ The Application Insights Java Profiler provides a system for:
 
 The Application Insights Java profiler uses the JFR profiler provided by the JVM to record profiling data, allowing users to download the JFR recordings at a later time and analyze them to identify the cause of performance issues.
 
-This data is gathered on demand when trigger conditions are met. The available triggers are thresholds over CPU usage, Memory consumption, and Request (service-level agreement triggers). Request triggers monitor Spans generated by Open Telemetry and allow the user to configure service-level agreement (SLA) requirements over the duration of those Spans.
+This data is gathered on demand when trigger conditions are met. The available triggers are thresholds over CPU usage, Memory consumption, and Request (service-level agreement triggers). Request triggers monitor Spans generated by OpenTelemetry and allow the user to configure service-level agreement (SLA) requirements over the duration of those Spans.
 
 When a threshold is reached, a profile of the configured type and duration is gathered and uploaded. This profile is then visible within the performance pane of the associated Application Insights Portal UI.
 
@@ -171,22 +171,22 @@ Example configuration:
 
 - `profile-without-env-data` (default value). A profile with certain sensitive events disabled, see Warning section for details.
 - `profile`. Uses the `profile.jfc` configuration that ships with JFR.
-- A path to a custom jfc configuration file on the file system, i.e `/tmp/myconfig.jfc`.
+- A path to a custom jfc configuration file on the file system, for example, `/tmp/myconfig.jfc`.
 
 `cpuTriggeredSettings` This configuration is used if a cpu profile is requested.
 This value can be one of:
 
 - `profile-without-env-data` (default value). A profile with certain sensitive events disabled, see Warning section for details.
 - `profile`. Uses the `profile.jfc` jfc configuration that ships with JFR.
-- A path to a custom jfc configuration file on the file system, i.e `/tmp/myconfig.jfc`.
+- A path to a custom jfc configuration file on the file system, for example, `/tmp/myconfig.jfc`.
 
 `manualTriggeredSettings` This configuration is used if a manual profile is requested.
 This value can be one of:
 
 - `profile-without-env-data` (default value). A profile with certain sensitive events disabled, see
   Warning section for details.
 - `profile`. Uses the `profile.jfc` jfc configuration that ships with JFR.
-- A path to a custom jfc configuration file on the file system, i.e `/tmp/myconfig.jfc`.
+- A path to a custom jfc configuration file on the file system, for example, `/tmp/myconfig.jfc`.
 
 `enableRequestTriggering` Whether JFR profiling should be triggered based on request configuration.
 This value can be one of: