From 6112b86ab7de914ec8fa61c9d56ba97f0955212b Mon Sep 17 00:00:00 2001
From: Saisurya Kattamuri <62474785+saisuryakat@users.noreply.github.com>
Date: Wed, 3 Jun 2020 13:36:28 +0700
Subject: [PATCH] Fix incorrect properties used in baggage section (#1662)

---
 docs/src/main/asciidoc/spring-cloud-sleuth.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc
index e9f63c622..2e5eb8bb9 100644
--- a/docs/src/main/asciidoc/spring-cloud-sleuth.adoc
+++ b/docs/src/main/asciidoc/spring-cloud-sleuth.adoc
@@ -90,8 +90,8 @@ Doing so forces the current request to be sampled regardless of configuration.
 Baggage are fields that are propagated with the trace, optionally out of process. You can use
 properties to define fields that have no special configuration such as name mapping:
 
- * `spring.sleuth.remote-fields` is a list of header names to accept and propagate to remote services.
- * `spring.sleuth.local-fields` is a list of names to propagate locally
+ * `spring.sleuth.baggage.remote-fields` is a list of header names to accept and propagate to remote services.
+ * `spring.sleuth.baggage.local-fields` is a list of names to propagate locally
 
 No prefixing applies with these keys. What you set is literally what is used.