Remove the recommendation to not synchronize access to Config.disabled (#4310)

Author: pellared

CHANGELOG.md

@@ -16,16 +16,22 @@ release.
 
 - Add in-development support for `otlp/stdout` exporter via `OTEL_TRACES_EXPORTER`.
   ([#4183](https://github.com/open-telemetry/opentelemetry-specification/pull/4183))
+- Remove the recommendation to not synchronize access to `TracerConfig.disabled`.
+  ([#4310](https://github.com/open-telemetry/opentelemetry-specification/pull/4310))
 
 ### Metrics
 
 - Add in-development support for `otlp/stdout` exporter via `OTEL_METRICS_EXPORTER`.
   ([#4183](https://github.com/open-telemetry/opentelemetry-specification/pull/4183))
+- Remove the recommendation to not synchronize access to `MeterConfig.disabled`.
+  ([#4310](https://github.com/open-telemetry/opentelemetry-specification/pull/4310))
 
 ### Logs
 
 - Add in-development support for `otlp/stdout` exporter via `OTEL_LOGS_EXPORTER`.
  ([#4183](https://github.com/open-telemetry/opentelemetry-specification/pull/4183))
+- Remove the recommendation to not synchronize access to `LoggerConfig.disabled`.
+  ([#4310](https://github.com/open-telemetry/opentelemetry-specification/pull/4310))
 
 ### Events
 

specification/logs/sdk.md

@@ -190,9 +190,7 @@ It consists of the following parameters:
   is [Enabled](./api.md#enabled). If `disabled` is `true`, `Enabled`
   returns `false`. If `disabled` is `false`, `Enabled` returns `true`. It is not
   necessary for implementations to ensure that changes to `disabled` are
-  immediately visible to callers of `Enabled`. I.e. atomic, volatile,
-  synchronized, or equivalent memory semantics to avoid stale reads are
-  discouraged to prioritize performance over immediate consistency.
+  immediately visible to callers of `Enabled`.
 
 ## Additional LogRecord interfaces
 

specification/metrics/sdk.md

@@ -973,9 +973,7 @@ default `MeterConfig.disabled=false` and instruments use the default
 aggregation when no matching views match the instrument.
 
 It is not necessary for implementations to ensure that changes
-to `MeterConfig.disabled` are immediately visible to callers of `Enabled`. I.e.
-atomic, volatile, synchronized, or equivalent memory semantics to avoid stale
-reads are discouraged to prioritize performance over immediate consistency.
+to `MeterConfig.disabled` are immediately visible to callers of `Enabled`.
 
 ## Attribute limits
 

specification/trace/sdk.md

@@ -184,9 +184,7 @@ It consists of the following parameters:
   is [Enabled](./api.md#enabled). If `disabled` is `true`, `Enabled`
   returns `false`. If `disabled` is `false`, `Enabled` returns `true`. It is not
   necessary for implementations to ensure that changes to `disabled` are
-  immediately visible to callers of `Enabled`. I.e. atomic, volatile,
-  synchronized, or equivalent memory semantics to avoid stale reads are
-  discouraged to prioritize performance over immediate consistency.
+  immediately visible to callers of `Enabled`.
 
 ## Additional Span Interfaces