Update docs/product/explore/session-replay/mobile/performance-overhead.mdx

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

Author: romtsn

docs/product/explore/session-replay/mobile/performance-overhead.mdx

@@ -4,9 +4,9 @@ sidebar_order: 30
 description: "Learn about how enabling Session Replay impacts the performance of your application."
 ---
 
-Session Replay for mobile works by taking snapshots of the view hierarchy as well as a screenshot within the same frame, at the rate of one per second. These screenshots are then compressed into a video file representing a segment of the user’s session. All these small segments are then streamed into Sentry with additional trace identifiers, breadcrumbs, and other useful debugging information to compose the full user session.
+Session Replay for mobile captures snapshots of the view hierarchy as well as a screenshot within the same frame once per second. These are compressed into a video file representing parts of the user’s session, then streamed to Sentry with trace identifiers, breadcrumbs, and other debugging information to reconstruct the full session.
 
-In order to perform this work without negatively impacting the host application's performance, Sentry employs a number of measures to minimize additional CPU and memory overhead, record screenshots and view hierarchy in a non-intrusive way and only when necessary, send the absolute minimum number of bytes required, and use low-latency ingestion endpoints geographically close to your end-users.
+To avoid impacting the host's app performance, Sentry minimizes CPU and memory usage by recording screenshots and view hierarchy non-intrusively and only when necessary, sending only essential bytes, and using low-latency ingestion endpoints geographically close to your end-users.
 
 **For most mobile applications, the performance overhead of our Session Replay SDK will be imperceptible to end-users.**