New Crowdin updates (#686)

Author: PX4BuildBot

ko/contributing/contributing.md

@@ -14,13 +14,13 @@ The sections below explain how to contribute to each category and how to raise a
 ## How to Contribute Simple Changes
 
 - Open a pull request against the specification repository: [https://github.com/mavlink/mavlink](https://github.com/mavlink/mavlink)
-- Reach out to the community on Slack and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
+- Reach out to the community on [Discord](https://discord.com/channels/1022170275984457759/1022185868317966458) and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
 - Address concerns by pushing more commits to the pull request
 
 ## How to Contribute Complex Changes
 
 - Open a pull request against the RFC repository containing a new RFC number [https://github.com/mavlink/rfcs](https://github.com/mavlink/rfcs) and use the template in the 0000 RFC.
-- Reach out to the community on Slack and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
+- Reach out to the community on [Discord](https://discord.com/channels/1022170275984457759/1022185868317966458) and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
 - Address concerns by pushing more commits to the pull request
 
 ## How to Contribute to Mavgen

ko/messages/common.md

@@ -3577,10 +3577,11 @@ See https://mavlink.io/en/services/standard_modes.html
 
 ### AVAILABLE_MODES_MONITOR (437) {#AVAILABLE_MODES_MONITOR}
 
-A change to the sequence number indicates that the set of [AVAILABLE_MODES](#AVAILABLE_MODES) has changed.
+A change to the sequence number indicates that the set of [AVAILABLE_MODES](#AVAILABLE_MODES) has changed, and that the receiver should re-request all available modes.
 
-A receiver must re-request all available modes whenever the sequence number changes.
-This is only emitted after the first change and should then be broadcast at low rate (nominally 0.3 Hz) and on change.
+The message is optional, and is only needed when the set of modes can change dynamically after boot.
+It should be emitted whenever the set of modes change.
+It should be streamed at low rate (nominally 0.3 Hz).
 See https://mavlink.io/en/services/standard_modes.html
 
 | Field Name | Type      | Description                                                                                                                                                                                                                                                               |

ko/messages/development.md

@@ -2,7 +2,7 @@
 
 # Dialect: development
 
-This dialect contains messages that are proposed for inclusion in the [standard set](standard.md), in order to ease development of prototype implementations.
+This dialect contains messages that are proposed for inclusion in the [common set](common.md), in order to ease development of prototype implementations.
 They should be considered a 'work in progress' and not included in production builds.
 
 This topic is a human-readable form of the XML definition file: [development.xml](https://github.com/mavlink/mavlink/blob/master/message_definitions/v1.0/development.xml).

ko/services/manual_control.md

@@ -88,8 +88,12 @@ ArduPilot Implementations:
 
 - [ArduCopter/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/GCS_Mavlink.cpp) (in `handleMessage` method)
 - [ArduPlane/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduPlane/GCS_Mavlink.cpp) (in `handleMessage` method)
-- [ArduRover/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduRover/GCS_Mavlink.cpp) (in `handle_manual_control` method)
 - [ArduSub/joystick.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduSub/joystick.cpp) (in `transform_manual_control_to_rc_override` method)
+- [ArduRover/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduRover/GCS_Mavlink.cpp) (in `handle_manual_control` method)
+
+  ::: info
+  ArduRover maps `y` as yaw instead of `r` (see [`handle_manual_control_axes`](https://github.com/ArduPilot/ardupilot/blob/0655825bb428db2218866fff14f0a5129302f6d6/Rover/GCS_MAVLink_Rover.cpp#L626-L627)).
+  :::
 
 ## Future Extensions
 

zh/contributing/contributing.md

@@ -14,13 +14,13 @@ The sections below explain how to contribute to each category and how to raise a
 ## How to Contribute Simple Changes
 
 - Open a pull request against the specification repository: [https://github.com/mavlink/mavlink](https://github.com/mavlink/mavlink)
-- Reach out to the community on Slack and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
+- Reach out to the community on [Discord](https://discord.com/channels/1022170275984457759/1022185868317966458) and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
 - 通过进一步支持拉动请求来解决关注问题
 
 ## How to Contribute Complex Changes
 
 - Open a pull request against the RFC repository containing a new RFC number [https://github.com/mavlink/rfcs](https://github.com/mavlink/rfcs) and use the template in the 0000 RFC.
-- Reach out to the community on Slack and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
+- Reach out to the community on [Discord](https://discord.com/channels/1022170275984457759/1022185868317966458) and the [mailing list](https://groups.google.com/forum/#!forum/mavlink) to raise awareness
 - 通过进一步支持拉动请求来解决关注问题
 
 ## How to Contribute to Mavgen

zh/messages/common.md

@@ -3577,10 +3577,11 @@ See https://mavlink.io/en/services/standard_modes.html
 
 ### AVAILABLE_MODES_MONITOR (437) {#AVAILABLE_MODES_MONITOR}
 
-A change to the sequence number indicates that the set of [AVAILABLE_MODES](#AVAILABLE_MODES) has changed.
+A change to the sequence number indicates that the set of [AVAILABLE_MODES](#AVAILABLE_MODES) has changed, and that the receiver should re-request all available modes.
 
-A receiver must re-request all available modes whenever the sequence number changes.
-This is only emitted after the first change and should then be broadcast at low rate (nominally 0.3 Hz) and on change.
+The message is optional, and is only needed when the set of modes can change dynamically after boot.
+It should be emitted whenever the set of modes change.
+It should be streamed at low rate (nominally 0.3 Hz).
 See https://mavlink.io/en/services/standard_modes.html
 
 | Field Name | Type      | 描述                                                                                                                                                                                                                                                                        |

zh/messages/development.md

@@ -2,7 +2,7 @@
 
 # Dialect: development
 
-This dialect contains messages that are proposed for inclusion in the [standard set](standard.md), in order to ease development of prototype implementations.
+This dialect contains messages that are proposed for inclusion in the [common set](common.md), in order to ease development of prototype implementations.
 They should be considered a 'work in progress' and not included in production builds.
 
 This topic is a human-readable form of the XML definition file: [development.xml](https://github.com/mavlink/mavlink/blob/master/message_definitions/v1.0/development.xml).

zh/services/manual_control.md

@@ -88,8 +88,12 @@ ArduPilot Implementations:
 
 - [ArduCopter/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/GCS_Mavlink.cpp) (in `handleMessage` method)
 - [ArduPlane/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduPlane/GCS_Mavlink.cpp) (in `handleMessage` method)
-- [ArduRover/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduRover/GCS_Mavlink.cpp) (in `handle_manual_control` method)
 - [ArduSub/joystick.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduSub/joystick.cpp) (in `transform_manual_control_to_rc_override` method)
+- [ArduRover/GCS_Mavlink.cpp](https://github.com/ArduPilot/ardupilot/blob/master/ArduRover/GCS_Mavlink.cpp) (in `handle_manual_control` method)
+
+  ::: info
+  ArduRover maps `y` as yaw instead of `r` (see [`handle_manual_control_axes`](https://github.com/ArduPilot/ardupilot/blob/0655825bb428db2218866fff14f0a5129302f6d6/Rover/GCS_MAVLink_Rover.cpp#L626-L627)).
+  :::
 
 ## Future Extensions