Update Local Scope Documentation

src/includes/enriching-events/scopes/scope-callback-param/java.mdx

@@ -0,0 +1,27 @@
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+import io.sentry.SentryLevel;
+
+// will be tagged with my-tag="my value"
+Sentry.captureException(new Exception("my error"), scope -> {
+  scope.setTag("my-tag", "my value");
+  scope.setLevel(SentryLevel.WARNING);
+});
+
+// will not be tagged with my-tag
+Sentry.captureException(new Exception("my error"));
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+import io.sentry.SentryLevel
+
+// will be tagged with my-tag="my value"
+Sentry.captureException(Exception("my error")) { scope ->
+  scope.setTag("my-tag", "my value")
+  scope.level = SentryLevel.WARNING
+}
+
+// will not be tagged with my-tag
+Sentry.captureException(Exception("my error"))
+```

src/includes/enriching-events/scopes/with-scope/java.mdx

@@ -1,25 +1,41 @@
+<PlatformSection notSupported={["android"]}>
+
 ```java {tabTitle: Java}
 import io.sentry.Sentry;
 import io.sentry.SentryLevel;
 
 Sentry.withScope(scope -> {
-  scope.setLevel(SentryLevel.FATAL);
-  scope.setTransaction("main");
+  scope.setTag("my-tag", "my value");
+  scope.setLevel(SentryLevel.WARNING);
 
-  // This message includes the dataset to the scope in this block:
-  Sentry.captureMessage("Fatal message!");
+  // will be tagged with my-tag="my value"
+  Sentry.captureException(new Exception("my error"));
 });
+
+// will not be tagged with my-tag
+Sentry.captureException(new Exception("my error"));
 ```
 
 ```kotlin {tabTitle: Kotlin}
 import io.sentry.Sentry
 import io.sentry.SentryLevel
 
 Sentry.withScope { scope ->
-  scope.level = SentryLevel.FATAL
-  scope.setTransaction("main")
+  scope.setTag("my-tag", "my value")
+  scope.level = SentryLevel.WARNING
 
-  // This message includes the dataset to the scope in this block:
-  Sentry.captureMessage("Fatal message!")
+  // will be tagged with my-tag="my value"
+  Sentry.captureException(Exception("my error"))
 }
+
+// will not be tagged with my-tag
+Sentry.captureException(Exception("my error"))
 ```
+
+<Alert level="info" title="Important">
+
+In the Java SDK `with-scope` does **not** work reliably in `globalHubMode` as the `scope` gets pushed on the stack global to the hub. In `globalHubMode` use the callback parameter of the capture methods detailed below.
+
+</Alert>
+
+</PlatformSection>

src/platforms/common/enriching-events/scopes.mdx

@@ -93,13 +93,19 @@ You can also apply this configuration when unsetting a user at logout:
 To learn what useful information can be associated with scopes see
 [the context documentation](../context/).
 
-<PlatformSection notSupported={["android"]}>
+<PlatformSection notSupported={["native"]}>
 
 ## Local Scopes
 
 We also support pushing and configuring a scope within a single call. This is typically
-called `with-scope` or `push-scope` depending on the SDK, and is very helpful if
-you only want to send data for one specific event. In the following example we use
+called `with-scope`, `push-scope` or implemented as a function parameter on the capture methods, depending on the SDK. It's very helpful if
+you only want to send data for one specific event.
+
+<PlatformSection supported={["go", "java", "javascript", "php", "python", "ruby", "rust"]} notSupported={["android"]}>
+
+### Using `with-scope`
+
+In the following example we use
 `with-scope` to attach a `level` and a `tag` to only one specific error:
 
 <PlatformContent includePath="enriching-events/scopes/with-scope" />
@@ -123,6 +129,30 @@ caught, and all errors that occur will be silently ignored and **not** reported.
 
 </PlatformSection>
 
+<PlatformSection supported={["apple", "dart", "dotnet", "java", "unreal"]}>
+
+### Using Scope Callback Parameter
+
+In the following example we use the scope callback parameter that is available for all `capture` methods to attach a `level` and a `tag` to only one specific error:
+
+<PlatformContent includePath="enriching-events/scopes/scope-callback-param" />
+
+Before the callback is invoked the SDK creates a clone of the current scope, and the changes
+made will stay isolated within the callback function. This allows you to
+more easily isolate pieces of context information to specific locations in your code or
+even call `clear` to briefly remove all context information.
+
+<Alert level="info" title="Important">
+
+Any exceptions that occur within the callback function for configuring a local scope will not be
+caught, and all errors that occur will be silently ignored and **not** reported.
+
+</Alert>
+
+</PlatformSection>
+
+</PlatformSection>
+
 <PlatformSection supported={["java"]} notSupported={["android"]}>
 
 ## Kotlin Coroutines