!3780 翻译完成：3335 add sample+codelab

Merge pull request !3780 from wusongqing/TR3335

en/application-dev/device/sensor-guidelines.md

@@ -13,9 +13,9 @@
 
 - Data provided by the Hall effect sensor implements the smart cover mode of your device.
 
-- Data provided by the heart rate sensor helps your application track the health of a user.
+- Data provided by the heart rate sensor helps your application track the heart health of a user.
 
-- Data provided by the pedometer sensor helps your application obtain the number steps a user has walked.
+- Data provided by the pedometer sensor helps your application obtain the number of steps a user has walked.
 
 - Data provided by the wear detection sensor helps your application detect whether a user is wearing a wearable device.
 
@@ -31,7 +31,7 @@
 
 ## How to Develop
 
-1. To obtain data from a type of sensor, configure the request permissions in the **config.json** file.  
+1. To obtain data from a type of sensor, configure the requested permissions in the **config.json** file.  
   
    ```
    "reqPermissions":[
@@ -75,7 +75,7 @@
    ```
    import sensor from "@ohos.sensor"
    sensor.on(sensor.sensorType.SENSOR_TYPE_ACCELEROMETER,function(data){
-          console.info("Subscription succeeded. data = "+ data);// The call is successful, and the obtained sensor data is printed.
+          console.info("Subscription succeeded. data = "+ data); // The call is successful, and the obtained sensor data is printed.
      }
    );
    ```
@@ -89,7 +89,7 @@
    ```
    import sensor from "@ohos.sensor"
    sensor.off(sensor.sensorType.SENSOR_TYPE_ACCELEROMETER,function() {
-       console.info("Succeeded in unsubscribing from acceleration sensor data.");// The unsubscription is successful, and the result is printed.
+       console.info("Succeeded in unsubscribing from acceleration sensor data."); // The unsubscription is successful, and the result is printed.
      }
    );
    ```
@@ -103,7 +103,7 @@
    ```
    import sensor from "@ohos.sensor"
    sensor.once(sensor.sensorType.SENSOR_TYPE_ACCELEROMETER,function(data) {
-           console.info("Data obtained successfully. data=" + data);// The call is successful, and the obtained sensor data is printed.
+           console.info("Data obtained successfully. data=" + data); // The call is successful, and the obtained sensor data is printed.
      }
    );
    ```
@@ -117,9 +117,14 @@
     ```
     try {
       sensor.once(sensor.sensorType.SENSOR_TYPE_ACCELEROMETER,function(data) {
-          console.info("Data obtained successfully. data=" + data);// The call is successful, and the obtained sensor data is printed.
+          console.info("Data obtained successfully. data=" + data); // The call is successful, and the obtained sensor data is printed.
       });
     } catch (error) {
       console.error(error);
     }
     ```
+## Samples
+
+The following sample is provided to help you better understand how to develop sensors:
+
+- [`Sensor`: sensor (eTS, API 8)](https://gitee.com/openharmony/app_samples/tree/master/device/Sensor)

en/application-dev/device/sensor-overview.md

 # Sensor Overview
 
 
-Sensors in OpenHarmony are an abstraction of underlying hardware-based sensors. Your application can access the underlying sensors via the sensors. Using the APIs provided by sensors, you can query sensors on your device, subscribe to sensor data, customize algorithms based on sensor data, and develop various sensor-based applications, such as compass, fitness and health, and games applications.
+Sensors in OpenHarmony are an abstraction of underlying sensor hardware. Your application can access the underlying sensor hardware via the sensors. Using the APIs provided by sensors, you can query sensors on your device, subscribe to sensor data, customize algorithms based on sensor data, and develop various sensor-based applications, such as compass, motion-controlled games, and fitness and health applications.
 
 
 A sensor is a device to detect events or changes in an environment and send messages about the events or changes to another device (for example, a CPU). Generally, a sensor is composed of sensitive components and conversion components. Sensors are the cornerstone of the IoT. A unified sensor management framework is required to achieve data sensing at a low latency and low power consumption, thereby keeping up with requirements of "1+8+N" products or business in the Seamless AI Life Strategy. The sensor list is as follows:
 
-| Sensor Type                             | Sensor Name              | Description                                                        | Usage                                |
+| Type                             | Name              | Description                                                        | Usage                                |
 | --------------------------------------- | ------------------ | ------------------------------------------------------------ | ---------------------------------------- |
 | SENSOR_TYPE_ACCELEROMETER               | Acceleration sensor      | Measures the acceleration (including the gravity acceleration) applied to a device on three physical axes (X, Y, and Z), in the unit of m/s<sup>2</sup>.| Detecting the motion status                            |
 | SENSOR_TYPE_ACCELEROMETER_UNCALIBRATED  | Uncalibrated acceleration sensor| Measures the uncalibrated acceleration (including the gravity acceleration) applied to a device on three physical axes (X, Y, and Z), in the unit of m/s<sup>2</sup>.| Measuring the acceleration bias estimation                      |
@@ -56,7 +56,7 @@ The following modules work cooperatively to implement OpenHarmony sensors: Senso
 
    | Sensor                      | Permission                             | Sensitivity        | Permission Description                   |
    | ------------------------- | -------------------------------- | ------------ | ----------------------- |
-   | Acceleration sensor, uncalibrated acceleration sensor, and linear acceleration sensor| ohos.permission.ACCELEROMETER    | system_grant | Allows your application to subscribe to data of these acceleration-related sensors in the motion category.|
+   | Acceleration sensor, uncalibrated acceleration sensor, and linear acceleration sensor| ohos.permission.ACCELEROMETER    | system_grant | Allows an application to subscribe to data of these acceleration-related sensors in the motion category.|
    | Gyroscope sensor and uncalibrated gyroscope sensor         | ohos.permission.GYROSCOPE        | system_grant | Allows an application to subscribe to data of the gyroscope-related sensors in the motion category.|
    | Pedometer sensor                      | ohos.permission.ACTIVITY_MOTION  | user_grant   | Allows an application to subscribe to the motion status.               |
    | Heart rate sensor                      | ohos.permission.READ_HEALTH_DATA | user_grant   | Allows an application to read health data.               |

en/application-dev/device/vibrator-guidelines.md

@@ -3,7 +3,7 @@
 
 ## When to Use
 
-You can set different vibration effects as needed, for example, customizing vibration effects with different intensities and durations for buttons on the device, and customizing one-shot or periodic vibration effects with different intensities and durations for alarm clocks and incoming calls.
+You can set different vibration effects as needed, for example, customizing the vibration intensity, frequency, and duration for button touches, alarm clocks, and incoming calls.
 
 
 ## Available APIs
@@ -62,9 +62,9 @@ You can set different vibration effects as needed, for example, customizing vibr
    ```
    import vibrator from "@ohos.vibrator"
    vibrator.vibrate(1000).then((error)=>{
-       if (error) {// The call fails, and error.code and error.message are printed.
+       if (error){ // The call fails, and error.code and error.message are printed.
           Console.log("Promise return failed.error.code"+error.code+"error.message"+error.message);  
-       }else{// The call is successful, and the device starts to vibrate.
+       }else{ // The call is successful, and the device starts to vibrate.
           Console.log("Promise returned to indicate a successful vibration.")  
        };
    })
@@ -75,10 +75,16 @@ You can set different vibration effects as needed, for example, customizing vibr
    ```
    import vibrator from "@ohos.vibrator"
    vibrator.stop(vibrator.VibratorStopMode.VIBRATOR_STOP_MODE_PRESET).then((error)=>{
-      if (error) {// The call fails, and error.code and error.message are printed.
+      if(error){ // The call fails, and error.code and error.message are printed.
           Console.log("Promise return failed.error.code"+error.code+"error.message"+error.message);
-      }else{// The call is successful, and the device stops vibration.
+      }else{ // The call is successful, and the device stops vibration.
           Console.log("Promise returned to indicate a successful stop.");
       };
    })
    ```
+
+## Samples
+
+The following sample is provided to help you better understand how to develop vibrators:
+
+- [`Vibrator`: vibrator (eTS, API 8)](https://gitee.com/openharmony/app_samples/tree/master/device/Vibrator)

en/application-dev/device/vibrator-overview.md

 # Vibrator Overview
 
 
-The vibrator service opens up the latest capabilities of the vibrator hardware to the maximum extent. By expanding the native vibrator service to implement integrated vibration and interaction design, the service delivers an exquisite integrated vibration experience and differentiated experience, and improves user interaction efficiency and usability.
+The vibrator service is built on the native vibrator service, bolstered by the latest capabilities of the vibrator hardware. By innovatively integrating vibration and interaction, the service takes user interaction efficiency and usability to the next level.
 
 
 ## Working Principles
@@ -12,7 +12,7 @@ The vibrator is a Misc device that consists of four modules: Vibrator API, Vibra
 
 ![0752d302-aeb9-481a-bb8f-e5524eb61eeb](figures/0752d302-aeb9-481a-bb8f-e5524eb61eeb.png)
 
-- Vibrator API: provides basic vibrator APIs, including the APIs for querying the vibrator list, querying the vibrator by effect, and triggering and stopping vibration.
+- Vibrator API: provides basic vibrator APIs, including the APIs for obtaining the vibrator list, querying the vibrator by effect, and triggering and stopping vibration.
 
 - Vibrator Framework: manages the framework layer of the vibrator and communicates with the Misc Device Service.