update CHANGELOG, updates

Author: JWinermaSplunk

CHANGELOG.md

@@ -17,6 +17,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   ([#3796](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3796))
 
 ### Added
+- `opentelemetry-instrumentation-structlog`: Add new package providing `StructlogHandler` and `StructlogInstrumentor` to bridge structlog into the OpenTelemetry Logs SDK pipeline with trace context correlation and exception capture.
+  ([#4286](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/4286))
 - `opentelemetry-instrumentation`: botocore: Add support for AWS Secrets Manager semantic convention attribute
   ([#3765](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3765))
 - Add `rstcheck` to pre-commit to stop introducing invalid RST

instrumentation/opentelemetry-instrumentation-structlog/src/opentelemetry/instrumentation/structlog/__init__.py

@@ -76,7 +76,6 @@
 }
 
 # Mapping from stdlib log levels to OTel severity numbers
-# Based on the SDK's LoggingHandler implementation
 _STD_TO_OTEL = {
     10: SeverityNumber.DEBUG,
     11: SeverityNumber.DEBUG2,
@@ -128,7 +127,6 @@
 def std_to_otel(levelno: int) -> SeverityNumber:
     """
     Map python log levelno to OTel log severity number.
-    Based on the SDK's LoggingHandler implementation.
     """
     if levelno < 10:
         return SeverityNumber.UNSPECIFIED
@@ -272,8 +270,7 @@ def flush(self) -> None:
         Flush the logger provider.
 
         This method flushes any pending logs. It runs in a separate thread
-        to avoid potential deadlocks, following the pattern from the SDK's
-        LoggingHandler.
+        to avoid potential deadlocks.
         """
         if hasattr(self._logger_provider, "force_flush") and callable(
             self._logger_provider.force_flush