From bbc1771625c4fc16e12e2e0489a4c758aef0a7aa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Neum=C3=BCller?= Date: Fri, 5 Jun 2020 08:39:41 +0200 Subject: [PATCH] Reword 'however' sentence. --- specification/trace/api.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/specification/trace/api.md b/specification/trace/api.md index 7721c2ab5eb..53bd933badb 100644 --- a/specification/trace/api.md +++ b/specification/trace/api.md @@ -77,12 +77,14 @@ stateful object that holds any configuration. Normally, the `TracerProvider` is expected to be accessed from a central place. Thus, the API SHOULD provide a way to set/register and access a global default `TracerProvider`. -However, some applications may want to or have to use multiple `TracerProvider` -instances, e.g. to have different settings (like `SpanProcessor`s) for each (and -consequently to the `Tracer`s obtained from them), or because its easier with -dependency injection frameworks. + +Notwithstanding any global `TracerProvider`, some applications may want to or +have to use multiple `TracerProvider` instances, +e.g. to have different configuration (like `SpanProcessor`s) for each +(and consequently for the `Tracer`s obtained from them), +or because its easier with dependency injection frameworks. Thus, implementations of `TracerProvider` SHOULD allow creating an arbitrary -number of instances. +number of `TracerProvider` instances. ### TracerProvider operations