docs(docs): Update CUAV X25 Series Doc (#26882)

docs/en/SUMMARY.md

@@ -171,6 +171,7 @@
       - [CUAV V5 nano (FMUv5)](flight_controller/cuav_v5_nano.md)
         - [CUAV V5 nano Wiring Quickstart](assembly/quick_start_cuav_v5_nano.md)
       - [CUAV X25 EVO](flight_controller/cuav_x25-evo.md)
+        - [CUAV X25 EVO Wiring Quick Start](assembly/quick_start_cuav_x25_evo.md)
       - [CUAV X25 SUPER](flight_controller/cuav_x25-super.md)
       - [CubePilot Cube Orange+ (CubePilot)](flight_controller/cubepilot_cube_orangeplus.md)
       - [CubePilot Cube Orange (CubePilot)](flight_controller/cubepilot_cube_orange.md)

docs/en/advanced_config/ethernet_setup.md

@@ -27,6 +27,8 @@ Supported flight controllers include:
 
 - [ARK Electronics ARKV6X](../flight_controller/ark_v6x.md)
 - [CUAV Pixhawk V6X](../flight_controller/cuav_pixhawk_v6x.md)
+- [CUAV X25 EVO](../flight_controller/cuav_x25-evo.md)
+- [CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
 - [Holybro Pixhawk 5X](../flight_controller/pixhawk5x.md)
 - [Holybro Pixhawk 6X](../flight_controller/pixhawk6x.md)
 - [RaccoonLab FMUv6X Autopilot](../flight_controller/raccoonlab_fmu6x.md)

docs/en/assembly/_assembly.md

@@ -409,6 +409,7 @@ They recommend sensors, power systems, and other components from the same manufa
 - [CUAV Pixhawk V6X Wiring QuickStart](../assembly/quick_start_cuav_pixhawk_v6x.md)
 - [CUAV V5+ Wiring Quickstart](../assembly/quick_start_cuav_v5_plus.md)
 - [CUAV V5 nano Wiring Quickstart](../assembly/quick_start_cuav_v5_nano.md)
+- [CUAV X25 EVO Wiring Quickstart](../assembly/quick_start_cuav_x25_evo.md)
 - [Holybro Pixhawk 6C Wiring Quickstart](../assembly/quick_start_pixhawk6c.md)
 - [Holybro Pixhawk 6X Wiring Quickstart](../assembly/quick_start_pixhawk6x.md)
 - [Holybro Pixhawk 5X Wiring Quickstart](../assembly/quick_start_pixhawk5x.md)

docs/en/assembly/quick_start_cuav_x25_evo.md

@@ -0,0 +1,153 @@
+# CUAV X25 EVO Wiring Quick Start
+
+::: warning
+PX4 does not manufacture this (or any) autopilot.
+Contact the [manufacturer](https://store.cuav.net/) for hardware support or compliance issues.
+:::
+
+This quick start guide shows how to power the [X25 EVO](../flight_controller/cuav_x25-evo.md) flight controller and connect its most important peripherals.
+
+::: info
+The following flight controller models are applicable to this quick start guide.
+[CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
+:::
+
+## Wiring Chart Overview
+
+The image below shows how to connect the most important sensors and peripherals (except the motor and servo outputs).
+We'll go through each of these in detail in the following sections.
+
+![wiring](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_01.jpg)
+
+| Interface     | **Function**                                                                                                                                                 |
+| :------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| POWER C1/C2   | Connect the PMU2 Lite to this port; this port is used for connecting the DroneCAN power module                                                               |
+| M1 ~ M16      | PWM signal output ports, usable for controlling motors or servos; support 3.3V/5V PWM configuration                                                          |
+| RC IN         | Connect remote controller receivers with one-way protocols (e.g., SBUS/DSM/PPM). Note: ELRS/CRSF receivers should be connected to any serial port, not RC IN |
+| RSSI          | For connecting signal strength feedback modules                                                                                                              |
+| GPS&SAFETY    | Connect Neo-series GPS or C-RTK-series RTK; this port includes interfaces for GPS, safety switch, and buzzer                                                 |
+| GPS2          | Usable for connecting additional GPS/RTK modules                                                                                                             |
+| DEBUG (DSU)   | For FMU chip debugging and reading debug device information; with ArduPilot firmware, it can be configured for other serial port functions                   |
+| ADC3V3        | For analog level signal detection; the maximum detectable level signal is 3.3V                                                                               |
+| ADC6V6        | For analog level signal detection; the maximum detectable level signal is 6.6V (PX4 is not supported.)                                                       |
+| TF CARD       | Insert an SD card here to enable log storage functionality                                                                                                   |
+| ETH           | Ethernet port, usable for connecting Ethernet devices such as companion computers                                                                            |
+| I2C1/2/3      | Connect external I2C devices (e.g., external compasses) for communication between the controller and I2C devices                                             |
+| TELEM1/TELEM2 | Connect telemetry modules (for data transmission) to enable MAVLINK data interaction                                                                         |
+| CAN1/2        | For communication between the controller and DroneCAN devices (e.g., connecting NEO4 SE GPS)                                                                 |
+| TYPE C        | USB port of the controller, usable for connecting to the ground station, flashing firmware, and other operations                                             |
+| SPI6          | SPI port for external expansion; generally not used                                                                                                          |
+
+## Vehicle Front
+
+::: info
+If the controller cannot be mounted in the recommended/default orientation (e.g. due to space constraints) you will need to configure the autopilot software with the orientation that you actually used: [Flight Controller Orientation](../config/flight_controller_orientation.md).
+:::
+
+![front](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_02.jpg)
+
+## GPS + Compass + Buzzer + Safety Switch + LED
+
+We recommend using a CAN GPS/RTK (such as [Neo 4SE](https://store.cuav.net/shop/cuav-neo-4-se-gps-module/)); simply connect it to the **CAN 1** or **CAN 2** port.
+
+You can also use a standard GPS/RTK module(such as [NEO3 GPS](https://store.cuav.net/shop/neo-3/) (10-pin connector)) by connecting it to the **GPS&SAFETY** port.
+Most commonly used GPS modules today integrate GPS, compass, safety switch, buzzer, and LED status light.
+
+If you need to use assisted GPS, connect to the **GPS2** port.
+
+The GPS/compass should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible (separating the compass from other electronics will reduce interference), with the direction markings towards the front of the vehicle (the arrow on the NEO GPS should match the arrow on the flight controller).
+
+![GPS](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_03.jpg)
+
+::: info
+The GPS module's integrated safety switch is enabled _by default_ (when enabled, PX4 will not let you arm the vehicle).
+To disable the safety, press and hold the safety switch for 1 second.
+You can press the safety switch again to enable safety and disarm the vehicle (this can be useful if, for whatever reason, you are unable to disarm the vehicle from your remote control or ground station).
+:::
+
+## Radio Control
+
+A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
+
+You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
+
+Connection methods vary by remote controller and receiver type:
+
+### Android Remote Controllers
+
+Take the H16 as an example:
+
+![H16 control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_04.jpg)
+
+Connect **TELEM1/TELEM2** to the UART0 port of the H16 remote controller, and link the H16’s SBUS pin to the **RC IN** port.
+
+### SBUS/DSM/PPM Protocol Receivers
+
+![SBUS/DSM/PPM control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_05.jpg)
+
+Use wires to connect the receiver to the **RC IN** port at the rear of the controller.
+
+### ELRS/CRSF Receivers
+
+![ELRS/CRSF control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_06.jpg)
+
+Connect the [ELRS/CRSF](../telemetry/crsf_telemetry.md) receiver to any UART serial port of the X25 EVO (e.g., **TELEM2**).
+
+## Power
+
+The X25 EVO comes standard with the PMU2 Lite power module, which supports 20–70V input and can measure a maximum current of 220A.
+It can be directly connected to the **Power C1/C2** port of the X25 EVO and is plug-and-play (no configuration required).
+
+![Power](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_07.png)
+
+## Telemetry (Radio) System
+
+[Telemetry system](../telemetry/index.md) allows you to communicate with the unmanned system via ground station software, enabling you to monitor and control the UAV’s status during flight. Connect the on-board unit of the telemetry system to the **TELEM1** or **TELEM2** port.
+
+You can also purchase telemetry radios from the [CUAV store](https://store.cuav.net/uav-telemetry-module/).
+
+![Telemetry system](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_04.jpg)
+
+## SD Card
+
+SD cards are highly recommended as they are required for [recording and analyzing flight details](../getting_started/flight_reporting.md), running tasks and using UAVCAN bus hardware.
+An SD card is already installed on X25 EVO when it leaves the factory.
+
+::: tip
+For more information see [Basic Concepts > SD Cards (Removable Memory)](../getting_started/px4_basic_concepts.md#sd-cards-removable-memory).
+:::
+
+## Motors/Servo
+
+Motors/servos are connected to the **M1~M16** ports in the order specified for your vehicle in the [Airframe Reference](../airframes/airframe_reference.md).
+
+![Motors](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_08.jpg)
+
+## Servo Power Supply
+
+The X25 EVO does not supply power to servos. If you need to power servos:
+
+1. Connect a BEC to the positive and negative terminals of any column among **M1 ~ M16** (the positive and negative terminals of **M1 ~ M16** are interconnected).
+2. Then connect the servos to the same column.
+
+![servo power supply](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_09.jpg)
+
+::: info
+The power rail voltage must be appropriate for the servo being used!
+:::
+
+## Other Peripherals
+
+The wiring and configuration of optional/less common components is covered within the topics for individual [peripherals](../peripherals/index.md).
+
+## Configuration
+
+General configuration information is covered in: [Autopilot Configuration](../config/index.md).
+
+QuadPlane-specific configuration is covered here: [QuadPlane VTOL Configuration](../config_vtol/vtol_quad_configuration.md)
+
+## Further information
+
+- [CUAV Docs](https://doc.cuav.net/) (CUAV)
+- [X25 EVO](../flight_controller/cuav_x25-evo.md) (PX4 Doc Overview page)
+- [X25 SUPER](../flight_controller/cuav_x25-super.md) (PX4 Doc Overview page)

docs/en/flight_controller/autopilot_manufacturer_supported.md

@@ -23,7 +23,7 @@ The boards in this category are:
 - [CUAV V5+](../flight_controller/cuav_v5_plus.md) (FMUv5)
 - [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) (FMUv5)
 - [CUAV X25 EVO](../flight_controller/cuav_x25-evo.md)
-  [CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
+- [CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
 - [CubePilot Cube Orange+](../flight_controller/cubepilot_cube_orangeplus.md)
 - [CubePilot Cube Orange](../flight_controller/cubepilot_cube_orange.md)
 - [CubePilot Cube Yellow](../flight_controller/cubepilot_cube_yellow.md)

docs/en/flight_controller/cuav_x25-evo.md

@@ -9,7 +9,7 @@ The _X25-EVO_ is an advanced autopilot manufactured by CUAV<sup>&reg;</sup>.
 
 The autopilot is recommended for commercial system integration but is also suitable for academic research and any other applications.
 
-![X25-EVO AutoPilot - hero image](../../assets/flight_controller/cuav_x25-evo/X25-EVO.jpg)
+![X25-EVO AutoPilot - hero image](../../assets/flight_controller/cuav_x25-evo/x25_evo.jpg)
 
 The X25-EVO brings you ultimate performance, stability, and reliability in every aspect.
 
@@ -19,12 +19,17 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
 
 ### Features
 
-- Arm® Cortex-M7® processor (STM32H743XI) with Floating-Point Unit (FPU), operating at 480MHz, and featuring 2MB Flash memory. Enables developers to enhance productivity and efficiency, allowing for more complex algorithms and models.
-- Automotive-grade RM3100 compass. Designed for better stability and anti-interference capability.
-- Triple-redundant IMUs and dual-redundant barometers located on separate buses. If the PX4 autopilot detects a sensor failure, the system seamlessly switches to another sensor to maintain flight control reliability.
-- Independent LDO power control supplies power to each sensor group. A vibration isolation system filters high-frequency vibrations and reduces noise to ensure accurate readings, enabling better overall flight performance for the vehicle.
+- Arm® Cortex-M7® processor (STM32H743XI) with Floating-Point Unit (FPU), operating at 480MHz, and featuring 2MB Flash memory.
+  Enables developers to enhance productivity and efficiency, allowing for more complex algorithms and models.
+- Automotive-grade RM3100 compass.
+  Designed for better stability and anti-interference capability.
+- Triple-redundant IMUs and dual-redundant barometers located on separate buses.
+  If the PX4 autopilot detects a sensor failure, the system seamlessly switches to another sensor to maintain flight control reliability.
+- Independent LDO power control supplies power to each sensor group.
+  A vibration isolation system filters high-frequency vibrations and reduces noise to ensure accurate readings, enabling better overall flight performance for the vehicle.
 - Integrated Microchip Ethernet PHY for high-speed communication with onboard devices like mission computers via Ethernet.
-- Dual temperature compensation systems, located on the IMU board and FMU board respectively. Temperature is controlled by onboard heating resistors to achieve the optimal operating temperature for the IMUs.
+- Dual temperature compensation systems, located on the IMU board and FMU board respectively.
+  Temperature is controlled by onboard heating resistors to achieve the optimal operating temperature for the IMUs.
 - PWM servo output voltage switchable between 3.3V or 5V.
 - Modular design for DIY carrier boards.
 
@@ -33,7 +38,7 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
 - Main Processor: STM32H743XI
   - 32-bit Arm® Cortex®-M7, 480MHz, 2MB Flash, 1MB RAM
 - Onboard Sensors:
-  - Accel/Gyro: IIM42652\*2
+  - Accel/Gyro: IIM42652 (x2)
   - Accel/Gyro: IIM42653
   - Magnetometer: RM3100
   - Barometer: BMP581
@@ -47,14 +52,14 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
   - Servo Rail Input: 0~9.9V
 - Rated Current:
   - Total Output Max Current: 10A
-  - TELEM1 and TELEM2 Output Current limiter: 4A
-  - CAN1 and CAN2 Output Current limiter: 2.4A
+  - `TELEM1` and `TELEM2` Output Current limiter: 4A
+  - `CAN1` and `CAN2` Output Current limiter: 2.4A
   - Other Ports Output Current limiter: 1.5A
 
 ### Interfaces
 
 - 16x PWM Servo Outputs
-- 1x Dedicated R/C Input for Spektrum / DSM and S.Bus
+- 1x Dedicated R/C Input(`RC IN`) for Spektrum / DSM and S.Bus
 - 1x Analog/PWM RSSI Input
 - 2x TELEM Ports (with full flow control)
 - 1x UART4 Port
@@ -83,7 +88,12 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
 
 ### Mechanical Data
 
-- Not provided.
+- Weight
+  - Flight Controller Module: 110g
+- Operating & storage temperature: -20 ~ 85°C
+- Dimensions:
+
+  ![CUAV X25 EVO](../../assets/flight_controller/cuav_x25-evo/x25_evo_size.png)
 
 ## Purchase Channels {#store}
 
@@ -91,11 +101,11 @@ Order from [CUAV](https://store.cuav.net/).
 
 ## Assembly/Setup
 
-- Not provided.
+The [X25 EVO Wiring Quick Start](../assembly/quick_start_cuav_x25_evo.md) provides instructions on how to assemble required/important peripherals including GPS, Power Module etc.
 
-## Pin Definitions
+## Pinouts
 
-- Not provided.
+![CUAV X25 EVO Pinout](../../assets/flight_controller/cuav_x25-evo/x25_evo_pinouts.jpg)
 
 ## Serial Port Mapping
 
@@ -106,12 +116,34 @@ Order from [CUAV](https://store.cuav.net/).
 | USART3 | /dev/ttyS2 | Debug Console |
 | UART4  | /dev/ttyS3 | UART4         |
 | UART5  | /dev/ttyS4 | TELEM2        |
-| USART6 | /dev/ttyS5 | RC            |
+| USART6 | /dev/ttyS5 | RC IN         |
 | UART7  | /dev/ttyS6 | TELEM1        |
 
+## PWM Outputs {#pwm_outputs}
+
+This flight controller supports up to 16 FMU PWM outputs (MAIN).
+
+Outputs:
+
+- Outputs 1-8 support [DShot](../peripherals/dshot.md).
+- Outputs 9-16 do not support DShot.
+- Outputs 1-7 support [Bidirectional DShot](../peripherals/dshot.md#bidirectional-dshot-telemetry).
+- Output 8 supports Bidirectional DShot output only (no eRPM capture).
+
+The 16 outputs are in 5 groups:
+
+- Outputs 1-4 in group1 (Timer5)
+- Outputs 5-8 in group2 (Timer4)
+- Outputs 9-11 in group3 (Timer1)
+- Outputs 12-14 in group4 (Timer8)
+- Outputs 15-16 in group5 (Timer12)
+
+All outputs within the same group must use the same output protocol and rate.
+
 ## Voltage Ratings
 
-The _X25-EVO_ achieves triple redundancy on power supplies if three power sources are provided. The three power rails are POWERC1, POWERC2, and USB.
+The _X25-EVO_ achieves triple redundancy on power supplies if three power sources are provided.
+The three power rails are `POWERC1`, `POWERC2`, and `USB`.
 
 - **POWER C1** and **POWER C2** are DroneCAN/UAVCAN battery interfaces.
 
@@ -154,7 +186,8 @@ The [PX4 System Console](../debug/system_console.md) and [SWD Interface](../debu
 
 ## Supported Platforms / Airframes
 
-Any multirotor/airplane/rover or boat that can be controlled using normal RC servos or Futaba S-Bus servos. The complete set of supported configurations can be found in the [Airframe Reference](../airframes/airframe_reference.md).
+Any multicopter / airplane / rover or boat that can be controlled with normal RC servos or Futaba S-Bus servos.
+The complete set of supported configurations can be seen in the [Airframes Reference](../airframes/airframe_reference.md).
 
 ## Further info
 

docs/en/flight_controller/cuav_x25-super.md

@@ -1,6 +1,6 @@
 # CUAV X25-SUPER
 
-<Badge type="tip" text="PX4 v1.18)" />
+<Badge type="tip" text="PX4 v1.18" />
 
 ::: warning
 PX4 does not manufacture this (or any) autopilot.
@@ -21,12 +21,17 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
 
 ### Features
 
-- Arm® Cortex-M7® processor (STM32H743XI) with Floating-Point Unit (FPU), operating at 480MHz, and featuring 2MB Flash memory. Enables developers to enhance productivity and efficiency, allowing for more complex algorithms and models.
-- Automotive-grade RM3100 compass. Designed for better stability and anti-interference capability.
-- Triple-redundant IMUs and dual-redundant barometers located on separate buses. If the PX4 autopilot detects a sensor failure, the system seamlessly switches to another sensor to maintain flight control reliability.
-- Independent LDO power control supplies power to each sensor group. A vibration isolation system filters high-frequency vibrations and reduces noise to ensure accurate readings, enabling better overall flight performance for the vehicle.
+- Arm® Cortex-M7® processor (STM32H743XI) with Floating-Point Unit (FPU), operating at 480MHz, and featuring 2MB Flash memory.
+  Enables developers to enhance productivity and efficiency, allowing for more complex algorithms and models.
+- Automotive-grade RM3100 compass.
+  Designed for better stability and anti-interference capability.
+- Triple-redundant IMUs and dual-redundant barometers located on separate buses.
+  If the PX4 autopilot detects a sensor failure, the system seamlessly switches to another sensor to maintain flight control reliability.
+- Independent LDO power control supplies power to each sensor group.
+  A vibration isolation system filters high-frequency vibrations and reduces noise to ensure accurate readings, enabling better overall flight performance for the vehicle.
 - Integrated Microchip Ethernet PHY for high-speed communication with onboard devices like mission computers via Ethernet.
-- Dual temperature compensation systems, located on the IMU board and FMU board respectively. Temperature is controlled by onboard heating resistors to achieve the optimal operating temperature for the IMUs.
+- Dual temperature compensation systems, located on the IMU board and FMU board respectively.
+  Temperature is controlled by onboard heating resistors to achieve the optimal operating temperature for the IMUs.
 - PWM servo output voltage switchable between 3.3V or 5V.
 - Modular design for DIY carrier boards.
 
@@ -50,14 +55,14 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
   - Servo Rail Input: 0~9.9V
 - Rated Current:
   - Total Output Max Current: 10A
-  - TELEM1 and TELEM2 Output Current limiter: 4A
-  - CAN1 and CAN2 Output Current limiter: 2.4A
+  - `TELEM1` and `TELEM2` Output Current limiter: 4A
+  - `CAN1` and `CAN2` Output Current limiter: 2.4A
   - Other Ports Output Current limiter: 1.5A
 
 ### Interfaces
 
 - 16x PWM Servo Outputs
-- 1x Dedicated R/C Input for Spektrum / DSM and S.Bus
+- 1x Dedicated R/C Input(`RC IN`) for Spektrum / DSM and S.Bus
 - 1x Analog/PWM RSSI Input
 - 2x TELEM Ports (with full flow control)
 - 1x UART4 Port
@@ -80,16 +85,15 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
   - DroneCAN/UAVCAN Power Input
 - 2x AD Ports
   - Analog Input (3.3V)
-  - Analog Input (6.6V - not supported)
+  - Analog Input (6.6V - not supported by PX4)
 - 1x Dedicated Debug Port
   - FMU Debug
 
 ### Mechanical Data
 
-- Size
-  - Flight controller
+- Dimensions:
 
-    ![CUAV X25-SUPER](../../assets/flight_controller/cuav_x25-super/x25-super_size.png)
+  ![CUAV X25-SUPER](../../assets/flight_controller/cuav_x25-super/x25-super_size.png)
 
 ## Purchase Channels {#store}
 
@@ -97,7 +101,7 @@ Order from [CUAV](https://store.cuav.net/).
 
 ## Assembly/Setup
 
-- Not provided.
+The [X25 SUPER Wiring Quick Start](../assembly/quick_start_cuav_x25_evo.md) provides instructions on how to assemble required/important peripherals including GPS, Power Module etc.
 
 ## Pinouts
 
@@ -113,7 +117,7 @@ Order from [CUAV](https://store.cuav.net/).
 | USART3 | /dev/ttyS2 | Debug Console |
 | UART4  | /dev/ttyS3 | UART4         |
 | UART5  | /dev/ttyS4 | TELEM2        |
-| USART6 | /dev/ttyS5 | RC            |
+| USART6 | /dev/ttyS5 | RC IN         |
 | UART7  | /dev/ttyS6 | TELEM1        |
 
 ## RC Input
@@ -122,7 +126,8 @@ The RC input pin is directly connected to the FMU UART6 TX.
 
 ## Voltage Ratings
 
-The _X25-SUPER_ achieves triple redundancy on power supplies if three power sources are provided. The three power rails are POWERC1, POWERC2, and USB.
+The _X25-SUPER_ achieves triple redundancy on power supplies if three power sources are provided.
+The three power rails are `POWERC1`, `POWERC2`, and `USB`.
 
 - **POWER C1** and **POWER C2** are DroneCAN/UAVCAN battery interfaces.
 
@@ -140,13 +145,13 @@ Digital DroneCAN/UAVCAN battery monitoring is enabled by default.
 ## Building Firmware
 
 ::: tip
-Most users will not need to build this firmware from PX4 v1.18.
+Most users will not need to build this firmware (from PX4 v1.18).
 It is pre-built and automatically installed by _QGroundControl_ when appropriate hardware is connected.
 :::
 
 To [build PX4](../dev_setup/building_px4.md) for this target, execute:
 
-```
+```sh
 make cuav_x25-super_default
 ```