From 1d8656de714e308c0699598dd914f19b6548be6c Mon Sep 17 00:00:00 2001 From: Hamish Willee Date: Wed, 22 Jan 2025 15:15:51 +1100 Subject: [PATCH] Update en/ros2/px4_ros2_msg_translation_node.md --- en/ros2/px4_ros2_msg_translation_node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/ros2/px4_ros2_msg_translation_node.md b/en/ros2/px4_ros2_msg_translation_node.md index 6499d8ff4d58..041f739f1fce 100644 --- a/en/ros2/px4_ros2_msg_translation_node.md +++ b/en/ros2/px4_ros2_msg_translation_node.md @@ -292,7 +292,7 @@ Example directory structure (coherent with example above): This section provides a step-by-step walkthrough and a basic working example of what the process of changing a versioned message looks like. Before making changes to a versioned message (in `msg/versioned/` or `srv/versioned/`), we first create an archived copy of it, and update existing translation code to point to the archived version definition. -We then update versioned message definition to increment the version number, add any new fields or other changes, and then add a new translation file to convert between it and the previous (now archived) version. +We then update the versioned message definition to increment the version number, add any new fields or other changes, and then add a new translation file to convert between it and the previous (now archived) version. The example describes the process of updating the `VehicleAttitude` message definition to contain an additional `new_field` entry, incrementing the message version from `3` to `4`, and creating a new direct translation in the process.