diff --git a/multi/multi__span_lifecycle.html b/multi/multi__span_lifecycle.html index 4f4b7153d..f68933a72 100644 --- a/multi/multi__span_lifecycle.html +++ b/multi/multi__span_lifecycle.html @@ -22,7 +22,7 @@ Your names have to be explicit and concrete. Big names lead to latency issues an situation might be as follows:

To continue a span, you can use brave.Tracer, as shown in the following example:

// let's assume that we're in a thread Y and we've received
 // the `initialSpan` from thread X
-Span continuedSpan = this.tracer.joinSpan(newSpan.context());
+Span continuedSpan = this.tracer.toSpan(newSpan.context());
 try {
 	// ...
 	// You can tag a span
diff --git a/single/spring-cloud-sleuth.html b/single/spring-cloud-sleuth.html
index ccd9440e6..056cff6c0 100644
--- a/single/spring-cloud-sleuth.html
+++ b/single/spring-cloud-sleuth.html
@@ -538,7 +538,7 @@ Your names have to be explicit and concrete. Big names lead to latency issues an
 situation might be as follows:

To continue a span, you can use brave.Tracer, as shown in the following example:

// let's assume that we're in a thread Y and we've received
 // the `initialSpan` from thread X
-Span continuedSpan = this.tracer.joinSpan(newSpan.context());
+Span continuedSpan = this.tracer.toSpan(newSpan.context());
 try {
 	// ...
 	// You can tag a span
diff --git a/spring-cloud-sleuth.xml b/spring-cloud-sleuth.xml
index 28396e1b4..fe4d871d4 100644
--- a/spring-cloud-sleuth.xml
+++ b/spring-cloud-sleuth.xml
@@ -1210,7 +1210,7 @@ It is in fact merely a technical implementation detail that you would not necess
 To continue a span, you can use brave.Tracer, as shown in the following example:
 // let's assume that we're in a thread Y and we've received
 // the `initialSpan` from thread X
-Span continuedSpan = this.tracer.joinSpan(newSpan.context());
+Span continuedSpan = this.tracer.toSpan(newSpan.context());
 try {
 	// ...
 	// You can tag a span