From ba36fa753fdc02753f5664c1efb0dff5e5931259 Mon Sep 17 00:00:00 2001 From: Chris Stavitsky <12092849+cstavitsky@users.noreply.github.com> Date: Mon, 26 Aug 2024 13:37:17 -0700 Subject: [PATCH] Fix broken anchor link `withActiveSpan` (#11129) anchor link was broken --- .../tracing/instrumentation/custom-instrumentation/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx index af5803fecc6b3..04a511a4ca306 100644 --- a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx +++ b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx @@ -30,7 +30,7 @@ In contrast, **inactive spans** will never have children automatically associate A key constraint for active spans is that they can only be made active inside of a callback. This constraint exists because otherwise it becomes impossible to associate spans with the correct parent span when working with asynchronous code. -In places where you are not able to wrap executing code in a callback (e.g. when working with hooks or similar) you have to work with inactive spans, and can combine this with [withActiveSpan](#with-active-span) to manually associate child spans with the correct parent span. +In places where you are not able to wrap executing code in a callback (e.g. when working with hooks or similar) you have to work with inactive spans, and can combine this with [withActiveSpan](#withactivespan) to manually associate child spans with the correct parent span.