diff --git a/multi/multi__propagation.html b/multi/multi__propagation.html
index 58648a9d5..59db7f498 100644
--- a/multi/multi__propagation.html
+++ b/multi/multi__propagation.html
@@ -56,8 +56,7 @@ With the spring.sleuth.baggage-keys, you set keys t
You can also use the spring.sleuth.propagation-keys property to pass a list of prefixed keys that are whitelisted without any prefix.
Notice that there’s no x- in front of the header keys.
In order to automatically set the baggage values to Slf4j’s MDC, you have to set
the spring.sleuth.log.slf4j.whitelisted-mdc-keys property with a list of whitelisted
-baggage keys. E.g. spring.sleuth.log.slf4j.whitelisted-mdc-keys=foo will set the value of the
-foo baggage into MDC.
The TraceContext.Extractor<C> reads trace identifiers and sampling status from an incoming request or message.
+baggage and propagation keys. E.g. spring.sleuth.log.slf4j.whitelisted-mdc-keys=foo will set the value of the foo baggage into MDC.
![]() | Important |
|---|---|
Remember that adding entries to MDC can drastically decrease the performance of your application! |
The TraceContext.Extractor<C> reads trace identifiers and sampling status from an incoming request or message.
The carrier is usually a request object or headers.
This utility is used in standard instrumentation (such as HttpServerHandler`) but can also be used for custom RPC or messaging code.
TraceContextOrSamplingFlags is usually used only with Tracer.nextSpan(extracted), unless you are
sharing span IDs between a client and a server.
A normal instrumentation pattern is to create a span representing the server side of an RPC.
Extractor.extract might return a complete trace context when applied to an incoming client request.
diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html
index f2e2cde89..a60840972 100644
--- a/single/spring-cloud-sleuth.html
+++ b/single/spring-cloud-sleuth.html
@@ -485,8 +485,7 @@ With the spring.sleuth.baggage-keys, you set keys t
You can also use the spring.sleuth.propagation-keys property to pass a list of prefixed keys that are whitelisted without any prefix.
Notice that there’s no x- in front of the header keys.
In order to automatically set the baggage values to Slf4j’s MDC, you have to set
the spring.sleuth.log.slf4j.whitelisted-mdc-keys property with a list of whitelisted
-baggage keys. E.g. spring.sleuth.log.slf4j.whitelisted-mdc-keys=foo will set the value of the
-foo baggage into MDC.
The TraceContext.Extractor<C> reads trace identifiers and sampling status from an incoming request or message.
+baggage and propagation keys. E.g. spring.sleuth.log.slf4j.whitelisted-mdc-keys=foo will set the value of the foo baggage into MDC.
![]() | Important |
|---|---|
Remember that adding entries to MDC can drastically decrease the performance of your application! |
The TraceContext.Extractor<C> reads trace identifiers and sampling status from an incoming request or message.
The carrier is usually a request object or headers.
This utility is used in standard instrumentation (such as HttpServerHandler`) but can also be used for custom RPC or messaging code.
TraceContextOrSamplingFlags is usually used only with Tracer.nextSpan(extracted), unless you are
sharing span IDs between a client and a server.
A normal instrumentation pattern is to create a span representing the server side of an RPC.
Extractor.extract might return a complete trace context when applied to an incoming client request.
diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml
index 085d6369b..08d568dec 100644
--- a/spring-cloud-sleuth.xml
+++ b/spring-cloud-sleuth.xml
@@ -1060,8 +1060,10 @@ Notice that there’s no