Correct unordered list formatting in all markdown files

.markdownlint-cli2.jsonc

@@ -11,8 +11,6 @@
     // These can be re-enabled incrementally as files are fixed
     "MD001": false,  // Heading levels should only increment by one level at a time
     "MD003": false,  // Heading style
-    "MD004": false,  // Unordered list style
-    "MD007": false,  // Unordered list indentation
     "MD012": false,  // Multiple consecutive blank lines
     "MD013": false,  // Line length
     "MD014": false,  // Dollar signs used before commands without showing output

BUILD.md

@@ -22,7 +22,7 @@ Do not run `waf` with `sudo`!  This leads to permission and environment problems
 There are several commands in the build system for advanced usage, but here we
 list some basic and more used commands as example.
 
-* **Build ArduCopter**
+- **Build ArduCopter**
 
     Below shows how to build ArduCopter for the Pixhawk2/Cube. Many other boards are
     supported and the next section shows how to get a full list of them.
@@ -51,7 +51,7 @@ list some basic and more used commands as example.
 
     The "arducopter" binary should appear in the `build/<board-name>/bin` directory.
 
-* **List available boards**
+- **List available boards**
 
     It's possible to get a list of supported boards on ArduPilot with the command
     below
@@ -77,7 +77,7 @@ list some basic and more used commands as example.
 
     ```
 
-* **List of available vehicle types**
+- **List of available vehicle types**
 
     Here is a list of the most common vehicle build targets:
 
@@ -92,7 +92,7 @@ list some basic and more used commands as example.
 
     ```
 
-* **Clean the build**
+- **Clean the build**
 
     Commands `clean` and `distclean` can be used to clean the objects produced by
     the build. The first keeps the `configure` information, cleaning only the
@@ -108,7 +108,7 @@ list some basic and more used commands as example.
 
     In some some cases `submodule_force_clean` may be necessary. This removes all submodules and then performs a `submodulesync`. (Note whitelisted modules like esp_idf is not removed.)
 
-* **Upload or install**
+- **Upload or install**
 
     Build commands have a `--upload` option in order to upload the binary built
     to a connected board. This option is supported by Pixhawk and Linux-based boards.
@@ -146,7 +146,7 @@ list some basic and more used commands as example.
     DESTDIR=/my/temporary/location ./waf install
     ```
 
-* **Use different targets**
+- **Use different targets**
 
     The build commands in the items above use `copter` as argument. This
     builds all binaries that fall under the "copter" group. See the
@@ -169,7 +169,7 @@ list some basic and more used commands as example.
     ./waf --targets tests/test_math
     ```
 
-* **Use clang instead of gcc**
+- **Use clang instead of gcc**
 
     Currently, gcc is the default on linux, and clang is used for MacOS.
     Building with clang on linux can be accomplished by setting the CXX
@@ -181,7 +181,7 @@ list some basic and more used commands as example.
 
     Note: Your clang binary names may differ.
 
-* **Other options**
+- **Other options**
 
     It's possible to see all available commands and options:
 

Tools/Linux_HAL_Essentials/README.md

@@ -3,17 +3,17 @@ PRU PWM
 
 ### Updating kernel
 
-* Check your kernel version using `uname -r`
-* If you get 3.8.13bone56+ as output then you may skip Updating kernel.
-* For other kernel versions write following cmds in your BBB:
+- Check your kernel version using `uname -r`
+- If you get 3.8.13bone56+ as output then you may skip Updating kernel.
+- For other kernel versions write following cmds in your BBB:
 
 ```
 wget https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone57/install-me.sh
 chmod +x install-me.sh
 ./install-me.sh
 ```
 
-* After above steps reboot and check your kernel version using `uname -r`,it should be `3.8.13bone57`
+- After above steps reboot and check your kernel version using `uname -r`,it should be `3.8.13bone57`
 
 ----
 
@@ -27,14 +27,14 @@ NOTE: For Ubuntu different scripts shall be used. E.g., for precise:
 
 You should first check if there is the PRU Compiler available in your Linux-Distribution.
 
-* `apt-get update`
-* `sudo apt-get install ti-pru-cgt-installer`
+- `apt-get update`
+- `sudo apt-get install ti-pru-cgt-installer`
 
 If it is not available in your Linux-Distribution you have to download it from the TI website.
 
