diff --git a/multi/multi__features.html b/multi/multi__features.html
index 5055ba30a..d11ea2dbd 100644
--- a/multi/multi__features.html
+++ b/multi/multi__features.html
@@ -5,7 +5,7 @@
2016-02-02 15:31:01.936 INFO [bar,46ab0d418373cbc9,46ab0d418373cbc9,false] 23030 --- [nio-8081-exec-4] ...
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.
When would you like the span not to be exportable?
When 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, and key-value annotations.
-Spring Cloud Slwuth is loosely based on HTrace but is compatible with Zipkin (Dapper).Sleuth records timing information to aid in latency analysis.
+Spring Cloud Sleuth is loosely based on HTrace but is compatible with Zipkin (Dapper).Sleuth records timing information to aid in latency analysis.
By using sleuth, you can pinpoint causes of latency in your applications.Sleuth is written to not log too much and to not cause your production application to crash.
To that end, Sleuth:
- Propagates structural data about your call graph in-band and the rest out-of-band.
- Includes opinionated instrumentation of layers such as HTTP.
- Includes a sampling policy to manage volume.
- Can report to a Zipkin system for query and visualization.
Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).Sleuth includes default logic to join a trace across HTTP or messaging boundaries.
For example, HTTP propagation works over Zipkin-compatible request headers.
diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html
index 231bebf4d..f594197f2 100644
--- a/single/spring-cloud-sleuth.html
+++ b/single/spring-cloud-sleuth.html
@@ -237,7 +237,7 @@ dependencies {
2016-02-02 15:31:01.936 INFO [bar,46ab0d418373cbc9,46ab0d418373cbc9,false] 23030 --- [nio-8081-exec-4] ...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.
When would you like the span not to be exportable?
When 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, and key-value annotations.
-Spring Cloud Slwuth is loosely based on HTrace but is compatible with Zipkin (Dapper).Sleuth records timing information to aid in latency analysis.
+Spring Cloud Sleuth is loosely based on HTrace but is compatible with Zipkin (Dapper).Sleuth records timing information to aid in latency analysis.
By using sleuth, you can pinpoint causes of latency in your applications.Sleuth is written to not log too much and to not cause your production application to crash.
To that end, Sleuth:
- Propagates structural data about your call graph in-band and the rest out-of-band.
- Includes opinionated instrumentation of layers such as HTTP.
- Includes a sampling policy to manage volume.
- Can report to a Zipkin system for query and visualization.
Instruments common ingress and egress points from Spring applications (servlet filter, async endpoints, rest template, scheduled actions, message channels, Zuul filters, and Feign client).Sleuth includes default logic to join a trace across HTTP or messaging boundaries.
For example, HTTP propagation works over Zipkin-compatible request headers.
diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml
index 347446fde..aa70afe08 100644
--- a/spring-cloud-sleuth.xml
+++ b/spring-cloud-sleuth.xml
@@ -615,7 +615,7 @@ When you want to wrap some operation in a Span and have it written to the logs o
Provides an abstraction over common distributed tracing data models: traces, spans (forming a DAG), annotations, and key-value annotations.
-Spring Cloud Slwuth is loosely based on HTrace but is compatible with Zipkin (Dapper).
+Spring Cloud Sleuth is loosely based on HTrace but is compatible with Zipkin (Dapper).
Sleuth records timing information to aid in latency analysis.