Update src/platforms/javascript/common/session-replay/understanding-sessions.mdx

Co-authored-by: Liza Mock <[email protected]>

Author: billyvg

src/platforms/javascript/common/session-replay/understanding-sessions.mdx

@@ -123,8 +123,8 @@ Sentry.init({
 });
 
 // ...
-// Sometime after your users are authenticated, check if they are an employee
-// If they are, we call `replay.flush()` to either flush the replay as normal if session-based replay, or if it is buffering due to error sampling, the flush will send the first segment of the replay.
+// After a user has been authenticated, check if they're an employee
+// If they are, we'll call `replay.flush()` to either flush the replay as normal if it's a session-based replay, or if it's buffering due to error sampling, the flush will send the first segment of the replay.
 
 // Since `replaysOnErrorSampleRate` is 1, we know that a replay has been buffered and `flush()` will flush the contents of that buffer. If both sample rates are < 1, then there is a chance that a replay has not been recording/buffering.
 // In this case, you can check that `replay.getReplayId()` returns a value, if it does, it means replay is active and you can call `replay.flush()`, other call `replay.start()` to start recording a new replay.