MAVLink messages update Tue Mar 4 23:47:35 UTC 2025

Author: PX4BuildBot

en/messages/common.md

@@ -3318,7 +3318,7 @@ Large debug/prototyping array. The message uses the maximum available payload fo
 Field Name | Type | Units | Description
 --- | --- | --- | ---
 time_usec | `uint64_t` | us | Timestamp (UNIX Epoch time or time since system boot). The receiving end can infer timestamp format (since 1.1.1970 or since system boot) by checking for the magnitude of the number. 
-name | `char[10]` | | Name, for human-friendly display in a Ground Control Station 
+name | `char[10]` | | Name, for human-friendly  in a Ground Control Station 
 array_id | `uint16_t` | | Unique ID used to discriminate between arrays<br>Messages with same value are from the same source (instance). 
 <span class='ext'>data</span> <a href='#mav2_extension_field'>++</a> | `float[58]` | | data 
 
@@ -3370,7 +3370,7 @@ resting_minimum_voltage | `uint16_t` | mV | invalid:UINT16_MAX | Minimum per-cel
 
 Fuel status.
 
-This message provides "generic" fuel level information for display in a GCS and for triggering failsafes in an autopilot.
+This message provides "generic" fuel level information for  in a GCS and for triggering failsafes in an autopilot.
 The fuel type and associated units for fields in this message are defined in the enum [MAV_FUEL_TYPE](#MAV_FUEL_TYPE).
 
 The reported `consumed_fuel` and `remaining_fuel` must only be supplied if measured: they must not be inferred from the `maximum_fuel` and the other value.