getsentry · philipphofmann · Jan 12, 2026 · Jan 9, 2026 · Jan 9, 2026
@@ -123,7 +123,7 @@ public struct SentryTracedView<Content: View>: View {
     ///
     /// - Parameter viewName: The name that will be used for the span, if nil we try to get the name of the content class.
     /// - Parameter waitForFullDisplay: Indicates whether this view transaction should wait for `SentrySDK.reportFullyDisplayed()`
-    /// in case you need to track some asyncronous task. This is ignored for any `SentryTracedView` that is child of another `SentryTracedView`.
+    /// in case you need to track some asynchronous task. This is ignored for any `SentryTracedView` that is child of another `SentryTracedView`.
     /// If nil, it will use the `enableTimeToFullDisplayTracing` option from the SDK.
     /// - Parameter content: The content that you want to track the performance
     public init(_ viewName: String? = nil, waitForFullDisplay: Bool? = nil, @ViewBuilder content: @escaping () -> Content) {

@@ -21,7 +21,7 @@ import UIKit
     ///   - redactOptions: Options provided to redact sensitive information.
     ///   - enableMaskRendererV2: Flag to enable experimental view renderer.
     /// - Note: The option `enableMaskRendererV2` is an internal flag, which is not part of the public API.
-    ///         Therefore, it is not part of the the `redactOptions` parameter, to not further expose it.
+    ///         Therefore, it is not part of the `redactOptions` parameter, to not further expose it.
     public init(
         renderer: SentryViewRenderer,
         redactOptions: SentryRedactOptions,

@@ -45,7 +45,7 @@ public final class SentryViewScreenshotOptions: NSObject, SentryRedactOptions {
      * this method can be slow, especially when rendering complex views, therefore enabling this flag will switch to render the underlying `CALayer` instead.
      *
      * - Note: This flag can only be used together with `enableViewRendererV2` with up to 20% faster render times.
-     * - Warning: Rendering the view hiearchy using the `CALayer.render(in:)` method can lead to rendering issues, especially when using custom views.
+     * - Warning: Rendering the view hierarchy using the `CALayer.render(in:)` method can lead to rendering issues, especially when using custom views.
      *            For complete rendering, it is recommended to set this option to `false`. In case you prefer performance over completeness, you can
      *            set this option to `true`.
      * - Experiment: This is an experimental feature and is therefore disabled by default. In case you are noticing issues with the experimental
@@ -121,7 +121,7 @@ public final class SentryViewScreenshotOptions: NSObject, SentryRedactOptions {
      * - Warning: This initializer is primarily used by Hybrid SDKs and is not intended for public use.
      */
     convenience init(dictionary: [String: Any]) {
-        // This initalizer is calling the one with optional parameters, so that defaults can be applied
+        // This initializer is calling the one with optional parameters, so that defaults can be applied
         // for absent values.
         self.init(
             enableViewRendererV2: (dictionary["enableViewRendererV2"] as? NSNumber)?.boolValue ?? DefaultValues.enableViewRendererV2,

@@ -188,7 +188,7 @@ public final class SentryReplayOptions: NSObject, SentryRedactOptions {
      * this method can be slow, especially when rendering complex views, therefore enabling this flag will switch to render the underlying `CALayer` instead.
      *
      * - Note: This flag can only be used together with `enableViewRendererV2` with up to 20% faster render times.
-     * - Warning: Rendering the view hiearchy using the `CALayer.render(in:)` method can lead to rendering issues, especially when using custom views.
+     * - Warning: Rendering the view hierarchy using the `CALayer.render(in:)` method can lead to rendering issues, especially when using custom views.
      *            For complete rendering, it is recommended to set this option to `false`. In case you prefer performance over completeness, you can
      *            set this option to `true`.
      * - Experiment: This is an experimental feature and is therefore disabled by default. In case you are noticing issues with the experimental
@@ -293,7 +293,7 @@ public final class SentryReplayOptions: NSObject, SentryRedactOptions {
      * - Warning: This initializer is primarily used by Hybrid SDKs and is not intended for public use.
      */
     @_spi(Private) public convenience init(dictionary: [String: Any]) {
-        // This initalizer is calling the one with optional parameters, so that defaults can be applied
+        // This initializer is calling the one with optional parameters, so that defaults can be applied
         // for absent values.
         self.init(
             sessionSampleRate: (dictionary["sessionSampleRate"] as? NSNumber)?.floatValue,

@@ -3,7 +3,7 @@ import Foundation
 
 /** Parses the custom X-Sentry-Rate-Limits header.
 
- This header exists of a multiple quotaLimits seperated by ",".
+ This header exists of a multiple quotaLimits separated by ",".
  Each quotaLimit exists of retry_after:categories:scope.
  retry_after: seconds until the rate limit expires.
  categories: semicolon separated list of categories. If empty, this limit

@@ -96,7 +96,7 @@
     /// It's crucial for developers to understand that the OS sends a SIGTERM to their app as a prelude
     /// to a graceful shutdown, before resorting to a SIGKILL. This SIGKILL, which your app can't catch
     /// or ignore, is a direct order to terminate your app's process immediately. Developers should be
-    /// aware that their app can receive a SIGTERM in various scenarios, such as  CPU or disk overuse,
+    /// aware that their app can receive a SIGTERM in various scenarios, such as CPU or disk overuse,
     /// watchdog terminations, or when the OS updates your app.
     ///
     /// @note The default value is @c false.