diff --git a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
index b2cb7f5435c1e..74ab625f10106 100644
--- a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
+++ b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
@@ -85,7 +85,7 @@ replay.start();
 replay.startBuffering();
 ```
 
-This can be used either if both `replaysSessionSampleRate` and `replaysOnErrorSampleRate` are `0` and thus no session has been started automatically, or if you previously stopped a session and want to start a new one (see below). `start()` and `startBuffering()` will throw an error if a session is currently running.
+This can be used either if both `replaysSessionSampleRate` and `replaysOnErrorSampleRate` are `0` and thus no session has been started automatically, or if you previously stopped a session and want to start a new one (see below). `start()` and `startBuffering()` will [log a debug message](/platforms/javascript/configuration/options/#debug) if a session is currently running.
 
 ## Manually Stopping Replay
 
@@ -107,7 +107,7 @@ await replay.flush();
 
 In `session` mode, this will upload any pending recording data to Sentry. In `buffer` mode, this will upload any pending recording data to Sentry and then continue recording, the same as when an error is sampled with `replaysOnErrorSampleRate`.
 
-Note that it's safe to call `flush()` at any time, even if Session Replay is stopped, in which case, it will do nothing.
+Calling `flush()` while Session Replay is stopped will start a new session recording.
 
 ## Examples of Custom Sampling