From 7c9a178ae0f1d3307cc0c84aa4152261191cf1e3 Mon Sep 17 00:00:00 2001 From: John Watson Date: Thu, 30 Jul 2020 08:50:20 -0700 Subject: [PATCH] Update specification/trace/api.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Christian Neumüller --- specification/trace/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/trace/api.md b/specification/trace/api.md index 51fbc757f0c..325a0485ae8 100644 --- a/specification/trace/api.md +++ b/specification/trace/api.md @@ -692,7 +692,7 @@ requested parent SpanContext: * A valid `SpanContext` is specified as the parent of the new `Span`: The API MUST treat this parent context as the context for the newly created `Span`. This means that a `SpanContext` that has been provided by a configured `Propagator` -will be propagated through the resulting call stack, but that no new `SpanContext`s will be created. +will be propagated through to any child span, but that no new `SpanContext`s will be created. * No valid `SpanContext` is specified as the parent of the new `Span`: The API MUST create an non-valid (both SpanID and TradeID are all zeros) `Span` for use by the API caller. This means that both the `TraceID` and the `SpanID` should be invalid.