Fix typo "the the" -> "the"

chromy · chromy · commit b0810c8207e5 · 2025-05-15T12:32:32.000+01:00
diff --git a/develop-docs/sdk/telemetry/sessions/index.mdx b/develop-docs/sdk/telemetry/sessions/index.mdx
@@ -517,7 +517,7 @@ Sessions should be enabled by default, a session is started as soon as a request
 #### Lifetime of a Session
 
 Sessions are never tracked nor sent individually, instead they are aggregated and the aggregates are sent every 30s and a final time when the web server is terminating.
-As an implementation hint to the point above, when a "Client" is closed or flushed the associated "Session Flusher" shall also be flushed and submit the current aggregates the the transport, before the transport is flushed/closed.
+As an implementation hint to the point above, when a "Client" is closed or flushed the associated "Session Flusher" shall also be flushed and submit the current aggregates the transport, before the transport is flushed/closed.
 Make sure this works reasonably for Serverless — there we shall not use "request mode" and SessionFlusher because we cannot have any work that happens outside of the request-response flow.
 Provide an easy way to integrate with existing Node frameworks (Express, Next.js, Koa).
 
diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx
@@ -78,7 +78,7 @@ Also, the queries prioritize `AND` before `OR`. For example, "x `AND` y `OR` z"
 
 ### Multiple Values on the Same Key
 
-You can search multiple values for the same key by putting the values in a list. For example, "x:[value1, value2]" will find the the same results as "x:value1 `OR` x:value2". When you do this, the search returns issues/events that match any search term.
+You can search multiple values for the same key by putting the values in a list. For example, "x:[value1, value2]" will find the same results as "x:value1 `OR` x:value2". When you do this, the search returns issues/events that match any search term.
 
 An example of searching on the same key with a list of values:
 
diff --git a/docs/concepts/search/searchable-properties/events.mdx b/docs/concepts/search/searchable-properties/events.mdx
@@ -637,7 +637,7 @@ The "package" the frame was contained in. Depending on the platform, this can be
 
 ### `sum(numeric field)`
 
-Returns results with a matching total value for the the field entered.
+Returns results with a matching total value for the field entered.
 
 - **Type:** matches field
 
diff --git a/docs/platforms/android/migration/index.mdx b/docs/platforms/android/migration/index.mdx
@@ -442,7 +442,7 @@ SentryOptions#addEventProcessor(object : EventProcessor {
 })
 ```
 
-A random generated `installationId` replaces `Settings.Secure.ANDROID_ID`, which has been removed. This may affect the number of unique users displayed on the the Issues page and Alerts.
+A random generated `installationId` replaces `Settings.Secure.ANDROID_ID`, which has been removed. This may affect the number of unique users displayed on the Issues page and Alerts.
 If you always set a custom user using `Sentry.setUser(customUser)`, the behavior has not changed. While you don't have to make any update, if you want to maintain the old behavior, use the following code snippet:
 
 ```java
