Fix Javadoc in SpanHandler (#1293)

A link was missing the `@` marker and thus would not render correctly. Additionally, 'abrupt' was unconventionally used as a verb ; replaced it with 'disrupt'.
openzipkin · Dec 15, 2023 · bad97d4 · bad97d4
1 parent b95cbf9
commit bad97d4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/brave/src/main/java/brave/handler/SpanHandler.java b/brave/src/main/java/brave/handler/SpanHandler.java
@@ -30,11 +30,11 @@
  *
  * <p>A {@link TraceContext} could be recorded twice, for example, if a long operation
  * began, called {@link Span#flush()} (recording 1) and later called {@link Span#finish()}
- * (recording 2). A {@link TraceContext} could be abrupted by garbage collection resulting in a
+ * (recording 2). A {@link TraceContext} could be disrupted by garbage collection resulting in a
  * {@link Cause#ABANDONED}. A user could even {@linkplain Cause#ABANDONED abandon} a span without
  * recording anything!
  *
- * <p>Collectors that process finished spans will need to look at the {link Cause} and {@link
+ * <p>Collectors that process finished spans will need to look at the {@link Cause} and {@link
  * MutableSpan} collected. For example, {@link Cause#FINISHED} is usually a good enough heuristic to
  * find complete spans.
  *