New Crowdin translations - zh-CN (#26553)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

docs/zh/camera/camera_architecture.md

@@ -36,7 +36,7 @@ The `camera_trigger`, `camera_capture` and `camera_feedback` modules are not use
 This work is handled by three PX4 components: [`camera_trigger` driver](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_trigger), [`camera_capture` driver](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_capture), [`camera-feedback` module](../modules/modules_system.md#camera-feedback).
 
 `camera_trigger` subscribes to the [VehicleCommand](../msg_docs/VehicleCommand.md) topic and monitors for updates to its [supported commands](../camera/fc_connected_camera.md#mavlink-command-interface).
-Thes updates occur when either a command is received via MAVLink or when a [camera item is reached in a mission](#camera-commands-in-missions).
+These updates occur when either a command is received via MAVLink or when a [camera item is reached in a mission](#camera-commands-in-missions).
 
 The commands enable and disable triggering, and configure triggering at time and distance intervals.
 The driver tracks these intervals, and when needed triggers the outputs.

docs/zh/camera/camera_intel_realsense_t265_vio.md

@@ -18,17 +18,22 @@ No longer available.
 
 At a high level:
 
-- The [`realsense-ros` wrapper](https://github.com/IntelRealSense/realsense-ros) provided by Intel should be used to extract the raw data from the camera.
+- The [`realsense-ros` wrapper](https://github.com/realsenseai/realsense-ros) provided by Intel should be used to extract the raw data from the camera.
+
 - The camera should be mounted with lenses facing down (default).
   Be sure to specify the camera orientation by publishing the static transform between the `base_link` and `camera_pose_frame` in a ROS launch file, for example:
+
   ```xml
   <node pkg="tf" type="static_transform_publisher" name="tf_baseLink_cameraPose"
       args="0 0 0 0 1.5708 0 base_link camera_pose_frame 1000"/>
   ```
+
   This is a static transform that links the camera ROS frame `camera_pose_frame` to the MAVROS drone frame `base_link`.
+
   - the first three `args` specify _translation_ x,y,z in metres from the center of the flight controller to the camera.
     For example, if the camera is 10cm in front of the controller and 4cm up, the first three numbers would be : [0.1, 0, 0.04,...]
   - the next three `args` specify rotation in radians (yaw, pitch, roll).
     So `[... 0, 1.5708, 0]` means pitch down by 90° (facing the ground). Facing straight forward would be [... 0 0 0].
+
 - The camera is sensitive to high-frequency vibrations!
   It should be soft-mounted with, for example, vibration isolation foam.

docs/zh/camera/fc_connected_camera.md

@@ -79,7 +79,7 @@ The shutter integration setting (`param2`) is only obeyed with a GPIO backend.
 
 ## Trigger Configuration
 
-Cameras can be connected to the FC for triggering using different intefaces, such as PWM, and GPIO, by specifying the appropriate [trigger interface backend](#trigger-interface-backends).
+Cameras can be connected to the FC for triggering using different interfaces, such as PWM, and GPIO, by specifying the appropriate [trigger interface backend](#trigger-interface-backends).
 You can also indicate the camera [trigger mode](#trigger-modes).
 
 This configuration can most easily be done from the _QGroundControl_ [Vehicle Setup > Camera](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/camera.html#px4-camera-setup) section.
@@ -308,7 +308,7 @@ Wire up your cameras to your AUX port by connecting the ground and signal pins t
 ### Step 4
 
 You will have to modify your driver to follow the sequence diagram above.
-Public reference implementations for [IDS Imaging UEye](https://github.com/ProjectArtemis/ueye_cam) cameras and for [IEEE1394 compliant](https://github.com/andre-nguyen/camera1394) cameras are available.
+Public reference implementations for [IDS Imaging UEye](https://github.com/anqixu/ueye_cam) cameras and for [IEEE1394 compliant](https://github.com/andre-nguyen/camera1394) cameras are available.
 
 ## 另见
 

docs/zh/camera/mavlink_v1_camera.md

@@ -1,4 +1,4 @@
-# 简单的 MAVLink 摄像头(Camera Protcol v1)
+# Simple MAVLink Cameras (Camera Protocol v1)
 
 本节说明了如何使用 PX4 的 MAVLink [相机](../camera/index.md), 实现了 [Camera Protocol v1 (简单触发协议)](https://mavlink.io/en/services/camera_v1.html) 的 PX4 和地面站。
 
@@ -18,7 +18,7 @@
 PX4 支持此命令集以触发通过原生支持协议的相机 （如本节所述），以及连接到飞控输出的相机。
 
 地面站和 MAVLink SDK 通常将相机命令发送给自动驾驶仪，然后转发给连接的类型为 '板载' 的 MAVLink 通道。
-PX4 还会将其在任务中遇到的任何相机任务项重新发出为相机命令：未被接受的命令将被记录。
+PX4 also re-emits any camera mission items it encounters in a mission as camera commands: commands that aren't accepted are logged.
 在所有情况下，命令都是使用自动驾驶仪的系统 ID 和组件 ID 为 0（即发送给所有组件，包括摄像头）。
 
 每次触发图像捕获时 PX4 也会发出一个 [CAMERA_TRIGGER](https://mavlink.io/en/messages/common.html#CAMERA_TRIGGER) (相机本身也可能在触发时发出此消息)。