New Crowdin translations - zh-CN (#25256)

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

docs/zh/ros/external_position_estimation.md

@@ -90,9 +90,7 @@ You can also disable GNSS, baro and range finder fusion using [EKF2_GPS_CTRL](..
 Reboot the flight controller in order for parameter changes to take effect.
 :::
 
-<a id="tuning-EKF2_EV_DELAY"></a>
-
-#### 调参 EKF2_EV_DELAY
+#### Tuning EKF2_EV_DELAY {#tuning-EKF2_EV_DELAY}
 
 [EKF2_EV_DELAY](../advanced_config/parameter_reference.md#EKF2_EV_DELAY) is the _Vision Position Estimator delay relative to IMU measurements_.
 
@@ -171,9 +169,7 @@ VIO and MoCap systems have different ways of obtaining pose data, and have their
 The setup for specific systems is covered [below](#setup_specific_systems).
 When using external heading estimation, magnetic North is ignored and faked with a vector corresponding to world <em x-id="3">x</em> axis (which can be placed freely during Vision/MoCap calibration). Yaw angle is therefore given with respect to local <em x-id="3">x</em>.
 
-<a id="relaying_pose_data_to_px4"></a>
-
-### 将数据回传给 PX4
+### Relaying Pose Data to PX4 {#relaying_pose_data_to_px4}
 
 MAVROS has plugins to relay a visual estimation from a VIO or MoCap system using the following pipelines:
 
@@ -253,13 +249,11 @@ When using the MAVROS _odom_ plugin, it is important that no other node is publi
 This might break the _tf_ tree.
 :::
 
-<a id="setup_specific_systems"></a>
-
-## 特定的系统设置
+## Specific System Setups {#setup_specific_systems}
 
 ### 光学跟踪 MoCap
 
-The following steps explain how to feed position estimates from an [OptiTrack](https://optitrack.com/motion-capture-robotics/) system to PX4.
+The following steps explain how to feed position estimates from an [OptiTrack](https://optitrack.com/applications/robotics/) system to PX4.
 It is assumed that the MoCap system is calibrated.
 See [this video](https://www.youtube.com/watch?v=cNZaFEghTBU) for a tutorial on the calibration process.