Fix markdown copyediting issues: spelling, grammar, and formatting (#81)

* Initial plan

* Fix markdown copyediting issues: spelling, grammar, and formatting

Co-authored-by: trask <[email protected]>

* Revert formatting change in docs/README.md and fix error-prone typo

Co-authored-by: trask <[email protected]>

* Revert error-prone typo fix in CONTRIBUTING.md

Co-authored-by: trask <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: trask <[email protected]>

Author: Copilot

CONTRIBUTING.md

@@ -36,13 +36,13 @@ from the OpenTelemetry Java Instrumentation project.
 See the [style guide](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/contributing/style-guideline.md).
 from the OpenTelemetry Java Instrumentation project.
 
-## Running a smoke test in Intellij
+## Running a smoke test in IntelliJ
 
 Pick the smoke test that you want to run, e.g. `MongoTest`.
 If the smoke test is abstract, then pick one of its subclasses, e.g. `MongoTest$Tomcat8Java8Test`.
 Right-click on it and select run.
 
-## Debugging a smoke test in Intellij
+## Debugging a smoke test in IntelliJ
 
 Add `-PsmokeTestRemoteDebug=true` to the gradle args, e.g.
 
@@ -52,7 +52,7 @@ Then create a Remote JVM Debug configuration, e.g.
 
 ![Create a Remote JVM Debug configuration](docs/intellij-debug-smoke-test-part-2.png)
 
-Then run (not debug) the smoke test as above in [Running the smoke tests from Intellij](#running-a-smoke-test-in-intellij).
+Then run (not debug) the smoke test as above in [Running the smoke tests from IntelliJ](#running-a-smoke-test-in-intellij).
 
 The JVM inside the container will wait remote debugger to be attached before starting.
 

agent/agent-profiler/request-triggers.md

@@ -81,7 +81,7 @@ Each individual configuration is formed of:
   supported type).
 - `profileDuration` - The duration in seconds of the profile to be collected when this SLA is
   breached.
-- `threshold` - The threshould applied to the output of the aggregation, if this value is breached a
+- `threshold` - The threshold applied to the output of the aggregation, if this value is breached a
   profile will be triggered, i.e the `breach-ratio` aggregation outputs the percentage of requests
   that breach the SLA, a threshold of 0.95 would trigger a profile if 95% of requests breach the
   SLA.

docs/README.md

@@ -112,5 +112,5 @@ This can be one of:
 
 - `profile-without-env-data` (default value). A profile with certain sensitive events disabled, see
   [Warning](#Warning) section for details.
-- `profile`. Uses the `profile.jfc` jfc configuration that ships with JFR.
+- `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`.

etw/README.md

@@ -37,7 +37,7 @@ Use the project property (`-P` option) `ai.etw.native.build` set to the desired
 
 ## Enabling verbose logging
 
-The property `ai.etw.native.verbose` accepts a boolean value; when true, it enables verbose logging. This is done with preprocessor directives, so it must be rebuilt to enable. This slows execution time significantly under sufficient load. The build throws an error if this property is true for a relase build.
+The property `ai.etw.native.verbose` accepts a boolean value; when true, it enables verbose logging. This is done with preprocessor directives, so it must be rebuilt to enable. This slows execution time significantly under sufficient load. The build throws an error if this property is true for a release build.
 
 * compile
   * Compiles the C++ sources.