-* Download [PRU C Compiler v2.0.0B2 installer](http://software-dl.ti.com/codegen/non-esd/downloads/beta.htm)
-* Please check the path where you install PRU compiler.
-* Setting environment variable
+- Download [PRU C Compiler v2.0.0B2 installer](http://software-dl.ti.com/codegen/non-esd/downloads/beta.htm)
+- Please check the path where you install PRU compiler.
+- Setting environment variable
 
 ```
 echo export PATH=/path/to/pru/compiler/bin:$PATH >> ~/.bashrc
@@ -46,12 +46,12 @@ source ~/.bashrc
 
 ### Compiling and loading the code
 
-* just `make`
-* copy generated executable `pwmpru1` to `ardupilot/Tools/Linux_HAL_Essentials/`.
-* To load firmware use
+- just `make`
+- copy generated executable `pwmpru1` to `ardupilot/Tools/Linux_HAL_Essentials/`.
+- To load firmware use
   - `./startup.sh load` : only once after reboot it will copy overlays and firmware to `/lib/firmware/` and loads them.
   - `./startup.sh reload` : it only copies firmware to `/lib/firmware/` and reloads pru firmware.
-* Enable loading cape during BBB startup (no need to follow above step if you do this step once):
+- Enable loading cape during BBB startup (no need to follow above step if you do this step once):
   - `cp BB-PXF-01-00A0.dtbo /lib/firmware`
   - add `cape_enable=capemgr.enable_partno=BB-PXF-01` to `/boot/uboot/uEnv.txt`
   - add `CAPE=BB-PXF-01` to `/etc/default/capemgr`

libraries/AP_HAL_ChibiOS/hwdef/3DRControlZeroG/README.md

@@ -10,31 +10,31 @@ The Control Zero H7 OEM revision G is a flight controller produced by [3DR (mRo)
 ## Features
 
 - Processor
-    - STM32H743IIK6 32-bit Processor
+  - STM32H743IIK6 32-bit Processor
 - Sensors
-    - BMI088 6DOF
-    - ICM20602 6DOF
-    - ICM20948 9DOF
-    - DPS368 Baro
+  - BMI088 6DOF
+  - ICM20602 6DOF
+  - ICM20948 9DOF
+  - DPS368 Baro
 - Power
-    - External Power Supply
-    - Logic level at 3.3V
+  - External Power Supply
+  - Logic level at 3.3V
 - Interfaces
-    - Bottom Connectors: 36pin front and 40pin back Samtec FTM-118-02-x and FTM-120-02-x
-    - 8x PWM / IO - DMA capable
-    - 1x RC Input
-    - 5x UARTs (2x with hardware flow control)
-    - 2x CAN
-    - 1x SPI
-    - 3x I2C
-    - SWD via TC2030 header
-    - SDCARD Socket
+  - Bottom Connectors: 36pin front and 40pin back Samtec FTM-118-02-x and FTM-120-02-x
+  - 8x PWM / IO - DMA capable
+  - 1x RC Input
+  - 5x UARTs (2x with hardware flow control)
+  - 2x CAN
+  - 1x SPI
+  - 3x I2C
+  - SWD via TC2030 header
+  - SDCARD Socket
 - Memory
-    - FRAM (256KB)
+  - FRAM (256KB)
 - Miscellaneous
-    - Onboard 3 color LED
-    - Buzzer
-    - Safety Button
+  - Onboard 3 color LED
+  - Buzzer
+  - Safety Button
 
 ### Uncased Weight and Dimensions
 

libraries/AP_HAL_ChibiOS/hwdef/AEDROXH7/README.md

@@ -56,9 +56,9 @@ M9 on a separate pad for LED strip (default configuration) or another PWM output
 
 The PWM is in 4 groups:
 
-* PWM 1-4 in group1
-* PWM 5-8 in group2
-* PWM 9 (LED) in group3
+- PWM 1-4 in group1
+- PWM 5-8 in group2
+- PWM 9 (LED) in group3
 
 Channels within the same group need to use the same output rate. If
 any channel in a group uses DShot then all channels in the group need

libraries/AP_HAL_ChibiOS/hwdef/AEROFOX-H7/README.md

@@ -7,31 +7,31 @@ The AEROFOX-H7 is a flight controller produced by [AEROFOX](http://aerofox.cn)
 ## Features
 
 - Processor
-    - STM32H743
+  - STM32H743
 
 - Sensors
-    - ADIS16470 (appears in the advanced version)
-    - ICM45686 (appears in the advanced version)
-    - ICM42688
-    - QMC5883L
-    - SPL06-001
+  - ADIS16470 (appears in the advanced version)
+  - ICM45686 (appears in the advanced version)
+  - ICM42688
+  - QMC5883L
+  - SPL06-001
 
 - Power
-    - 2S-12S (MAX60V) Lipo input voltage
-    - 5V BEC for system power supply( 5V peripheral current limit 1.2A)
-    - 5V/12V BEC for VTX( Current limit 2.5A, need strong heat dissipation)
-    - Dual power automatic switching and condition monitoring
+  - 2S-12S (MAX60V) Lipo input voltage
+  - 5V BEC for system power supply( 5V peripheral current limit 1.2A)
+  - 5V/12V BEC for VTX( Current limit 2.5A, need strong heat dissipation)
+  - Dual power automatic switching and condition monitoring
 
 - Interfaces
-    - 16x PWM output
-    - 7x UARTs for RC, TELEM, GPS and other peripherals
-    - 2x I2C ports for external compass, airspeed, baro
-    - 2x CAN port
-    - 4x Relay output
-    - 4x ADC input
-
-    FPC connector
-    - The connector includes an SPI, an I2C, an PWM IMU heating control pin.
+  - 16x PWM output
+  - 7x UARTs for RC, TELEM, GPS and other peripherals
+  - 2x I2C ports for external compass, airspeed, baro
+  - 2x CAN port
+  - 4x Relay output
+  - 4x ADC input
+
+  FPC connector
+  - The connector includes an SPI, an I2C, an PWM IMU heating control pin.
 
 ## Pinout
 

libraries/AP_HAL_ChibiOS/hwdef/AET-H743-Basic/README.md

@@ -101,14 +101,14 @@ The voltage sensors can handle up to 6S LiPo batteries.
 
 The first voltage/current sensor is enabled by default and the pin inputs for the second, unenabled sensor are also set by default:
 
-* BATT_MONITOR 4
-* BATT_VOLT_PIN 10
-* BATT_CURR_PIN 11
-* BATT_VOLT_MULT 11
-* BATT_AMP_PERVLT 40
-* BATT2_VOLT_PIN 18
-* BATT2_CURR_PIN 7
-* BATT2_VOLT_MULT 11
+- BATT_MONITOR 4
+- BATT_VOLT_PIN 10
+- BATT_CURR_PIN 11
+- BATT_VOLT_MULT 11
+- BATT_AMP_PERVLT 40
+- BATT2_VOLT_PIN 18
+- BATT2_CURR_PIN 7
+- BATT2_VOLT_MULT 11
 
 ## Compass
 

libraries/AP_HAL_ChibiOS/hwdef/AnyleafH7/README.md

@@ -5,27 +5,27 @@ The Mercury H7 is a flight controller produced by [AnyLeaf](http://www.anyleaf.o
 ## Features
 
 - Processor
-    - STM32H743 32-bit processor
+  - STM32H743 32-bit processor
 - Sensors
-    - ICM42688 Acc/Gyro with dedicated 32.768kHz crystal
-    - DPS310 barometer
+  - ICM42688 Acc/Gyro with dedicated 32.768kHz crystal
+  - DPS310 barometer
 - Power
-    - 2S - 6S Lipo input voltage with voltage monitoring
-    - 9V, 3A supply for powering video transmitters
-    - 5V, 2A supply for powering servos and electronics
-    - 3.3V, 500mA supply for powering electronics
+  - 2S - 6S Lipo input voltage with voltage monitoring
+  - 9V, 3A supply for powering video transmitters
+  - 5V, 2A supply for powering servos and electronics
+  - 3.3V, 500mA supply for powering electronics
 - Interfaces
-    - 8x Bidirectional-DSHOT, or PWM-capable motor outputs
-    - 1x CAN-FD port for external peripherals
-    - 1x DJI-format Vtx connector
-    - 4x UARTs/serial for external peripherals, 3 of which are available by default
-    - 1x I2C bus for external peripherals
-    - USB-C port
-    - All UARTs support hardware inversion
-    - Onboard ExpressLRS radio transceiver for control and/or telemetry data.
+  - 8x Bidirectional-DSHOT, or PWM-capable motor outputs
+  - 1x CAN-FD port for external peripherals
+  - 1x DJI-format Vtx connector
+  - 4x UARTs/serial for external peripherals, 3 of which are available by default
+  - 1x I2C bus for external peripherals
+  - USB-C port
+  - All UARTs support hardware inversion
+  - Onboard ExpressLRS radio transceiver for control and/or telemetry data.
 - Dimensions
-    - Size: 37.5 x 37.5mm
-    - Weight: 8g
+  - Size: 37.5 x 37.5mm
+  - Weight: 8g
 
 ## Pinout
 

libraries/AP_HAL_ChibiOS/hwdef/Atlas-Control/README.md

@@ -148,10 +148,10 @@ See [ArduPilot RC documentation](https://ardupilot.org/plane/docs/common-rc-syst
 
 The 14 PWM outputs are in 4 groups: Each group must be the same protocol (ie PWM or DShot or Serial LED, etc.):
 
-* Outputs 1, 2, 3 and 4 in group1 (supports Bi-directional DShot)
-* Outputs 5, 6, 7 and 8 in group2 (supports Bi-directional DShot)
-* Outputs 9, 10, 11 and 12 in group3 (supports DShot)
-* Outputs 13 and 14 in group4 (PWM only, no DMA)
+- Outputs 1, 2, 3 and 4 in group1 (supports Bi-directional DShot)
+- Outputs 5, 6, 7 and 8 in group2 (supports Bi-directional DShot)
+- Outputs 9, 10, 11 and 12 in group3 (supports DShot)
+- Outputs 13 and 14 in group4 (PWM only, no DMA)
 
 ## Battery Monitoring
 
@@ -160,12 +160,12 @@ The board has two dedicated power monitor ports on 6 pin connectors.
 The board is supplied with an analog power module. Analog monitoring is set as the default configuration.
 The module is rated for up to 60V (14S) and 60A continuous current.
 
-* **BATT_MONITOR**: 4 (Analog Voltage and Current)
-* **BATT_VOLT_PIN**: 16
-* **BATT_CURR_PIN**: 17
-* **BATT_VOLT_MULT**: 18.000
-* **BATT_AMP_PERVLT**: 24.000
-* **BATT_VLT_OFFSET**: -0.1
+- **BATT_MONITOR**: 4 (Analog Voltage and Current)
+- **BATT_VOLT_PIN**: 16
+- **BATT_CURR_PIN**: 17
+- **BATT_VOLT_MULT**: 18.000
+- **BATT_AMP_PERVLT**: 24.000
+- **BATT_VLT_OFFSET**: -0.1
 
 ## Compass
 

libraries/AP_HAL_ChibiOS/hwdef/BROTHERHOBBYF405v3/README.md

@@ -33,11 +33,11 @@ The BROTHERHOBBYF405v3 is a flight controller produced by [BROTHERHOBBY](https:/
 
 The default RC input is configured on UART2, all ArduPilot compatible protocols, except PPM and SBUS, are supported. SBUS support is provided via the HD VTX connector on SERIAL1 and requires the protocol be set to :ref:`SERIAL1_PROTOCOL<SERIAL1_PROTOCOL>` = "23" and change SERIAL2 _Protocol to something other than '23'.
 
-* PPM is not supported
-* FPort requires an external bi-directional inverter (see :ref:`common-fport-receivers`)
-* CRSF requires connection to TX2 and automatically supports telemetry
-* DSM/SRXL connects to the RX2 pin, but SBUS would still be connected to SBUS.
-* SRXL2 requires a connection to TX2 and automatically provides telemetry. Set :ref:`SERIAL2_OPTIONS<SERIAL2_OPTIONS>` to “4”.
+- PPM is not supported
+- FPort requires an external bi-directional inverter (see :ref:`common-fport-receivers`)
+- CRSF requires connection to TX2 and automatically supports telemetry
+- DSM/SRXL connects to the RX2 pin, but SBUS would still be connected to SBUS.
+- SRXL2 requires a connection to TX2 and automatically provides telemetry. Set :ref:`SERIAL2_OPTIONS<SERIAL2_OPTIONS>` to "4".
 
 ## FrSky Telemetry
 

libraries/AP_HAL_ChibiOS/hwdef/BROTHERHOBBYH743/README.md

@@ -33,9 +33,9 @@ The BROTHERHOBBYH743 is a flight controller produced by [BROTHERHOBBY](https://w
 
 The default RC input is configured on the UART2_RX inverted from the SBUS pin.  All unidirectional ArduPilot compatible protocols, except PPM, are supported. Receivers using bi-directional protocols such as CRSF/ELRS should be tied to the TX2 and RX2 pins.
 
-* FPort requires connection to TX2 . See :ref:`FPort Receivers<common-Fport-receivers>`.
-* CRSF/ELRS also requires a TX2 connection, in addition to RX2, and automatically provides telemetry.
-* SRXL2 requires a connection to TX2 and automatically provides telemetry. Set :ref:`SERIAL2_OPTIONS<SERIAL2_OPTIONS>` to “4”.
+- FPort requires connection to TX2 . See :ref:`FPort Receivers<common-Fport-receivers>`.
+- CRSF/ELRS also requires a TX2 connection, in addition to RX2, and automatically provides telemetry.
+- SRXL2 requires a connection to TX2 and automatically provides telemetry. Set :ref:`SERIAL2_OPTIONS<SERIAL2_OPTIONS>` to "4".
 
 ## FrSky Telemetry