diff --git a/content/en/real_user_monitoring/application_monitoring/ios/setup.md b/content/en/real_user_monitoring/application_monitoring/ios/setup.md
index eff0ad04543..bbad359f2fd 100644
--- a/content/en/real_user_monitoring/application_monitoring/ios/setup.md
+++ b/content/en/real_user_monitoring/application_monitoring/ios/setup.md
@@ -40,7 +40,7 @@ This page describes how to instrument your iOS and tvOS applications for [Real U
 
 ## Prerequisites
 
-Before you begin, ensure you have:
+Before you begin, you need:
 - Xcode 12.0 or later
 - iOS 11.0+ or tvOS 11.0+ deployment target
 - A Datadog account with RUM or Error Tracking enabled
@@ -112,16 +112,16 @@ DatadogRUM.xcframework
 ### Step 2 - Specify application details in the UI
 
 1. Navigate to [**Digital Experience** > **Add an Application**][10].
-2. Select `iOS` as the application type and enter an application name to generate a unique Datadog application ID and client token.
+2. Select `iOS` as the application type and enter an application name to generate a unique application ID and client token.
 3. To instrument your web views, click the **Instrument your webviews** toggle. For more information, see [Web View Tracking][11].
 
 ### Step 3 - Initialize the library
 
 In the initialization snippet, set an environment name, service name, and client token.
 
-The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. The `AppDelegate` is your app's main entry point that handles app lifecycle events. 
+The SDK should be initialized as early as possible in the app life cycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. The `AppDelegate` is your app's main entry point that handles app life cycle events. 
 
-This ensures the SDK can correctly capture all measurements, including application startup duration. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`.
+Initializing here allows the SDK to correctly capture all measurements, including application startup duration. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`.
 
 <div class="alert alert-warning">Initializing the SDK elsewhere (for example later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.</div>
 
@@ -515,6 +515,33 @@ struct BarView: View {
 }
 ```
 
+## Verify your setup
+
+After completing setup, verify that the iOS SDK is correctly sending data to Datadog.
+
+### Check the Xcode console
+
+Enable verbose SDK logging to confirm data is being sent. Add the following in the `DEBUG` build configuration only:
+
+```swift
+Datadog.verbosityLevel = .debug
+```
+
+After running your app, look for output similar to the following in the Xcode debugger console:
+
+```
+[DATADOG SDK] 🐶 → 17:23:09.849 [DEBUG] ⏳ (rum) Uploading batch...
+[DATADOG SDK] 🐶 → 17:23:10.972 [DEBUG]    → (rum) accepted, won't be retransmitted: success
+```
+
+**Note**: Remove `Datadog.verbosityLevel` before building for Release.
+
+### View your data in Datadog
+
+After running your app, navigate to the [RUM Explorer][8] to see sessions from your application. You should see session data within a few minutes.
+
+To view crash reports and iOS errors, navigate to [**Error Tracking**][15]. For more details on crash analysis with symbolicated stack traces, see [iOS Crash Reporting and Error Tracking][7].
+
 ## Track iOS errors
 
 [iOS Crash Reporting and Error Tracking][7] displays any issues in your application and the latest available errors. You can view error details and attributes including JSON in the [RUM Explorer][8].
@@ -529,17 +556,17 @@ To disable automatic user data collection for client IP or geolocation data:
 2. Click **User Data Collection**.
 3. Use the toggles for those settings. For more information, see [RUM iOS Data Collected][12].
 
-To ensure the safety of your data, you must use a client token. Using only [Datadog API keys][2] to configure the `dd-sdk-ios` library would expose them client-side in your iOS application's byte code.
+Use a client token to help protect your data. Using only [Datadog API keys][2] to configure the `dd-sdk-ios` library would expose them client-side in your iOS application's byte code.
 
 For more information about setting up a client token, see the [Client token documentation][3].
 
 ## Sending data when device is offline
 
-The iOS SDK ensures availability of data when your user device is offline. In cases of low-network areas, or when the device battery is too low, all events are first stored on the local device in batches. They are sent as soon as the network is available, and the battery is high enough to ensure the iOS SDK does not impact the end user's experience. If the network is not available while your application is in the foreground, or if an upload of data fails, the batch is kept until it can be sent successfully.
+The iOS SDK maintains data availability when your user device is offline. In cases of low-network areas or low battery, all events are first stored on the local device in batches. Batches are sent when the network is available and the battery is sufficient. If a network upload fails, the batch is kept until it can be sent successfully.
 
 This means that even if users open your application while offline, no data is lost.
 
-**Note**: The data on the disk is automatically discarded if it gets too old to ensure the iOS SDK does not use too much disk space.
+**Note**: The data on the disk is automatically discarded if it gets too old, helping the iOS SDK avoid using too much disk space.
 
 ## Supported versions
 
@@ -563,3 +590,4 @@ See [Supported versions][9] for a list of operating system versions and platform
 [12]: /real_user_monitoring/ios/data_collected/
 [13]: https://app.datadoghq.com/rum/application/
 [14]: /real_user_monitoring/application_monitoring/agentic_onboarding/?tab=realusermonitoring
+[15]: https://app.datadoghq.com/rum/error-tracking