From cf8250762bf4dcfdf95bd5391516d97602fca3e3 Mon Sep 17 00:00:00 2001
From: Marcin Grzejszczak <mgrzejszczak@pivotal.io>
Date: Wed, 16 Mar 2016 16:14:07 +0100
Subject: [PATCH] Updated docs

---
 README.adoc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.adoc b/README.adoc
index 4e436fe2f..9ef1b433e 100644
--- a/README.adoc
+++ b/README.adoc
@@ -169,6 +169,10 @@ latency in your applications. Sleuth is written to not log too much, and to not
 * Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints,
 rest template, scheduled actions, message channels, zuul filters, feign client).
 
+* Sleuth includes default logic to join a trace across http or messaging boundaries. For example, http propagation
+works via Zipkin-compatible request headers. This propagation logic is defined and customized via
+`SpanInjector` and `SpanExtractor` implementations.
+
 * Provides simple metrics of accepted / dropped spans.
 
 * If `spring-cloud-sleuth-zipkin` then the app will generate and collect Zipkin-compatible traces.