From de0e26e8b7e546d5e171644af049d80ae0b9ad19 Mon Sep 17 00:00:00 2001
From: shivkanya9146 <62445341+shivkanya9146@users.noreply.github.com>
Date: Sat, 4 Apr 2020 00:24:07 +0530
Subject: [PATCH] chore: replace @opentelemetry/opentelemetry-context-base with
 @opentelemetry/context-base (#925)

---
 packages/opentelemetry-node/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/opentelemetry-node/README.md b/packages/opentelemetry-node/README.md
index 1a9a40f0cdf..4dd8d84a741 100644
--- a/packages/opentelemetry-node/README.md
+++ b/packages/opentelemetry-node/README.md
@@ -27,7 +27,7 @@ This is done by wrapping all tracing-relevant functions.
 
 This instrumentation code will automatically
 - extract a trace-context identifier from inbound requests to allow distributed tracing (if applicable)
-- make sure that this current trace-context is propagated while the transaction traverses an application (see [@opentelemetry/opentelemetry-context-base](https://github.com/open-telemetry/opentelemetry-js/blob/master/packages/opentelemetry-context-base/README.md) for an in-depth explanation)
+- make sure that this current trace-context is propagated while the transaction traverses an application (see [@opentelemetry/context-base](https://github.com/open-telemetry/opentelemetry-js/blob/master/packages/opentelemetry-context-base/README.md) for an in-depth explanation)
 - add this trace-context identifier to outbound requests to allow continuing the distributed trace on the next hop (if applicable)
 - create and end spans