diff --git a/assets/images/real-device-app-testing/App_Manager_r1.png b/assets/images/real-device-app-testing/App_Manager_r1.png
new file mode 100644
index 000000000..207b01e47
Binary files /dev/null and b/assets/images/real-device-app-testing/App_Manager_r1.png differ
diff --git a/assets/images/real-device-app-testing/App_Manager_r2.png b/assets/images/real-device-app-testing/App_Manager_r2.png
new file mode 100644
index 000000000..f7c3689e9
Binary files /dev/null and b/assets/images/real-device-app-testing/App_Manager_r2.png differ
diff --git a/assets/images/real-device-app-testing/App_Manager_r3.png b/assets/images/real-device-app-testing/App_Manager_r3.png
new file mode 100644
index 000000000..9580805f5
Binary files /dev/null and b/assets/images/real-device-app-testing/App_Manager_r3.png differ
diff --git a/docs/app-auto-network-throttling.md b/docs/app-auto-network-throttling.md
index 52a3edd08..017d9e7d5 100644
--- a/docs/app-auto-network-throttling.md
+++ b/docs/app-auto-network-throttling.md
@@ -125,17 +125,14 @@ To utilize the **networkProfile** capability, ensure that you include `network:
     ```python
     driver.execute_script("updateNetworkProfile=offline")
     ```
+:::note
+Currently, for iOS, we do not support any capability or LambdaHook for offline mode.
+:::
 
-#### iOS
-
-- **LambdaHook:** You can also switch to offline mode during the test execution with the following command:
-    ```python
-    driver.execute_script("updateNetworkProfile=offline")
-    ```
 
 ## Toggle Offline/Online Mode via API
 
-- For both iOS and android devices you can use the offline/online mode API as well within the running test session:
+- For android devices you can use the offline/online mode API as well within the running test session:
 
     ```bash
     curl --location 'https://mobile-api.lambdatest.com/mobile-automation/api/v1/sessions/<session-id>/update_network' \
diff --git a/docs/app-manager.md b/docs/app-manager.md
index 8e9439082..f4befff3d 100644
--- a/docs/app-manager.md
+++ b/docs/app-manager.md
@@ -128,6 +128,23 @@ Once your apps are uploaded, you can easily search and filter them using the too
 <img loading="lazy" src={require('../assets/images/real-device-app-testing/APP_MANAGER_VERSION_CONTROL.png').default} className="doc_img"/>
 ---
 
+### Release Notes for Versions
+For each app version, you can add multiline release notes to help differentiate between multiple builds.
+- To add release notes, open the three dots menu on the desired version in the App Card and click Version Details.
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/App_Manager_r1.png').default} className="doc_img"/>
+- Inside Version Details, you’ll see an option to enter release notes.
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/App_Manager_r2.png').default} className="doc_img"/>
+- Once added, a notes icon appears on the version. On hover, the release note is shown directly from the App Card. 
+<img loading="lazy" src={require('../assets/images/real-device-app-testing/App_Manager_r3.png').default} className="doc_img"/>
+
+:::info
+- Maximum release notes length is upto 500 characters.
+- On hover, only the first 100 characters are displayed, followed by ... if the text is longer.
+- Only the owner of the version has permission to add or edit release notes, Other users can only view them.
+:::
+
+---
+
 ## Launching an App on a Real Device  
 Once a specific version is selected:
 
diff --git a/docs/hyperexecute-maestro-testing.md b/docs/hyperexecute-maestro-testing.md
index 0bb92ebbe..ef118230b 100644
--- a/docs/hyperexecute-maestro-testing.md
+++ b/docs/hyperexecute-maestro-testing.md
@@ -107,6 +107,14 @@ https://github.com/LambdaTest/hyperexecute-maestro-sample-test/blob/main/android
 ```
 </TabItem>
 
+<TabItem value="iOS-Real Device" label="iOS-Real Device" default>
+> To enable execution on iOS real devices, install the following [JAR-file](https://prod-mobile-artefacts.lambdatest.com/assets/maestro-cli/1.41.0-beta-1/maestro.jar)
+ and include it in your payload. This JAR acts as a wrapper to facilitate compatibility with Maestro when running on iOS real devices.
+```yaml reference title="hyperexecute.yaml"
+https://github.com/LambdaTest/hyperexecute-maestro-sample-test/blob/main/ios-realdevice.yaml
+```
+</TabItem>
+
 <TabItem value="android-emu" label="Android-Emulator" default>
 
 > To enable this for your organizaton, connect with us through our <span className="doc\_\_lt" onClick={() => window.openLTChatWidget()}>**24/7 chat support**</span> or drop us an email to [support@lambdatest.com](mailto:support@lambdatest.com).
@@ -139,6 +147,11 @@ The above command will generate a `report.xml` file in the root directory after
 ```yaml reference
 https://github.com/LambdaTest/hyperexecute-maestro-sample-test/blob/main/maestro-test/runTest.sh
 ```
+When running on iOS real devices, you need to use a dedicated script since the execution flow differs slightly from iOS simulators and Android.
+
+```yaml reference
+https://github.com/LambdaTest/hyperexecute-maestro-sample-test/blob/main/maestro-test/runTest_ios_realdevice.sh
+```
 
 2. Update your HyperExecute YAML file to enable the native reporting in HyperExecute using the generated JUnit XML files.