From ed86f0d2c8c3c5e64d18988a890774445c8ed577 Mon Sep 17 00:00:00 2001
From: buildmaster <buildmaster@springframework.org>
Date: Fri, 24 Feb 2017 16:08:49 +0000
Subject: [PATCH] Sync docs from master to gh-pages

---
 spring-cloud-sleuth.html | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/spring-cloud-sleuth.html b/spring-cloud-sleuth.html
index 6d842cbf4..8f3dd4a3a 100644
--- a/spring-cloud-sleuth.html
+++ b/spring-cloud-sleuth.html
@@ -2626,12 +2626,6 @@ are creating Spans each time a new task is submitted, invoked or scheduled.</p>
 subscribe events. To disable Spring Integration instrumentation, set <code>spring.sleuth.integration.enabled</code> to false.</p>
 </div>
 <div class="paragraph">
-<p>Spring Cloud Sleuth up till version 1.0.4 is sending invalid tracing headers when using messaging. Those headers are actually
-the same as the ones sent in HTTP (they contain a <code>-</code>) in its name. For the sake of
-backwards compatibility in 1.0.4 we&#8217;ve started sending both valid and invalid headers. Please upgrade to 1.0.4 because
-in Spring Cloud Sleuth 1.1 we will remove the support for the deprecated headers.</p>
-</div>
-<div class="paragraph">
 <p>You can provide the <code>spring.sleuth.integration.patterns</code> pattern to explicitly
 provide the names of channels that you want to include for tracing. By default all channels
 are included.</p>