docs: auto-sync metadata [skip ci]

Co-Authored-By: PX4 BuildBot <bot@px4.io>

docs/en/ros2/px4_ros2_msg_translation_node.md

@@ -305,7 +305,6 @@ The example describes the process of updating the `VehicleAttitude` message defi
    Update the existing translations header files `msg/translation_node/translations/*.h` to reference the newly archived message definition.
 
    For example, update references in those files:<br>
-
    - Replace `px4_msgs::msg::VehicleAttitude` → `px4_msgs_old::msg::VehicleAttitudeV3`
    - Replace `#include <px4_msgs/msg/vehicle_attitude.hpp>` → `#include <px4_msgs_old/msg/vehicle_attitude_v3.hpp>`
 
@@ -386,7 +385,6 @@ The example describes the process of updating the `VehicleAttitude` message defi
    ```
 
    Version translation templates are provided here:
-
    - [Direct Topic Message Translation Template](https://github.com/PX4/PX4-Autopilot/blob/main/msg/translation_node/translations/example_translation_direct_v1.h)
    - [Generic Topic Message Translation Template](https://github.com/PX4/PX4-Autopilot/blob/main/msg/translation_node/translations/example_translation_multi_v2.h)
    - [Direct Service Message Translation Template](https://github.com/PX4/PX4-Autopilot/blob/main/msg/translation_node/translations/example_translation_service_v1.h)
@@ -440,7 +438,7 @@ For translations with multiple input topics, the translation continues once all
 - Services messages only support a linear history, i.e. no message splitting or merging.
 - Having both publishers and subscribers for two different versions of the same topic is currently not handled by the translation node and would trigger infinite circular publications.
   This refers to the following problematic configuration:
-  
+
   ```
   app 1: pub topic_v1, sub topic_v1
   app 2: pub topic_v2, sub topic_v2