diff --git a/docs/platforms/dart/guides/flutter/migration.mdx b/docs/platforms/dart/guides/flutter/migration.mdx
@@ -42,7 +42,7 @@ There are no Flutter specific breaking changes. However there are some in [sentr
 
 You may remove `android:extractNativeLibs="true"` meta-data in the `AndroidManifest` file or `android.bundle.enableUncompressedNativeLibs=false` in the `gradle.properties` file if you're using the [Android Native Development Kit](/platforms/android/configuration/using-ndk/). Sentry can now symbolicate events with the default value of [extractNativeLibs](https://developer.android.com/studio/releases/gradle-plugin#extractNativeLibs) and [android.bundle.enableUncompressedNativeLibs](https://developer.android.com/studio/releases/gradle-plugin#behavior-changes).
 
-A random generated installationId replaces [Settings.Secure.ANDROID_ID](https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID), which has been removed. This may affect the number of unique users displayed on the the Issues page and Alerts. If you always set a custom user using Sentry.setUser(customUser), the behavior has not changed. While you don't have to make any update, if you want to maintain the old behavior, use the following code snippet.
+A random generated installationId replaces [Settings.Secure.ANDROID_ID](https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID), which has been removed. This may affect the number of unique users displayed on the Issues page and Alerts. If you always set a custom user using Sentry.setUser(customUser), the behavior has not changed. While you don't have to make any update, if you want to maintain the old behavior, use the following code snippet.
 It makes use of the [device_info_plus](https://pub.dev/packages/device_info_plus) plugin:
 
 
diff --git a/docs/platforms/java/common/maven/index.mdx b/docs/platforms/java/common/maven/index.mdx
@@ -38,7 +38,7 @@ Using Maven in your application module's `pom.xml` add:
 
 ### Configure
 
-We expose the following configuration values, by adding a `<configuration>` section to the the plugin in `pom.xml`:
+We expose the following configuration values, by adding a `<configuration>` section to the plugin in `pom.xml`:
 
 ```xml
 <project>
diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx
@@ -213,7 +213,7 @@ Options used to configure the transport. This is an object with the following po
 - `headers`: An object containing headers to be sent with every request.
 - `proxy`: A proxy used for outbound requests. Can be http or https.
 - `caCerts`: A path or list of paths to a CA certificate, or a buffer of CA certificates.
-- `httpModule`: A custom HTTP module to use for requests. Defaults to the the native `http` and `https` modules.
+- `httpModule`: A custom HTTP module to use for requests. Defaults to the native `http` and `https` modules.
 - `keepAlive`: Determines whether to keep the socket alive between requests. Defaults to `false`.
 
 </PlatformCategorySection>
diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx
@@ -91,7 +91,7 @@ Sentry.replayCanvasIntegration({
 ```
 
 **Step 2**
-Call the the following `snapshot()` method inside your application's paint loop. `snapshot()` needs to be called in the same execution loop as the canvas draw commands, otherwise you may be snapshotting empty canvas buffers. This is due to how WebGL works when `preserveDrawingBuffer` is `false`.
+Call the following `snapshot()` method inside your application's paint loop. `snapshot()` needs to be called in the same execution loop as the canvas draw commands, otherwise you may be snapshotting empty canvas buffers. This is due to how WebGL works when `preserveDrawingBuffer` is `false`.
 
 ```javascript
 function paint() {
diff --git a/docs/platforms/react-native/migration/before-v5.mdx b/docs/platforms/react-native/migration/before-v5.mdx
@@ -131,7 +131,7 @@ The breaking changes are relevant only to Android. There are no breaking changes
 
 Sentry React Native version `2.5.0` depends on Sentry Android `5.0.0`. Please [refer to the Android migration guide for Android-specific changes](/platforms/android/migration/#migrating-from-iosentrysentry-android-430-to-iosentrysentry-android-500).
 
-`Settings.Secure.ANDROID_ID` has been removed and replaced with a randomly-generated `installationId`. This may affect the number of unique users displayed on the the Issues page and Alerts. If you've always set a custom user using `Sentry.setUser(customUser)`, the behavior hasn't changed. While you don't have to make any updates, if you want to maintain the old behavior, use the following code snippet which makes use of the [react-native-device-info](https://github.com/react-native-device-info/react-native-device-info) library.
+`Settings.Secure.ANDROID_ID` has been removed and replaced with a randomly-generated `installationId`. This may affect the number of unique users displayed on the Issues page and Alerts. If you've always set a custom user using `Sentry.setUser(customUser)`, the behavior hasn't changed. While you don't have to make any updates, if you want to maintain the old behavior, use the following code snippet which makes use of the [react-native-device-info](https://github.com/react-native-device-info/react-native-device-info) library.
 
 ```javascript
 import { Platform } from "react-native";
diff --git a/docs/product/explore/discover-queries/query-builder/query-equations.mdx b/docs/product/explore/discover-queries/query-builder/query-equations.mdx
@@ -103,7 +103,7 @@ Get the percentage of transactions that completed within a threshold
 
 ### Calculate a custom Apdex
 
-[Apdex](/product/insights/overview/metrics/#apdex) is defined as `(satisfied + tolerable*0.5 + frustrated*0)/total`. If you wanted to change the the weight of tolerable to 0.2, you would create the following query and equation.
+[Apdex](/product/insights/overview/metrics/#apdex) is defined as `(satisfied + tolerable*0.5 + frustrated*0)/total`. If you wanted to change the weight of tolerable to 0.2, you would create the following query and equation.
 
 1. Create a new query with the following four columns:
    - Column 1:
diff --git a/docs/product/issues/issue-details/performance-issues/function-regressions.mdx b/docs/product/issues/issue-details/performance-issues/function-regressions.mdx
@@ -37,4 +37,4 @@ The before and after values also link to example profiles you can examine to ide
 
 ## Example Profiles
 
-The "Example Profiles" section shows a list of example profiles where you can find the the regressed function from before and after the regression.
+The "Example Profiles" section shows a list of example profiles where you can find the regressed function from before and after the regression.
diff --git a/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx b/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx
@@ -4,7 +4,7 @@ sidebar_order: 30
 description: "Learn more about Large Render Blocking Assets and how to diagnose and fix them."
 ---
 
-A _Large Render Blocking Asset_ is a performance problem that happens when a large asset causes a delay in displaying the page content. For example, if a page includes a stylesheet, and the browser pauses page rendering until the the entire stylesheet downloads and processes. If that stylesheet is large, the user may see a blank or unstyled screen for a long time. This problem occurs when applications don't split up asset files, load non-essential assets synchronously, or load assets too early.
+A _Large Render Blocking Asset_ is a performance problem that happens when a large asset causes a delay in displaying the page content. For example, if a page includes a stylesheet, and the browser pauses page rendering until the entire stylesheet downloads and processes. If that stylesheet is large, the user may see a blank or unstyled screen for a long time. This problem occurs when applications don't split up asset files, load non-essential assets synchronously, or load assets too early.
 
 ## Detection Criteria
 
