chore: adjust changesets and readme

Author: iivvaannxx

.changeset/add-versioning-policy.md

@@ -0,0 +1,5 @@
+---
+"@adobe/aio-lib-telemetry": patch
+---
+
+Add [versioning policy](https://github.com/adobe/aio-lib-telemetry/blob/main/README.md#versioning-policy) to the README.

.changeset/updated-otel-deps.md

@@ -2,6 +2,4 @@
 "@adobe/aio-lib-telemetry": patch
 ---
 
-[[BREAKING]](https://github.com/adobe/aio-lib-telemetry/blob/main/README.md#versioning-policy) Update OpenTelemetry dependencies (see the [Renovate PR](https://github.com/adobe/aio-lib-telemetry/pull/62) for the full list).
-
-Add [versioning policy](https://github.com/adobe/aio-lib-telemetry/blob/main/README.md#versioning-policy) to the README.
+[[BREAKING]](https://github.com/adobe/aio-lib-telemetry/blob/main/README.md#versioning-policy) Update OpenTelemetry dependencies (see the [Renovate PR](https://github.com/adobe/aio-lib-telemetry/pull/62) for the full list). The `otel` entrypoint no longer re-exports the `NoopLogRecordProcessor` class, as it's no longer exported by the OpenTelemetry Logs SDK. If you were using it, removing it should be safe, as it basically does nothing and it's the same as not using the processor at all.

README.md

@@ -18,17 +18,17 @@ npm install @adobe/aio-lib-telemetry
 
 ## Versioning Policy
 
-This library follows [semantic versioning](https://semver.org/) with one important exception: **breaking changes to the `otel` endpoint do not trigger major version releases**.
+This library follows [semantic versioning](https://semver.org/) with one important exception: **breaking changes to the `otel` entrypoint do not trigger major version releases**.
 
-The [`otel` endpoint](./docs/api-reference/README.md#opentelemetry-api) re-exports OpenTelemetry APIs, which remain experimental and receive frequent updates that may include breaking changes. Strictly adhering to semantic versioning would require releasing a new major version with each OpenTelemetry update, which would be disruptive given their rapid release cadence.
+The [`otel` entrypoint](./docs/api-reference/README.md#opentelemetry-api) re-exports OpenTelemetry APIs, which remain experimental and receive frequent updates that may include breaking changes. Strictly adhering to semantic versioning would require releasing a new major version with each OpenTelemetry update, which would be disruptive given their rapid release cadence.
 
 **Our versioning approach:**
 
 - **Major versions** are reserved for breaking changes to our library's own API
-- **Minor/patch versions** may include breaking changes to the `otel` endpoint
+- **Minor/patch versions** may include breaking changes to the `otel` entrypoint
 - All breaking changes, including those in `otel`, are documented in release notes with a `[BREAKING]` label
 
-**Recommendation:** Always review release notes before upgrading, especially if you use the `otel` endpoint directly.
+**Recommendation:** Always review release notes before upgrading, especially if you use the `otel` entrypoint directly.
 
 ## Usage