diff --git a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
index 02af97b2e93f..c3c747255757 100644
--- a/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/zh_CN/RemoteFeatures/RemoteControl.md
@@ -44,42 +44,42 @@ _注意：对于AAPS 3.2及更高版本，**NSClient**已被**AAPSClient**替代
 
 通过USB数据线传输到跟随者手机上；或者， 拖动到Google Drive文件夹中，然后点击“app-AAPSClient-release”文件将其添加到跟随者手机。
 
-### Synchronization- AAPSClient and AAPS set up (for Version 3.2.0.0 above)
+### 同步-AAPSClient和AAPS的设置（适用于3.2.0.0及以上版本）
 
-Once __AAPSClient__ apk is installed on the follower phone, the user must ensure their ‘Preferences’ in Config Builder are correctly set up and aligned with __AAPS__ for Nightscout 15 (see Release Notes [here](../Maintenance/UpdateToNewVersion)). The example below provides Synchronization guidance for NSClient and NSClientV3 using Nightscout15 but there are other options available with __AAPS__ (e.g xDrip+).
+一旦在跟随者手机上安装了__AAPSClient__ apk，用户必须确保其在Config Builder中的“Preferences”正确设置并与Nightscout 15的__AAPS__对齐（请参阅[此处](../Maintenance/UpdateToNewVersion)的发布说明）。 下面的示例提供了使用Nightscout15的NSClient和NSClientV3的同步指南，但__AAPS__还有其他可用选项（例如xDrip+）。
 
-Within the ‘Synchronization’ located under ‘Config Builder’, the user can opt for either Synchronization options for both __AAPS__ and follower phone being:
+在“Config Builder”下的“Synchronization”中，用户可以选择__AAPS__和跟随者手机都适用的同步选项：
 
-- Option 1: NSClient (also known as ‘v1’) - which synchronizes the user’s data with Nightscout; or
+- 选项1：NSClient（也称为“v1”）- 将用户的数据与Nightscout同步；
 
-- Option 2: NSClientV3 (also referred to as ‘v3’).- which synchronizes the user’s data with Nightscout using v3 API.
+- 选项2：NSClientV3（也称为“v3”）- 使用v3 API将用户的数据与Nightscout同步。
 
 ![AAPS1_Screenshot 2024-05-17 133502](../images/4bdfed7e-3b2f-4fe8-b6db-6fcf0e5c7d98.png)
 
-The user must ensure that __both__ the AAPS and AAPS Client phones are synched together by actioning either option for v1 or v3 being:
+用户必须确保AAPS和AAPSClient手机__都__通过选择v1或v3的选项进行同步：
 
-Option 1: v1 for both phones:
+选项1：两台手机都使用v1：
 
-- Enter your Nightscout URL
+- 输入您的Nightscout URL
 
-- Enter your API secret
+- 输入您的API密钥
 
-Option 2: v3 for both phones:
+选项2：两台手机都使用v3：
 
-- Enter your Nightscout URL under NSClientV3 tab
+- 在NSClientV3标签下输入您的Nightscout URL
 
-- Enter your NS access token under ‘Config Build’ tab. Please follow the notes [here](https://nightscout.github.io/nightscout/security/#create-a-token)
+- 在“Config Build”标签下输入您的NS访问令牌。 请按照[此处](https://nightscout.github.io/nightscout/security/#create-a-token)的说明操作
 
-If selecting Websockets (which is optional) ensure this is activated or deactivated for both __AAPS’__ and __AAPSClient’s__ phone. Activating Websockets in __AAPS__ and not within __AAPSClient__ (and vice versa) will only cause __AAPS__ to malfunction. By enabling websockets will allow for faster synchronization with Nightscout but may lead to more phone battery consumption.
+如果选择Websockets（这是可选的），请确保它在__AAPS__和__AAPSClient__手机中均已激活或停用。 在__AAPS__中激活Websockets而在__AAPSClient__中未激活（反之亦然）将导致__AAPS__出现故障。 启用Websockets将允许与Nightscout更快同步，但可能导致手机电池消耗更多。
 
 ![WB2_Screenshot 2024-05-17 140548](../images/d9a7dc5-b3ea-4bf3-9286-313f329b1966.png)
 
 
-Users should ensure that both __AAPSClient__ and __AAPS__ are showing  ‘connected’ under the ‘NSClient' tab for each phone, and that ‘Profile Switches’ or ‘Temp Target' can be correctly activated in __AAPS__ once selected in __AAPSClient__.
+用户应确保__AAPSClient__和__AAPS__在各自手机的“NSClient”标签下均显示“已连接”，并且一旦在__AAPSClient__中选择，就可以在__AAPS__中正确激活“Profile Switches”或“Temp Target”。
 
-Users should also ensure that carbs are logged in both ‘Treatments’ within both __AAPSClient__ and __AAPS__ otherwise this could indicate a malfunction within the user’s set up.
+用户还应确保在__AAPSClient__和__AAPS__的“Treatments”中都记录了碳水化合物，否则可能表明用户设置出现故障。
 
-### Troubleshooting 'NS access token' configuration issues
+### 故障排除“NS访问令牌”配置问题
 
 The precise 'NS access token' configuration may differ depending upon whether your Nightscout provider is a paid for hosted site or not.