link to v8

getsentry · Sep 19, 2024 · f0bda97 · f0bda97
1 parent 2ccdfbe
commit f0bda97
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/includes/profiling-node-runtime-flags.mdx b/includes/profiling-node-runtime-flags.mdx
@@ -1,6 +1,6 @@
 
 ## Runtime Flags
-There are three runtime flags you can set that control the behavior of the profiler. Two of the flags relate to how the SDK resolves the profiler binaries. The third alters how the underlying profiler is initialized by v8.
+There are three runtime flags you can set that control the behavior of the profiler. Two of the flags relate to how the SDK resolves the profiler binaries. The third alters how the underlying profiler is initialized by [v8](https://v8docs.nodesource.com/).
 
 <Note>
 These flags are intended for advanced use cases only. Setting them isn't required for most use cases.
@@ -9,7 +9,7 @@ These flags are intended for advanced use cases only. Setting them isn't require
 - SENTRY_PROFILER_BINARY_PATH
 
 This flag sets the profiler binary path and bypasses arch, platform, and libc checks. It can be useful in some build configurations if you want to override which binary is required at runtime.
-    
+
 - SENTRY_PROFILER_BINARY_DIR
 
 Acts similarly to the flag above, however, this flag only specifies the directory where the binaries are located and defers to the runtime to resolve the correct binary depending on the arch, platform, and libc version.