You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spec/21-http_response_header_format.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ When a participant starts or restarts a trace (that is, when the participant gen
107
107
108
108
A participant that continues a trace started upstream — that is, if the participant uses the `trace-id` value from an incoming `traceparent` header in its own `traceresponse` header — MUST set the `random-trace-id` flag in the `traceresponse` header to the same value that was found in the incoming `traceparent` header.
109
109
110
-
A participant that continues a trace started downstream — that is, if the participant uses the `trace-id` value from a `traceresponse` header it has receieved— MUST set the `random-trace-id` flag in its own `traceresponse` header to the same value that was found in the `traceresponse` header from which the `trace-id` was taken.
110
+
A participant that continues a trace started downstream — that is, if the participant uses the `trace-id` value from a `traceresponse` header it has received— MUST set the `random-trace-id` flag in its own `traceresponse` header to the same value that was found in the `traceresponse` header from which the `trace-id` was taken.
0 commit comments