diff --git a/docs/platforms/javascript/guides/node/profiling/index.mdx b/docs/platforms/javascript/guides/node/profiling/index.mdx
index 71d28898152e7c..6fb57a956ccc80 100644
--- a/docs/platforms/javascript/guides/node/profiling/index.mdx
+++ b/docs/platforms/javascript/guides/node/profiling/index.mdx
@@ -101,7 +101,7 @@ _(New in version 8.28.0)_
 
 The current profiling implementation stops the profiler automatically after 30 seconds (unless you manually stop it earlier). Naturally, this limitation makes it difficult to get full coverage of your app's execution. We now offer an experimental continuous mode, where profiling data is periodically uploaded while running, with no limit on how long the profiler may run.
 
-To get started with continuous profiling, you can start and stop the profiler directly with `Sentry.profiler.startProfiling` and `Sentry.profiler.stopProfiling`.
+To get started with continuous profiling, you can start and stop the profiler directly with `Sentry.profiler.startProfiler` and `Sentry.profiler.stopProfiler`.
 
 <Note>
 
@@ -116,11 +116,11 @@ Sentry.init({
   dsn: "___PUBLIC_DSN___",
 });
 
-Sentry.profiler.startProfiling();
+Sentry.profiler.startProfiler();
 
 // run some code here
 
-Sentry.profiler.stopProfiling();
+Sentry.profiler.stopProfiler();
 ```
 
 These new APIs do not offer any sampling functionality—every call to start the profiler will run and start sending profiling data. If you are interested in reducing the amount of profiles that run, you must take care to do it at the callsites.