@@ -92,11 +92,11 @@ relay: [`MetricUnit`](https://getsentry.github.io/relay/relay_metrics/enum.Metri
9292
9393## Span Seeking and Span Creating Mode
9494
95- When a metric is emitted it shall either determine the current span (span seeking) or
95+ When a metric is emitted it shall either determine the current span (span seeking) or
9696create a new span (span creating).
9797
9898In ** span seeking** mode, the span is determined based on the current span on the scope.
99- APIs such as ` .increment() ` , ` .distribution() ` , ` .gauge() ` and ` .set() ` operate in span
99+ APIs such as ` .increment() ` , ` .distribution() ` , ` .gauge() ` and ` .set() ` operate in span
100100seeking mode.
101101
102102In ** span creating** mode a new active span is started.
@@ -108,7 +108,7 @@ In span creating mode the span should be setup the following way:
108108* the metric tags should be applied to the span as well
109109* the span is finished once the timing callback finishes
110110
111- From there two things shall be happening unless they are disabled:
111+ From there two things shall be happening unless they are disabled:
112112* ** Common tag attaching:** the tags ` transaction ` , ` release ` and ` environment `
113113 shall be automatically added to the metric.
114114* ** Span local aggregation:** the metric shall be attached to the determined span
@@ -234,7 +234,7 @@ class Distribution:
234234
235235### Gauges
236236
237- Gauges (` g ` ) are generally discouraged. They are often also called "summaries" as they
237+ Gauges (` g ` ) are often also called "summaries" as they
238238are similar in nature to distributions, but somewhat lossy. They are however emitted
239239per span when metric summaries are enabled. As they are hard to aggregate across
240240different emitters they can be tricky to use properly in practice.
0 commit comments