From 02157f447ac7b4dfd7ceced3c6808cf512c680f0 Mon Sep 17 00:00:00 2001 From: Federico Bond Date: Fri, 23 Feb 2024 16:14:25 -0300 Subject: [PATCH] docs: update OpenTelemetry hook README (#49) Signed-off-by: Federico Bond --- hooks/openfeature-hooks-opentelemetry/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hooks/openfeature-hooks-opentelemetry/README.md b/hooks/openfeature-hooks-opentelemetry/README.md index 6b2d28d..ca5d713 100644 --- a/hooks/openfeature-hooks-opentelemetry/README.md +++ b/hooks/openfeature-hooks-opentelemetry/README.md @@ -18,7 +18,7 @@ More information on hooks can be found in the [OpenFeature documentation][hook-c ### Register Globally -The `TracingHook` can be set on the OpenFeature singleton. This will ensure that every flag evaluation will always create a span event, if am active span is available. +The `TracingHook` can be set globally. This will ensure that every flag evaluation will always create a span event, if an active span is available. ```python from openfeature import api @@ -29,7 +29,7 @@ api.add_hooks(TracingHook()) ### Register Per Client -The `TracingHook` can be set on an individual client. This should only be done if it wasn't set globally and other clients shouldn't use this hook. Setting the hook on the client will ensure that every flag evaluation performed by this client will always create a span event, if an active span is available. +The `TracingHook` can also be set on an individual client. This should only be done if it wasn't set globally and other clients shouldn't use this hook. Setting the hook on the client will ensure that every flag evaluation performed by this client will always create a span event, if an active span is available. ```python from openfeature import api