chore(SR): Update Mobile SDK perf pages for SR perf (#12392)

Author: kahest

docs/platforms/android/overhead/index.mdx

@@ -45,5 +45,3 @@ As stated in our <Link to="/product/explore/profiling/performance-overhead">prod
 ## Session Replay
 
 As stated in our <Link to="/product/explore/session-replay/mobile/performance-overhead">product docs on the topic</Link>, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the <PlatformLink to="/session-replay/performance-overhead/">performance overhead docs for this SDK</PlatformLink>.
-
-Note that this feature is still under development and we're working on optimizing performance.

docs/platforms/apple/common/overhead/index.mdx

@@ -56,6 +56,4 @@ As stated in our <Link to="/product/explore/profiling/performance-overhead">prod
 
 As stated in our <Link to="/product/explore/session-replay/mobile/performance-overhead">product docs on the topic</Link>, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the <PlatformLink to="/session-replay/performance-overhead/">performance overhead docs for this SDK</PlatformLink>.
 
-Note that this feature is still under development. We're working on performance improvements to mitigate a known issue where active Session Replay recording can currently introduce slow frames, especially on older iOS devices (for example iPhone 8).
-
 </PlatformSection>

docs/platforms/apple/guides/ios/session-replay/performance-overhead.mdx

@@ -5,7 +5,7 @@ notSupported:
 description: "Learn about how enabling Session Replay impacts the performance of your application."
 ---
 
-If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-ios) app. 
+If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-ios) app.
 
 You can learn more about the various performance overhead optimizations implemented in the iOS Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs.
 
@@ -16,7 +16,7 @@ The Pocket Casts app offers a diverse mix of components, including Fragments, Ac
 - **User Flow:** The same flow was executed 10 times to ensure consistency.
 - **Real-World Representation:** This approach closely mirrors performance in real-world scenarios.
 
-The benchmarks were run on an iPhone 14 Pro.
+The benchmarks were run on an iPhone 14 Pro. Note that active Session Replay recording can introduce slow frames on older lower-end iOS devices (for example iPhone 8).
 
 ### Results
 Below are the results of the benchmarking tests, presented as median values to reflect typical overhead.
@@ -30,5 +30,3 @@ Below are the results of the benchmarking tests, presented as median values to r
 | App Startup Time (Cold)          | 1264.80 ms      | 1265 ms             |
 | Main Thread Time                 | n/a             | 43ms                |
 | Network Bandwidth                | n/a             | 50 KB               |
-
-

docs/platforms/react-native/overhead/index.mdx

@@ -45,5 +45,3 @@ As stated in our <Link to="/product/explore/profiling/performance-overhead">prod
 ## Session Replay
 
 As stated in our <Link to="/product/explore/session-replay/mobile/performance-overhead">product docs on the topic</Link>, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the <PlatformLink to="/session-replay/performance-overhead/">performance overhead docs for this SDK</PlatformLink>.
-
-Note that this feature is still under development. We're working on performance improvements to mitigate a known issue where active Session Replay recording can currently introduce slow frames, especially on older iOS devices (for example iPhone 8).

docs/platforms/react-native/session-replay/performance-overhead.mdx

@@ -5,21 +5,21 @@ notSupported:
 description: "Learn about how enabling Session Replay impacts the performance of your application."
 ---
 
-If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source Pocket Casts app. 
+If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source Pocket Casts app.
 
 You can learn more about the various optimizations implemented in the React Native Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs.
 
 The React Native Replay SDK is a lightweight wrapper for the native iOS and Android SDKs, so its overhead is minimal and doesn't require separate measurement. Below are the benchmark results for each platform.
 
-We measured the overhead using the [Pocket Casts iOS](https://github.com/Automattic/pocket-casts-ios) and [Pocket Casts Android](https://github.com/Automattic/pocket-casts-android) open-source apps. Each includes a diverse set of components such as ViewControllers and SwiftUI screens. 
+We measured the overhead using the [Pocket Casts iOS](https://github.com/Automattic/pocket-casts-ios) and [Pocket Casts Android](https://github.com/Automattic/pocket-casts-android) open-source apps. Each includes a diverse set of components such as ViewControllers and SwiftUI screens.
 
 Here's how the benchmarks were conducted:
 
 - **Configuration:** Full masking was enabled, and optimized release builds were used.
 - **User Flow:** The same flow was executed 10 times to ensure consistency.
 - **Real-World Representation:** This approach closely mirrors performance in real-world scenarios.
 
-The benchmarks were run on an iPhone 14 Pro and a Pixel 2XL.
+The benchmarks were run on an iPhone 14 Pro and a Pixel 2XL. Note that active Session Replay recording can introduce slow frames on older lower-end iOS devices (for example iPhone 8).
 
 ## iOS
 
@@ -44,5 +44,3 @@ The benchmarks were run on an iPhone 14 Pro and a Pixel 2XL.
 | App Startup Time (Cold)          | 1533.35 ms      | 1539.55 ms          |
 | Main Thread Time                 | n/a             | 20ms                |
 | Network Bandwidth                | n/a             | 35 KB               |
-
-