diff --git a/content/hardware/02.uno/boards/uno-q/tutorials/01.user-manual/content.md b/content/hardware/02.uno/boards/uno-q/tutorials/01.user-manual/content.md
index e0e5b6680f..880bfd0809 100644
--- a/content/hardware/02.uno/boards/uno-q/tutorials/01.user-manual/content.md
+++ b/content/hardware/02.uno/boards/uno-q/tutorials/01.user-manual/content.md
@@ -1360,11 +1360,13 @@ With this example the UNO Q will send back whatever it receives on the UART.
 
 #### From Serial to Monitor
 
-Because of the UNO Q’s architecture, using `Serial` does not display data in the Arduino App Lab Serial Monitor as you might expect.
+Because of the UNO Q’s architecture, using `Serial` does not display data in the Arduino App Lab **Console** as you might expect.
 
-To make debugging just as easy as on other Arduino boards, we provide the `Monitor` object, which you can use to print debugging messages, sensor readings, or any other information directly to the Serial Monitor.
+To make debugging just as easy as on other Arduino boards, we provide the `Monitor` object, which you can use to print debugging messages, sensor readings, or any other information directly to the App Lab Console.
 
-You can do exactly the same, but with a minor prerequisite; including the `Arduino_RouterBridge` library in your sketch:
+Note: `Serial` still works over UART, but its output is not shown in App Lab.
+
+You can achieve the same behavior with a minor prerequisite: include the `Arduino_RouterBridge` library in your sketch.
 
 ```cpp
 #include <Arduino_RouterBridge.h>
diff --git a/content/software/app-lab/tutorials/01.getting-started/apps-lab-ide.md b/content/software/app-lab/tutorials/01.getting-started/apps-lab-ide.md
index 55e1a062a1..4b8539aca8 100644
--- a/content/software/app-lab/tutorials/01.getting-started/apps-lab-ide.md
+++ b/content/software/app-lab/tutorials/01.getting-started/apps-lab-ide.md
@@ -229,7 +229,9 @@ Each official example provides a detailed documentation provided in the `readme.
 Once an App is launched, the status of the App is available in the **Console**. There are three tabs available:
 - **Start-up** - outputs the logs from the start-up process. Here you will find information regarding compilation for the microcontroller and deployment of the Python® application on the Linux system.
 - **Main (Python®)** - view the logs from the Python® application (`print()`)
-- **Sketch (Microcontroller)** - view serial data from the sketch (`Serial.println()`)
+- **Sketch (Microcontroller)** – view data sent from the sketch using `Monitor.print()`.
+   
+**Note:** `Serial.println()` outputs data over UART and is not shown in the App Lab Console. To display messages in the Console, use `Monitor.print()`. Learn more in [From Serial to Monitor](/tutorials/uno-q/user-manual/#from-serial-to-monitor)
 
 ![App logs](assets/app-logs.png)
 
@@ -308,4 +310,4 @@ In this guide, we have covered some of the most important aspects of the editor,
 More documentation for the Arduino App Lab is available at:
 - [Arduino App Lab Documentation](https://docs.arduino.cc/software/app-lab/)
 
-You can also visit the [Arduino® UNO Q](/hardware/uno-q) hardware page for details on the board.
\ No newline at end of file
+You can also visit the [Arduino® UNO Q](/hardware/uno-q) hardware page for details on the board.
diff --git a/content/software/app-lab/tutorials/01.getting-started/assets/app-logs.png b/content/software/app-lab/tutorials/01.getting-started/assets/app-logs.png
index 86cb3e5640..ffefbc6a9a 100644
Binary files a/content/software/app-lab/tutorials/01.getting-started/assets/app-logs.png and b/content/software/app-lab/tutorials/01.getting-started/assets/app-logs.png differ