From aaff81dc1895fd7b80e05564cfdeecb790f16352 Mon Sep 17 00:00:00 2001
From: Marcin Grzejszczak <mgrzejszczak@pivotal.io>
Date: Fri, 11 Mar 2016 10:29:00 +0100
Subject: [PATCH] Updated the docs

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

diff --git a/README.adoc b/README.adoc
index 37f7716f3..314c0822d 100644
--- a/README.adoc
+++ b/README.adoc
@@ -152,7 +152,9 @@ notice the `[appname,traceId,spanId,exportable]` entries from the MDC:
     - *spanId* - the id of a specific operation that took place
     - *appname* - the name of the application that logged the span
     - *traceId* - the id of the latency graph that contains the span
-    - *exportable* - whether the log should be exported to Zipkin or not
+    - *exportable* - whether the log should be exported to Zipkin or not. When would you like the span not to be
+    exportable? In the case in which you want to wrap some operation in a Span and have it written to the logs
+    only.
 
 * Provides an abstraction over common distributed tracing data models: traces, spans (forming a DAG), annotations,
 key-value annotations. Loosely based on HTrace, but Zipkin (Dapper) compatible.