Revert false positives

Author: szepeviktor

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

@@ -6,7 +6,7 @@ sidebar_order: 9000
 
 ## "Missing API declaration" after App Store review
 
-Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITEMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/apple/data-management/apple-privacy-manifest) guide.
+Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/apple/data-management/apple-privacy-manifest) guide.
 
 ## Wrong App Start Data
 

docs/platforms/dart/guides/flutter/troubleshooting.mdx

@@ -16,7 +16,7 @@ Please read the [Android developer documentation](https://developer.android.com/
 
 ## "Missing API declaration" after App Store review
 
-Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITEMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/dart/guides/flutter/data-management/apple-privacy-manifest) guide.
+Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/dart/guides/flutter/data-management/apple-privacy-manifest) guide.
 
 ## Known Limitations
 

docs/platforms/dotnet/guides/aspnetcore/index.mdx

@@ -26,8 +26,8 @@ Install-Package Sentry.AspNetCore -Version {{@inject packages.version('sentry.do
 dotnet add package Sentry.AspNetCore -v {{@inject packages.version('sentry.dotnet.aspnetcore') }}
 ```
 
-```shell {tabTitle:Packet CLI}
-packet add Sentry --version {{@inject packages.version('sentry.dotnet.aspnetcore') }}
+```shell {tabTitle:Paket CLI}
+paket add Sentry --version {{@inject packages.version('sentry.dotnet.aspnetcore') }}
 ```
 
 This package extends [Sentry.Extensions.Logging](/platforms/dotnet/guides/extensions-logging/). This means that besides the ASP.NET Core related features, through this package you'll also get access to all the framework's logging integration and also the features available in the main [Sentry](/platforms/dotnet/) SDK.

docs/platforms/dotnet/index.mdx

@@ -47,8 +47,8 @@ Install the **NuGet** package to add the Sentry dependency:
   Install-Package Sentry -Version {{@inject packages.version('sentry.dotnet') }}
   ```
 
-  ```shell {tabTitle:Packet CLI}
-  packet add Sentry --version {{@inject packages.version('sentry.dotnet') }}
+  ```shell {tabTitle:Paket CLI}
+  paket add Sentry --version {{@inject packages.version('sentry.dotnet') }}
 ```
 </OnboardingOption>
 
@@ -70,9 +70,9 @@ Install the **NuGet** package to add the Sentry dependency:
   Install-Package Sentry.Profiling -Version {{@inject packages.version('sentry.dotnet.profiling') }}
   ```
 
-  ```shell {tabTitle:Packet CLI}
-  packet add Sentry --version {{@inject packages.version('sentry.dotnet') }}
-  packet add Sentry.Profiling --version {{@inject packages.version('sentry.dotnet.profiling') }}
+  ```shell {tabTitle:Paket CLI}
+  paket add Sentry --version {{@inject packages.version('sentry.dotnet') }}
+  paket add Sentry.Profiling --version {{@inject packages.version('sentry.dotnet.profiling') }}
     ```
 </OnboardingOption>
 

docs/platforms/javascript/common/user-feedback/configuration/index__v7.x.mdx

@@ -58,20 +58,20 @@ feedbackIntegration({
 
 Most text that you see in the default Feedback widget can be customized.
 
-| Key                  | Default                                | Description                                                        |
-| -------------------- | -------------------------------------- | ------------------------------------------------------------------ |
-| `buttonLabel`        | `Report a Bug`                         | The label of the injected button.                                  |
-| `submitButtonLabel`  | `Send Bug Report`                      | The label of the submit button used in the feedback form.          |
-| `cancelButtonLabel`  | `Cancel`                               | The label of the cancel button used in the feedback form.          |
-| `formTitle`          | `Report a Bug`                         | The title at the top of the feedback form.                         |
-| `nameLabel`          | `Name`                                 | The label of the name input field.                                 |
-| `namePlaceholder`    | `Your Name`                            | The placeholder for the name input field.                          |
-| `emailLabel`         | `Email`                                | The label of the email input field.                                |
-| `emailPlaceholder`   | `[email protected]`               | The placeholder for the email input field.                         |
-| `messageLabel`       | `Description`                          | The label for the feedback description input field.                |
-| `messagePlaceholder` | `What's the bug? What did you expect?` | The placeholder for the feedback description input field.          |
+| Key                  | Default                                | Description                                                         |
+| -------------------- | -------------------------------------- | ------------------------------------------------------------------- |
+| `buttonLabel`        | `Report a Bug`                         | The label of the injected button.                                   |
+| `submitButtonLabel`  | `Send Bug Report`                      | The label of the submit button used in the feedback form.           |
+| `cancelButtonLabel`  | `Cancel`                               | The label of the cancel button used in the feedback form.           |
+| `formTitle`          | `Report a Bug`                         | The title at the top of the feedback form.                          |
+| `nameLabel`          | `Name`                                 | The label of the name input field.                                  |
+| `namePlaceholder`    | `Your Name`                            | The placeholder for the name input field.                           |
+| `emailLabel`         | `Email`                                | The label of the email input field.                                 |
+| `emailPlaceholder`   | `[email protected]`               | The placeholder for the email input field.                          |
+| `messageLabel`       | `Description`                          | The label for the feedback description input field.                 |
+| `messagePlaceholder` | `What's the bug? What did you expect?` | The placeholder for the feedback description input field.           |
 | `successMessageText` | `Thank you for your report!`           | The message to be displayed after a successful feedback submission. |
-| `isRequiredText`     | `(required)`                           | The text displayed next to a required field.       |
+| `isRequiredText`     | `(required)`                           | The text displayed next to a required field.                        |
 
 Example of customization:
 

docs/platforms/javascript/guides/cloudflare/frameworks/astro.mdx

@@ -11,26 +11,26 @@ After installing the Sentry Astro SDK, you can now install the Sentry Cloudflare
 
 <PlatformContent includePath="getting-started-install" />
 
-To use the SDK, you'll need to set either the `nodejs_also` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
+To use the SDK, you'll need to set either the `nodejs_als` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
 needs access to the `AsyncLocalStorage` API to work correctly.
 
 ```jsonc {tabTitle:JSON} {filename:wrangler.jsonc}
 {
   "compatibility_flags": [
-    "nodejs_also",
+    "nodejs_als",
     // "nodejs_compat"
   ],
 }
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
-compatibility_flags = ["nodejs_also"]
+compatibility_flags = ["nodejs_als"]
 # compatibility_flags = ["nodejs_compat"]
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
 compatibility_flags = ["nodejs_compat"]
-# compatibility_flags = ["nodejs_also"]
+# compatibility_flags = ["nodejs_als"]
 ```
 
 Then create a `functions` directory and add a `_middleware.js` file to it with the following code:

docs/platforms/javascript/guides/cloudflare/frameworks/remix.mdx

@@ -23,20 +23,20 @@ Now you can install the Sentry Cloudflare SDK. First, install the SDK with your
 
 <PlatformContent includePath="getting-started-install" />
 
-To use the SDK, you'll need to set either the `nodejs_also` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
+To use the SDK, you'll need to set either the `nodejs_als` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
 needs access to the `AsyncLocalStorage` API to work correctly.
 
 ```jsonc {tabTitle:JSON} {filename:wrangler.jsonc}
 {
   "compatibility_flags": [
-    "nodejs_also",
+    "nodejs_als",
     // "nodejs_compat"
   ],
 }
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
-compatibility_flags = ["nodejs_also"]
+compatibility_flags = ["nodejs_als"]
 # compatibility_flags = ["nodejs_compat"]
 ```
 

docs/platforms/javascript/guides/cloudflare/frameworks/sveltekit.mdx

@@ -23,20 +23,20 @@ If you installed the SDK before, make sure that `@sentry/sveltekit` version `9.2
 
 ## 2. Cloudflare configuration
 
-To use the SDK, you'll need to set either the `nodejs_also` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
+To use the SDK, you'll need to set either the `nodejs_als` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
 needs access to the `AsyncLocalStorage` API to work correctly.
 
 ```jsonc {tabTitle:JSON} {filename:wrangler.jsonc}
 {
   "compatibility_flags": [
-    "nodejs_also",
+    "nodejs_als",
     // "nodejs_compat"
   ],
 }
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
-compatibility_flags = ["nodejs_also"]
+compatibility_flags = ["nodejs_als"]
 # compatibility_flags = ["nodejs_compat"]
 ```
 

docs/platforms/javascript/guides/hono/index.mdx

@@ -42,20 +42,20 @@ yarn add @sentry/cloudflare
 pnpm add @sentry/cloudflare
 ```
 
-To use the SDK, you'll need to set either the `nodejs_also` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
+To use the SDK, you'll need to set either the `nodejs_als` or `nodejs_compat` compatibility flags in your `wrangler.jsonc`/`wrangler.toml` config. This is because the SDK
 needs access to the `AsyncLocalStorage` API to work correctly.
 
 ```jsonc {tabTitle:JSON} {filename:wrangler.jsonc}
 {
   "compatibility_flags": [
-    "nodejs_also",
+    "nodejs_als",
     // "nodejs_compat"
   ],
 }
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
-compatibility_flags = ["nodejs_also"]
+compatibility_flags = ["nodejs_als"]
 # compatibility_flags = ["nodejs_compat"]
 ```
 
@@ -109,21 +109,21 @@ yarn add @sentry/cloudflare
 pnpm add @sentry/cloudflare
 ```
 
-To use the SDK, you'll need to set either the `nodejs_compat` or `nodejs_also` compatibility flags in your `wrangler.toml`/`wrangler.json`.
+To use the SDK, you'll need to set either the `nodejs_compat` or `nodejs_als` compatibility flags in your `wrangler.toml`/`wrangler.json`.
 This is because the SDK needs access to the `AsyncLocalStorage` API to work correctly.
 
 ```jsonc {tabTitle:JSON} {filename:wrangler.jsonc}
 {
   "compatibility_flags": [
     "nodejs_compat",
-    // "nodejs_also"
+    // "nodejs_als"
   ],
 }
 ```
 
 ```toml {tabTitle:Toml} {filename:wrangler.toml}
 compatibility_flags = ["nodejs_compat"]
-# compatibility_flags = ["nodejs_also"]
+# compatibility_flags = ["nodejs_als"]
 ```
 
 Next, add the `sentryPagesPlugin` as

docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx

@@ -10,7 +10,7 @@ If you need additional help, [ask on GitHub](https://github.com/getsentry/sentry
 
 ## "Missing API declaration" after App Store review
 
-Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITEMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest) guide.
+Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest) guide.
 
 ## Tests Not Working
 

docs/platforms/native/advanced-usage/signal-handling/index.mdx

@@ -28,7 +28,7 @@ In the context of the Native SDK, we are only interested in signals that will re
 
 * `SIGSEGV`: The process tried to access an invalid virtual memory "segment".
 * `SIGBUS`: The process tried to access an invalid physical address or a VM page failed to "page-in".
-* `SIGABRT`: Raised when `abort()` was called. This is the only signal handled on Windows (and only by the `crashpad` backend) because calling `abort()` bypasses Structured Exception Handling ([`SHE`](https://learn.microsoft.com/en-us/windows/win32/debug/structured-exception-handling)).
+* `SIGABRT`: Raised when `abort()` was called. This is the only signal handled on Windows (and only by the `crashpad` backend) because calling `abort()` bypasses Structured Exception Handling ([`SEH`](https://learn.microsoft.com/en-us/windows/win32/debug/structured-exception-handling)).
 * `SIGFPE`: An erroneous arithmetic operation occurred in the CPU.
 * `SIGILL`: The process attempted to execute an illegal (often privileged) processor instruction.
 * `SIGTRAP`: This is typically used to inform debuggers when execution hits a breakpoint instruction (`int 3`, `brk`, etc.). Instrumentation tools and sanitizers also sometimes issue breakpoints.

docs/platforms/native/common/enriching-events/screenshots/index.mdx

@@ -5,7 +5,7 @@ description: "Learn more about taking screenshots when an error occurs. Sentry p
 
 Sentry makes it possible to automatically take a screenshot and include it as an <PlatformLink to="/enriching-events/attachments/">attachment</PlatformLink> when a user experiences an error, an exception, or a crash.
 
-This feature is currently only available on Windows and has a few limitations. For example, the `inproc` and `breakpad` backends use local exception handlers for capturing the screenshot and therefore rely on the exception handler being called. Only the `crashpad` backend with an external handler process is able to capture screenshots of fast-fail crashes that bypass Structured Exception Handling ([`SHE`](https://learn.microsoft.com/en-us/windows/win32/debug/structured-exception-handling)). Another example where a screenshot might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
+This feature is currently only available on Windows and has a few limitations. For example, the `inproc` and `breakpad` backends use local exception handlers for capturing the screenshot and therefore rely on the exception handler being called. Only the `crashpad` backend with an external handler process is able to capture screenshots of fast-fail crashes that bypass Structured Exception Handling ([`SEH`](https://learn.microsoft.com/en-us/windows/win32/debug/structured-exception-handling)). Another example where a screenshot might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
 ## Enabling Screenshots
 

docs/platforms/python/legacy-sdk/integrations.mdx

@@ -1268,7 +1268,7 @@ To use with Sentry, use the Sentry handler tag:
 </logger>
 ```
 
-This configuration retains normal logging to a logfile, but adds Sentry logging for ERRORRs.
+This configuration retains normal logging to a logfile, but adds Sentry logging for ERRORs.
 
 All options of `raven.base.Client` are supported.
 
@@ -1338,7 +1338,7 @@ Zope has extensible logging configuration options. A basic instance (not ZEO cli
 </eventlog>
 ```
 
-This configuration retains normal logging to a logfile, but adds Sentry logging for ERRORRs.
+This configuration retains normal logging to a logfile, but adds Sentry logging for ERRORs.
 
 All options of `raven.base.Client` are supported.
 

docs/platforms/unreal/configuration/setup-crashreporter/index.mdx

@@ -45,7 +45,7 @@ Sentry SDK can integrate with the UE Crash Reporter, but it also offers addition
 | Supported engine versions    | All UE 5 and UE 4.27       | Built-in engine tool   |
 | Supported platforms          | Desktop, mobile, consoles  | Desktop                |
 | Crash capturing *            | Supported **               | Supported              |
-| Additional event context      | Supported                  | Supported              |
+| Additional event context     | Supported                  | Supported              |
 | Automatic breadcrumbs        | Supported                  | Not supported          |
 | Screenshot attachment        | Supported ***              | Not supported          |
 | Crash events filtering       | Supported                  | Not supported          |

docs/security-legal-pii/security/ssl.mdx

@@ -38,7 +38,7 @@ Supported ciphers:
 - TLS_RSA_WITH_AES_256_GCM_SHA384
 - TLS_RSA_WITH_AES_128_CBC_SHA
 - TLS_RSA_WITH_AES_256_CBC_SHA
-- TLS_RSA_WITH_3DES_EDGE_CBC_SHA
+- TLS_RSA_WITH_3DES_EDE_CBC_SHA
 
 This suite of protocols and ciphers represents Sentry's official support; however, clients may experience an agreement on individual ciphers that exceed the strength ratings of those listed above.
 

platform-includes/configuration/before-send/native.mdx

@@ -71,6 +71,6 @@ The Crashpad backend on macOS doesn't currently support notifying the crashing p
 
 <Alert level="warning" title="Limitations in Crashpad on Windows for Fast-fail Crashes">
 
-The Crashpad backend on Windows supports fast-fail crashes, which bypass SHE (Structured Exception Handling) primarily for security reasons. `sentry-native` registers a WER (Windows Error Reporting) module, which signals the `crashpad_handler` to send a minidump when a fast-fail crash occurs. However, since this process bypasses SHE, the application local exception handler is no longer invoked, which also means that for these kinds of crashes, `before_send` and `on_crash` will not be invoked before sending the minidump and thus have no effect.
+The Crashpad backend on Windows supports fast-fail crashes, which bypass SEH (Structured Exception Handling) primarily for security reasons. `sentry-native` registers a WER (Windows Error Reporting) module, which signals the `crashpad_handler` to send a minidump when a fast-fail crash occurs. However, since this process bypasses SEH, the application local exception handler is no longer invoked, which also means that for these kinds of crashes, `before_send` and `on_crash` will not be invoked before sending the minidump and thus have no effect.
 
 </Alert>

platform-includes/getting-started-install/dotnet.aspnetcore.mdx

@@ -12,8 +12,8 @@ Install-Package Sentry.AspNetCore
 dotnet add package Sentry.AspNetCore
 ```
 
-Packet:
+Paket:
 
 ```shell
-packet add Sentry.AspNetCore
+paket add Sentry.AspNetCore
 ```

platform-includes/getting-started-install/dotnet.mdx

@@ -8,6 +8,6 @@ dotnet add package Sentry -v {{@inject packages.version('sentry.dotnet') }}
 Install-Package Sentry -Version {{@inject packages.version('sentry.dotnet') }}
 ```
 
-```shell {tabTitle:Packet CLI}
-packet add Sentry --version {{@inject packages.version('sentry.dotnet') }}
+```shell {tabTitle:Paket CLI}
+paket add Sentry --version {{@inject packages.version('sentry.dotnet') }}
 ```