diff --git a/docs/assets/flight_controller/arkv6s/ark_v6s_front.jpg b/docs/assets/flight_controller/arkv6s/ark_v6s_front.jpg
index 4c07abbcaf3..f9a75c47219 100644
Binary files a/docs/assets/flight_controller/arkv6s/ark_v6s_front.jpg and b/docs/assets/flight_controller/arkv6s/ark_v6s_front.jpg differ
diff --git a/docs/en/flight_controller/ark_v6s.md b/docs/en/flight_controller/ark_v6s.md
index 04db728b8df..755f8911d76 100644
--- a/docs/en/flight_controller/ark_v6s.md
+++ b/docs/en/flight_controller/ark_v6s.md
@@ -71,7 +71,8 @@ For pinout of the ARKV6S see the [DS-10 Pixhawk Autopilot Bus Standard](https://
 | UART8  | /dev/ttyS7 | GPS2          |
 
 ::: info
-The mapping above applies to the running PX4 firmware. The ARKV6S bootloader enables only `UART7` (TELEM1), so when flashing firmware over UART with [`px4_uploader.py`](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/px4_uploader.py) you must connect to the **TELEM1** port — no other UART will respond in bootloader mode.
+The mapping above applies to the running PX4 firmware.
+The ARKV6S bootloader enables only `UART7` (TELEM1), so when flashing firmware over UART with [`px4_uploader.py`](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/px4_uploader.py) you must connect to the `TELEM1` port — no other UART will respond in bootloader mode.
 :::
 
 ## Building Firmware