switch the new_api to the be api

open-telemetry · May 5, 2021 · 98a6377 · 98a6377
1 parent 6763ad6
commit 98a6377
Show file tree

Hide file tree

Showing 7 changed files with 1,822 additions and 1,823 deletions.
diff --git a/specification/glossary.md b/specification/glossary.md
@@ -150,7 +150,7 @@ Synonyms: *Instrumenting Library*.
 ### Tracer Name / Meter Name
 
 This refers to the `name` and (optional) `version` arguments specified when
-creating a new `Tracer` or `Meter` (see [Obtaining a Tracer](trace/api.md#tracerprovider)/[Obtaining a Meter](metrics/api.md#meter-interface)).
+creating a new `Tracer` or `Meter` (see [Obtaining a Tracer](trace/api.md#tracerprovider)/[Obtaining a Meter](metrics/api.md#meterprovider)).
 The name/version pair identifies the [Instrumentation Library](#instrumentation-library).
 
 ## Logs

diff --git a/specification/metrics/api.md b/specification/metrics/api.md
diff --git a/specification/metrics/datamodel.md b/specification/metrics/datamodel.md
@@ -169,7 +169,7 @@ compressed format rather than individual timeseries.
 While OpenTelemetry provides flexibility in how instruments can be transformed
 into metric streams, the instruments are defined such that a reasonable default
 mapping can be provided. The exact
-[OpenTelemetry instruments](api.md##metric-instruments) are more fully
+[OpenTelemetry instruments](api.md##instrument) are more fully
 detailed in the API specification.
 
 In the Event model, the primary data are (instrument, number) points, originally