Update

Author: buenaflor

docs/platforms/dart/guides/flutter/enriching-events/viewhierarchy/index.mdx

@@ -27,16 +27,16 @@ This callback gives you fine-grained control over view hierarchy captures based
 
 <Alert>
 
-The `debounce` parameter is `true` if the debounce is active.
-If you want to capture view hierarchies regardless of the debounce, you can ignore the `debounce` parameter.
+The `shouldDebounce` parameter is `true` if the debounce is active.
+If you want to capture view hierarchies regardless of the debounce, you can ignore the `shouldDebounce` parameter.
 
 </Alert>
 
-```dart {tabTitle: 'Respect debounce'} {2-9}
+```dart {tabTitle: Respect debounce} {2-9}
 await SentryFlutter.init((options) {
-  options.beforeCaptureViewHierarchy = (event, hint, debounce) async {
+  options.beforeCaptureViewHierarchy = (event, hint, shouldDebounce) async {
     // If debounce is active, skip capturing
-    if (debounce) {
+    if (shouldDebounce) {
       return false;
     }
     // Capture view hierarchy if it's a fatal event
@@ -45,9 +45,9 @@ await SentryFlutter.init((options) {
 });
 ```
 
-```dart {tabTitle: 'Ignore debounce'} {2-4}
+```dart {tabTitle: Ignore debounce} {2-4}
 await SentryFlutter.init((options) {
-  options.beforeCaptureViewHierarchy = (event, hint, debounce) async {
+  options.beforeCaptureViewHierarchy = (event, hint, shouldDebounce) async {
     // Capture view hierarchy if it's a fatal event regardless of debounce
     return event.level == SentryLevel.fatal;
   };

docs/platforms/dart/guides/flutter/features/index.mdx

@@ -46,16 +46,13 @@ Sentry supports Flutter Web as well, with the following limitations:
 - Stack traces aren't symbolicated when compiled using WebAssembly (WASM).
 - Stack traces are not symbolicated when loaded as a browser extension.
 - Offline caching isn't supported for exceptions.
-- <Link to="/product/releases/health">Release Health</Link> isn't supported.
-- Device context data isn't as rich on the web as it is on mobile.
 
 **Desktop Limitations:**
 
 Sentry supports Flutter on Linux and Windows as well, with the following limitations:
 
 - Native crashes are not supported on Windows.
 - [Release Health](/product/releases/health/) isn't supported.
-- Device context data isn't as rich on Linux and Windows as it is on mobile.
 
 When running on macOS, you can expect the same feature set as on iOS.
 

includes/dart-integrations/app-start-instrumentation.mdx

@@ -50,16 +50,6 @@ This instrumentation is automatically enabled. There is no need for further conf
 
 App start instrumentation is designed specifically for pure Flutter applications and requires UI rendering to function properly. If you're using Flutter in an add-to-app integration scenario, the app start metrics will not provide accurate measurements. In such cases, we recommend disabling this instrumentation.
 
-```dart
-// ignore: implementation_imports
-import 'package:sentry_flutter/src/integrations/native_app_start_integration.dart';
-
-// in SentryFlutter.init
-final integration = options.integrations.firstWhere(
-  (integration) => integration is NativeAppStartIntegration);
-options.removeIntegration(integration);
-```
-
 </Alert>
 
 ## Verify
@@ -75,3 +65,18 @@ Open the [sentry.io performance page](https://sentry.io/performance), find, and
 ### 3. View App Start Metrics:
 
 Select the event within your transaction. Sentry displays the app start metrics on the right side of the screen in the **Mobile Vitals** section.
+
+## Disable App Start Instrumentation
+
+To disable the app start instrumentation, you can remove the `NativeAppStartIntegration` from the `integrations` list in your `SentryFlutter.init` call.
+
+```dart
+// ignore: implementation_imports
+import 'package:sentry_flutter/src/integrations/native_app_start_integration.dart';
+
+await SentryFlutter.init((options) {
+  final integration = options.integrations.firstWhere(
+    (integration) => integration is NativeAppStartIntegration);
+  options.removeIntegration(integration);
+});
+```