Merge branch 'master' of github.com:getsentry/sentry-docs into smi/quick-start/react-manual-tracing

Author: inventarSarah

develop-docs/sdk/data-model/event-payloads/contexts.mdx

@@ -8,7 +8,7 @@ related to the current user and the environment. For example, the device or
 application version. Its canonical name is `contexts`.
 
 The `contexts` type can be used to define arbitrary contextual data on the
-event. It accepts an object of key/value pairs. The key is the “alias” of the
+event. It accepts an object of key/value pairs. The key is the "alias" of the
 context and can be freely chosen. However, as per policy, it should match the
 type of the context unless there are two values for a type. You can omit `type`
 if the key name is the type.
@@ -273,7 +273,7 @@ To summarize:
 
 : _Optional_. Typically provides the full name, full version, and release alias. This maps to `PRETTY_NAME` in [`/etc/os-release`](https://www.freedesktop.org/software/systemd/man/latest/os-release.html#PRETTY_NAME=) (examples: `Ubuntu 22.04.4 LTS`, `Raspian GNU/Linux 10 (buster)`).
 
-### Example OS Context
+**Example OS Context**
 
 The OS Context for the 3 major OSs should look like this:
 
@@ -468,7 +468,7 @@ Examples: `"Apple Metal"` or `"Direct3D11"`
 
 : _Optional_. Are geometry shaders available on the device?
 
-### Example GPU Context
+**Example GPU Context**
 
 ```json
 {
@@ -496,7 +496,7 @@ The `type` and default key is `"state"`.
 
 : **Required**. Object with two keys: _Optional_ `type` for naming the state library (e.g.: Redux, MobX, Vuex) and **Required** `value` that holds the state object.
 
-### Example State Context
+**Example State Context**
 
 ```json
 {
@@ -598,7 +598,7 @@ The `type` and default key is `"cloud_resource"`.
 
 - Example: `t4g.medium`
 
-### Example Cloud Resource Context
+**Example Cloud Resource Context**
 
 The following example illustrates the contexts part of the <Link to="/sdk/data-model/event-payloads/">event payload</Link> and omits other attributes for simplicity.
 
@@ -720,7 +720,7 @@ The `route` currently supports the following predefined fields if it's a map:
 
 If the route is set to a string (e.g. `"route": "foo"`), it will be normalized into a map (e.g. `"route": {"name": "foo"}`) server-side.
 
-### Example Trace Context
+**Example Trace Context**
 
 ```json
 {
@@ -766,7 +766,7 @@ envelope endpoint.
 
 : **Required**. The replay_id associated with the event.
 
-### Example Replay Context
+**Example Replay Context**
 
 ```json
 {
@@ -792,7 +792,7 @@ This is mostly set on transactions in a web server environment where one transac
 
 - Example: `200`
 
-### Example Response Context
+**Example Response Context**
 
 ```json
 {
@@ -822,7 +822,7 @@ The required field is `package` which should contain the package or framework wh
 
 - Example: `true`
 
-### Example Response Context
+**Example Response Context**
 
 ```json
 {
@@ -852,7 +852,7 @@ The feature flag context contains information about the flags evaluated prior to
 - Example: `false`
 
 
-### Example Feature Flag Context
+**Example Feature Flag Context**
 
 ```json
 {

docs/platforms/android/tracing/instrumentation/perf-v2.mdx

@@ -4,44 +4,41 @@ sidebar_order: 11
 description: "Learn how to get even more insights into Android app performance"
 ---
 
-<Alert>
+Performance V2 contains a set of features that enrich performance instrumentation. It tightly integrates with the [Mobile Vitals](/product/insights/mobile/mobile-vitals/) Insights module, enabling <PlatformLink to="/tracing/instrumentation/perf-v2/#app-start">App Start</PlatformLink> and <PlatformLink to="/tracing/instrumentation/perf-v2/#frames-delay">Frames Delay</PlatformLink> reporting.
 
-This feature is marked as _experimental_.
-Supported in Sentry's Android SDK version `7.4.0` and above.
-
-</Alert>
-
-Performance V2 is a set of features which enrich your existing instrumentation, giving you more insights into potential performance bottlenecks. These features tightly integrate with the [Mobile Vitals](/product/insights/mobile/mobile-vitals/) insights module.
+Since version 8 of the SDK, Performance V2 is generally available and enabled by default. In versions `7.4.0..<8.0.0`, this feature is available as _experimental_ and you need to opt in to use it:
 
 ### Enabling Performance V2
 
-```java {filename:MyApplication.java}
+```java {filename:MyApplication.java} {4}
 import io.sentry.android.core.SentryAndroid;
 
 SentryAndroid.init(this, options -> {
   options.setEnablePerformanceV2(true);
 });
 ```
 
-```kotlin {filename:MyApplication.kt}
+```kotlin {filename:MyApplication.kt} {4}
 import io.sentry.android.core.SentryAndroid
 
 SentryAndroid.init(this) { options ->
   options.enablePerformanceV2 = true
 }
 ```
 
-```xml {filename:AndroidManifest.xml}
+```xml {filename:AndroidManifest.xml} {3-5}
 <manifest>
     <application>
-        <meta-data android:name="io.sentry.performance-v2.enable" android:value="true" />
+        <meta-data
+          android:name="io.sentry.performance-v2.enable"
+          android:value="true" />
     </application>
 </manifest>
 ```
 
 ### App Start
 
-Besides enabling performance-v2, this feature requires the <PlatformLink to="/configuration/gradle/">Sentry Android Gradle Plugin</PlatformLink> (version `4.2.0` or above) to be applied to your app module.
+Besides enabling Performance V2, this feature requires the <PlatformLink to="/configuration/gradle/">Sentry Android Gradle Plugin</PlatformLink> (version `4.2.0` or above) to be applied to your app module.
 
 Once enabled, your App Start transaction will show a detailed span breakdown of various components:
 * `process.load`: The process initialization time

docs/platforms/java/common/source-context/index.mdx

@@ -20,4 +20,4 @@ Next, calculate the derived file path. Take the frame `module` and replace all `
 
 Finally, compare the derived with the path found in your source repository. In this example, the `com/example/vu/android/` folder may match the `src/com/example/vu/android/` folder in the source code. Using that information, set the **Stack Trace Root** to `com/example/vu/android/` and the **Source Code Root** to `src/com/example/vu/android/`. This tells Sentry to replace all file paths beginning in `com/example/vu/android/` with `src/com/example/vu/android/` when searching for the source code.
 
-Because Sentry will use the first matching code mapping, it is recommended to always provide a non-empty value for the **Stack Trace Root** when possible. An empty value in the **Stack Trace Root** will match all file paths, which will work poorly if multiple code mapprings are required.
+Because Sentry will use the first matching code mapping, it is recommended to always provide a non-empty value for the **Stack Trace Root** when possible. An empty value in the **Stack Trace Root** will match all file paths, which will work poorly if multiple code mappings are required.