Skip to content

Commit c350104

Browse files
author
Anuraag Agrawal
committed
Lint
1 parent d4621cf commit c350104

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

specification/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ and across process boundaries. These are propagated from parent to child **Spans
119119

120120
### Links between spans
121121

122-
A **Span** may be linked to zero or more other **Spans** that are causally related.
122+
A **Span** may be linked to zero or more other **Spans** that are causally related.
123123
**Links** can point to **Spans** inside a single **Trace** or across different **Traces**.
124124
**Links** can be used to represent batched operations where a **Span** was
125125
initiated by multiple initiating **Spans**, each representing a single incoming

specification/trace/api.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ Table of Contents
2323
* [Determining the Parent Span from a Context](#determining-the-parent-span-from-a-context)
2424
* [Add Links](#add-links)
2525
* [Span operations](#span-operations)
26-
* [Get Context](#get-context)
2726
* [IsRecording](#isrecording)
2827
* [Set Attributes](#set-attributes)
2928
* [Add Events](#add-events)
@@ -170,7 +169,7 @@ These functions MUST delegate to the `Tracing Context Utilities`.
170169

171170
These parts of the span serve to identify it, both in-process and remotely. They are immutable
172171
pieces of the `Span`, as opposed to the data collecting [span operations](#span-operations).
173-
These identifiers conform to the [W3C TraceContext specification](https://www.w3.org/TR/trace-context/).
172+
These identifiers conform to the [W3C TraceContext specification](https://www.w3.org/TR/trace-context/).
174173
It contains two identifiers - a `TraceId` and a `SpanId` - along with a set of common
175174
`TraceFlags` and system-specific `TraceState` values.
176175

@@ -368,7 +367,7 @@ When a new `Span` is created from a `Context`, the `Context` may contain a `Span
368367
representing the currently active instance, and will be used as parent.
369368
If there is no `Span` in the `Context`, the newly created `Span` will be a root span.
370369

371-
A remote span's [span identifiers](#span-identifiers) can be set as active in a `Context`,
370+
A remote span's [span identifiers](#span-identifiers) can be set as active in a `Context`,
372371
through the use of a [Propagated Span](#propagated-span-creation).
373372
For example, a `Propagator` performing context extraction may need this.
374373

@@ -567,7 +566,7 @@ calling of corresponding API.
567566
### Propagated Span creation
568567

569568
The API MUST provide an operation for creating an object implementing the `Span` interface
570-
provided its identifiers. This is done in order to expose it in operations such as in-process
569+
provided its identifiers. This is done in order to expose it in operations such as in-process
571570
`Span` propagation.
572571

573572
If a new type is required for supporting this operation, it SHOULD be named `PropagatedSpan`.

0 commit comments

Comments
 (0)