[editorial] Remove implementation detail from Logs Bridge API (#3884)

open-telemetry · Feb 28, 2024 · 6fd4f08 · 6fd4f08
1 parent 8a78903
commit 6fd4f08
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -20,6 +20,8 @@ release.
 
 ### Logs
 
+- Remove implementation detail from Logs Bridge API.
+  ([#3884](https://github.com/open-telemetry/opentelemetry-specification/pull/3884))
 - Clarify that logs attributes are a superset of standard attributes.
   ([#3852](https://github.com/open-telemetry/opentelemetry-specification/pull/3852))
 

diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md
@@ -46,9 +46,6 @@ graph TD
 
 `Logger`s can be accessed with a `LoggerProvider`.
 
-In implementations of the API, the `LoggerProvider` is expected to be the stateful
-object that holds any configuration.
-
 Normally, the `LoggerProvider` is expected to be accessed from a central place.
 Thus, the API SHOULD provide a way to set/register and access a global default
 `LoggerProvider`.