!5566 翻译完成 4650：js-apis-uitest.md修改失败示例代码 等

Merge pull request !5566 from ester.zhou/C2-0617

en/application-dev/notification/common-event.md

@@ -13,7 +13,7 @@ Each application can subscribe to common events as required. After your applicat
 ## Common Event Subscription Development
 
 ### When to Use
-You can create a subscriber object to subscribe to a common event to obtain the parameters passed in the event. Certain system common events require specific permissions to subscribe to. For details, see [Required Permissions](../reference/apis/js-apis-commonEvent.md).
+You can create a subscriber object to subscribe to a common event to obtain the parameters passed in the event. Certain system common events require specific permissions to subscribe to. For details, see [Required Permissions](../reference/apis/js-apis-commonEvent.md#required-permissions).
 
 ### Available APIs
 | API                                                                                         | Description|
@@ -25,13 +25,13 @@ You can create a subscriber object to subscribe to a common event to obtain the
 ### How to Develop
 1. Import the **commonEvent** module.
 
-```javascript
+```js
 import commonEvent from '@ohos.commonEvent';
 ```
 
 2. Create a **subscribeInfo** object. For details about the data types and parameters of the object, see [CommonEventSubscribeInfo](../reference/apis/js-apis-commonEvent.md#commoneventsubscribeinfo).
 
-```javascript
+```js
 private subscriber = null	// Used to save the created subscriber object for subsequent subscription and unsubscription.
 
 // Subscriber information
@@ -42,7 +42,7 @@ var subscribeInfo = {
 
 3. Create a subscriber object and save the returned object for subsequent operations such as subscription and unsubscription.
 
-```javascript
+```js
 // Callback for subscriber creation.
 commonEvent.createSubscriber(subscribeInfo, (err, subscriber) => {
     if (err.code) {
@@ -57,7 +57,7 @@ commonEvent.createSubscriber(subscribeInfo, (err, subscriber) => {
 
 4. Create a subscription callback, which is triggered when an event is received. The data returned by the subscription callback contains information such as the common event name and data carried by the publisher. For details about the data types and parameters of the common event data, see [CommonEventData](../reference/apis/js-apis-commonEvent.md#commoneventdata).
 
-```javascript
+```js
 // Callback for common event subscription.
 if (this.subscriber != null) {
     commonEvent.subscribe(this.subscriber, (err, data) => {
@@ -74,7 +74,7 @@ if (this.subscriber != null) {
 }
 ```
 
-## Public Event Publishing Development
+## Common Event Publishing Development
 
 ### When to Use
 You can use the **publish** APIs to publish a custom common event, which can carry data for subscribers to parse and process.
@@ -89,13 +89,13 @@ You can use the **publish** APIs to publish a custom common event, which can car
 #### Development for Publishing a Common Event
 1. Import the **commonEvent** module.
 
-```javascript
+```js
 import commonEvent from '@ohos.commonEvent';
 ```
 
 2. Pass in the common event name and callback, and publish the event.
 
-```javascript
+```js
 // Publish a common event.
 commonEvent.publish("event", (err) => {
 	if (err.code) {
@@ -109,13 +109,13 @@ commonEvent.publish("event", (err) => {
 #### Development for Publishing a Common Event with Given Attributes
 1. Import the **commonEvent** module.
 
-```javascript
+```js
 import commonEvent from '@ohos.commonEvent'
 ```
 
 2. Define attributes of the common event to publish. For details about the data types and parameters in the data to publish, see [CommonEventPublishData](../reference/apis/js-apis-commonEvent.md#commoneventpublishdata).
 
-```javascript
+```js
 // Attributes of a common event.
 var options = {
 	code: 1,			 // Result code of the common event
@@ -125,7 +125,7 @@ var options = {
 
 3. Pass in the common event name, attributes of the common event, and callback, and publish the event.
 
-```javascript
+```js
 // Publish a common event.
 commonEvent.publish("event", options, (err) => {
 	if (err.code) {
@@ -149,14 +149,14 @@ You can use the **unsubscribe** API to unsubscribe from a common event.
 ### How to Develop
 1. Import the **commonEvent** module.
 
-```javascript
+```js
 import commonEvent from '@ohos.commonEvent';
 ```
 
 2. Subscribe to a common event by following instructions in [Common Event Subscription Development](#Common-Event-Subscription-Development).
 3. Invoke the **unsubscribe** API in **CommonEvent** to unsubscribe from the common event.
 
-```javascript
+```js
 if (this.subscriber != null) {
     commonEvent.unsubscribe(this.subscriber, (err) => {
         if (err.code) {

en/application-dev/quick-start/syscap.md

@@ -4,26 +4,26 @@
 
 ### System Capabilities and APIs
 
-SysCap is short for System Capability. It refers to a standalone feature in the operating system, for example, Bluetooth, Wi-Fi, NFC, or camera. Each system capability corresponds to a set of bound APIs, whose availability depends on the support of the target device. Such a set of APIs can be provided in the IDE for association.
+SysCap is short for System Capability. It refers to a standalone feature in the operating system, for example, Bluetooth, Wi-Fi, NFC, or camera. Each SysCap corresponds to a set of bound APIs, whose availability depends on the support of the target device. Such a set of APIs are provided in DevEco Studio for association.
 
 ![image-20220326064841782](figures/image-20220326064841782.png)
 
 
 
-### Supported Capability Set, Associated Capability Set, and Required Capability Set
+### Supported SysCap Set, Associated SysCap Set, and Required SysCap Set
 
-The supported capability set, associated capability set, and required capability set are collections of system capabilities.
-The supported capability set covers the device capabilities, and the required capability set covers the application capabilities. If the capability set required by application A is a subset of the capability set supported by device N, application A can be distributed to device N for installation and running. Otherwise, application A cannot be distributed.
-The associated capability set covers the system capabilities of associated APIs that the IDE offers during application development.
+The supported SysCap set, associated SysCap set, and required SysCap set are collections of SysCaps.
+The supported SysCap set covers the device capabilities, and the required SysCap set covers the application capabilities. If the SysCap set required by application A is a subset of the SysCap set supported by device N, application A can be distributed to device N for installation and running. Otherwise, application A cannot be distributed.
+The associated SysCap set covers the system capabilities of associated APIs that the IDE offers during application development.
 
 ![image-20220326064913834](figures/image-20220326064913834.png)
 
 
 
-### Devices and Supported Capability Sets
+### Devices and Supported SysCap Sets
 
-Each device provides a capability set that matches its hardware capability.
-The SDK classifies devices into general devices and custom devices. The general devices' supported capability set is defined by OpenHarmony, and the custom devices' is defined by device vendors.
+Each device provides a SysCap set that matches its hardware capability.
+The SDK classifies devices into general devices and custom devices. The general devices' supported SysCap set is defined by OpenHarmony, and the custom devices' is defined by device vendors.
 
 ![image-20220326064955505](figures/image-20220326064955505.png)
 
@@ -31,7 +31,7 @@ The SDK classifies devices into general devices and custom devices. The general
 
 ### Mapping Between Devices and SDK Capabilities
 
-The SDK provides a full set of APIs for the IDE. The IDE identifies the supported capability set based on the devices supported by the project, filters the APIs contained in the capability set, and provides the supported APIs for association (to autocomplete input).
+The SDK provides a full set of APIs for the IDE. DevEco Studio identifies the supported SysCap set based on the devices supported by the project, filters the APIs contained in the SysCap set, and provides the supported APIs for association (to autocomplete input).
 
 ![image-20220326065043006](figures/image-20220326065043006.png)
 
@@ -49,11 +49,11 @@ Right-click the project directory and choose **Import Product Compatibility ID**
 
 
 
-### Configuring the Associated Capability Set and Required Capability Set
+### Configuring the Associated SysCap Set and Required SysCap Set
 
-The IDE automatically configures the associated capability set and required capability set based on the settings supported by the created project. You can modify the capability sets when necessary.
-You can add APIs to the associated capability set in the IDE by adding system capabilities. However, note that these APIs may not be supported on the device. Therefore, check whether these APIs are supported before using them.
-Exercise caution when modifying the required capability set. Incorrect modifications may cause the application to unable to be distributed to the target device.
+DevEco Studio automatically configures the associated SysCap set and required SysCap set based on the settings supported by the created project. You can modify these SysCap sets when necessary.
+You can add APIs to the associated SysCap set in DevEco Studio by adding system capabilities. However, note that these APIs may not be supported on the device. Therefore, check whether these APIs are supported before using them.
+Exercise caution when modifying the required SysCap set. Incorrect modifications may result in the application being unable to be distributed to the target device.
 
 ```
 /* syscap.json */
@@ -74,15 +74,15 @@ Exercise caution when modifying the required capability set. Incorrect modificat
 			...
 		]
 	},
-	development: {             /* The SysCap set in addedSysCaps and the SysCap set supported by each device configured in devices form the associated capability set. */
+	development: {             /* The SysCap set in addedSysCaps and the SysCap set supported by each device configured in devices form the associated SysCap set. */
 		addedSysCaps: [
 			"SystemCapability.Location.Location.Lite",
 			...
 		]
 	},
 	production: {              /* Used to generate the RPCID. Exercise caution when adding this parameter. Under incorrect settings, applications may fail to be distributed to target devices. */
-		addedSysCaps: [],      // Intersection of SysCap sets supported by devices configured in devices. It is the required capability set with addedSysCaps set and removedSysCaps set.
-		removedSysCaps: []     // When the required capability set is a capability subset of a device, the application can be distributed to the device.
+		addedSysCaps: [],      // Intersection of SysCap sets supported by devices configured in devices. It is the required SysCap set with addedSysCaps set and removedSysCaps set.
+		removedSysCaps: []     // When the required SysCap set is a capability subset of a device, the application can be distributed to the device.
 	}
 }
 ```
@@ -91,7 +91,7 @@ Exercise caution when modifying the required capability set. Incorrect modificat
 
 ### Single-Device Application Development
 
-By default, the association capability set and required system capability set of the application are the same as the supported system capability set of the device. Exercise caution when modifying the required capability set.
+By default, the associated SysCap set and required SysCap set of the application are the same as the supported SysCap set of the device. Exercise caution when modifying the required SysCap set.
 
 ![image-20220326065124911](figures/image-20220326065124911.png)
 
@@ -99,7 +99,7 @@ By default, the association capability set and required system capability set of
 
 ### Cross-Device Application Development
 
-By default, the associated capability set of the application is the union of multiple devices' supported capability sets. The capability sets must be the intersection.
+By default, the associated SysCap set of an application is the union of multiple devices' supported SysCap sets, while the required SysCap set is the intersection of the devices' supported SysCap sets.
 
 ![image-20220326065201867](figures/image-20220326065201867.png)
 
@@ -133,9 +133,9 @@ if (geolocation) {
 
 
 
-### Checking the Differences Between Devices with the Same Capability
+### Checking the Differences Between Devices with a Specific SysCap
 
-The performance of a system capability may vary by device type. For example, a tablet is superior to a smart wearable device in terms of the camera capability.
+The performance of a SysCap may vary by device type. For example, a tablet is superior to a smart wearable device in terms of the camera capability.
 
 ```
 import userAuth from '@ohos.userIAM.userAuth';
@@ -158,11 +158,11 @@ authenticator.execute('FACE_ONLY', 'S1', (err, result) => {
 
 ### How Do SysCap Differences Arise Between Devices
 
-The SysCap of devices varies according to the component combination defined by the product solution vendor. The following figure shows the overall process.
+The device SysCaps in product solutions vary according to the component combination defined by the product solution vendor. The following figure shows the overall process.
 
 ![image-20220326072448840](figures/image-20220326072448840.png)
 
-1. A set of OpenHarmony source code consists of optional and mandatory components. Different components have different system capabilities. In other words, different components represent different SysCaps.
+1. A set of OpenHarmony source code consists of optional and mandatory components. Different components represent different SysCaps.
 
 2. In a normalized released SDK, APIs are mapped to SysCap sets.
 
@@ -170,10 +170,10 @@ The SysCap of devices varies according to the component combination defined by t
 
 4. The components configured for a product can be OpenHarmony components or proprietary components developed by a third party. Since there is mapping between components and SysCap, the SysCap set of the product can be obtained after all components are assembled.
 
-5. The SysCap set is encoded to generate the PCID. You can import the PCID to the IDE and decode it into SysCap. During development, compatibility processing is performed to mitigate the SysCap differences of devices.
+5. The SysCap set is encoded to generate the PCID. You can import the PCID to DevEco Studio and decode it into SysCaps. During development, compatibility processing is performed to mitigate the SysCap differences of devices.
 
-6. System parameters deployed on devices contain the SysCap set. The system provides native interfaces and application interfaces for components and applications to check whether a SysCap set is available.
+6. System parameters deployed on devices contain the SysCap set. The system provides native interfaces and application interfaces for components and applications to check whether a specific SysCap is available.
 
-7. During application development, the SysCap required by the application is encoded into the Required Product Compatibility ID (RPCID) and written into the application installation package. During application installation, the package manager decodes the RPCID to obtain the SysCap required by the application and compares it with the SysCap of the device. If the SysCap required by the application is met, the application can be installed.
+7. During application development, the SysCap set required by the application is encoded into the Required Product Compatibility ID (RPCID) and written into the application installation package. During application installation, the package manager decodes the RPCID to obtain the SysCap set required by the application and compares it with the SysCap set supported by the device. If the SysCap set required by the application is met, the application can be installed on the device.
 
-8. When an application is running, the **canIUse** API can be used to query whether the SysCap is compatible with the device.
+8. When an application is running on a device, the **canIUse** API can be used to query whether the device is compatible with a specific SysCap.

en/application-dev/reference/arkui-ts/ts-interpolation-calculation.md

 # Interpolation Calculation
 
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**<br>
 > This animation is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
 
@@ -31,7 +31,8 @@ Implements initialization for the interpolation curve, which is used to create a
   | -------- | -------- | -------- | -------- | -------- |
   | curve | Curve | No | Linear | Curve object. |
 
-- Return values
+- Return value
+  
   Curve object.
 
 
@@ -47,9 +48,10 @@ Constructs a step curve object.
     | Name | Type | Mandatory | Default Value | Description |
   | -------- | -------- | -------- | -------- | -------- |
   | count | number | Yes | - | Number of steps. Must be a positive integer. |
-  | end | boolean | No | true | Step change at the start or end point of each interval. Defaults to **true**, indicating that the step change occurs at the end point. | 
+  | end | boolean | Yes | true | Step change at the start or end point of each interval. Defaults to **true**, indicating that the step change occurs at the end point. |
+
+- Return value
   
-- Return values
   Curve object.
 
 
@@ -69,7 +71,8 @@ Constructs a third-order Bezier curve object. The curve value must be between 0
   | x2 | number | Yes | Horizontal coordinate of the second point on the Bezier curve. |
   | y2 | number | Yes | Vertical coordinate of the second point on the Bezier curve. |
 
-- Return values
+- Return value
+  
   Curve object.
 
 
@@ -89,7 +92,8 @@ Constructs a spring curve object.
   | stiffness | number | Yes | Stiffness. |
   | damping | number | Yes | Damping. |
 
-- Return values
+- Return value
+  
   Curve object.
 
 
@@ -105,8 +109,8 @@ let curve3 = Curves.cubicBezier(0.1, 0.0, 0.1, 1.0) // Create a third-order Bezi
 ```
 
 
-  Curve objects can be created only by the preceding APIs.
-  | API | Description | 
+Curve objects can be created only by the preceding APIs.
+| API | Description |
 | -------- | -------- |
 | interpolate(time: number): number | Calculation function of the interpolation curve. Passing a normalized time parameter to this function returns the current interpolation.<br/>**time**: indicates the current normalized time. The value ranges from 0 to 1.<br/>The curve interpolation corresponding to the normalized time point is returned. |
 

en/application-dev/ui/js-framework-resource-restriction.md

@@ -25,7 +25,7 @@ The name of a resource qualifier consists of one or more qualifiers that represe
 
 | Data Type | Description and Value Range |
 | -------- | -------- |
-| Screen density | Indicates the screen density of the device, in dpi. The value can be:<br/>- ldpi: low-density screen (~120 dpi) (0.75 x Reference density)<br/>- mdpi: medium-density screen (~160 dpi) (reference density)<br/>- hdpi: high-density screen (~240 dpi) (1.5 x Reference density)<br/>- xhdpi: extra high-density screen (~320 dpi) (2.0 x Reference density)<br/>- xxhdpi: extra extra high-density screen (~480 dpi) (3.0 x Reference density)<br/>- xxxhdpi: extra extra extra high-density screen (~640 dpi) (4.0 x Reference density) | 
+| Screen density | Indicates the screen density of the device, in dpi. The value can be:<br/>- ldpi: low-density screen (\~120 dpi) (0.75 x Reference density)<br/>- mdpi: medium-density screen (\~160 dpi) (reference density)<br/>- hdpi: high-density screen (\~240 dpi) (1.5 x Reference density)<br/>- xhdpi: extra high-density screen (\~320 dpi) (2.0 x Reference density)<br/>- xxhdpi: extra extra high-density screen (\~480 dpi) (3.0 x Reference density)<br/>- xxxhdpi: extra extra extra high-density screen (\~640 dpi) (4.0 x Reference density) |
 
 
 ## Rules for Matching Qualifiers Files and Device Resources
@@ -91,5 +91,5 @@ resources/res-defaults.json:
 </div>
 ```
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**:
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
 > The resource qualifier file does not support color enumeration.

en/application-dev/ui/ts-component-based-styles.md

 # @Styles
 
 
-The @Styles decorator adds new attribute functions to basic components, such as <Text>, <Column>, and <Button>. Currently, @Styles supports only universal attributes. You can use the @Styles decorator to quickly define and reuse the custom styles of a component.
+The **@Styles** decorator adds new attribute functions to basic components, such as **\<Text>**, **\<Column>**, and **\<Button>**. Currently, **@Styles** supports only universal attributes. You can use the **@Styles** decorator to quickly define and reuse the custom styles of a component.
 
-
-@Styles can be defined inside or outside a component. When it is defined outside a component, the keyword function must be included.
+**@Styles** can be defined inside or outside a component. When it is defined outside a component, the keyword function must be included.
 
 
 
@@ -36,11 +35,10 @@ struct FancyUse {
 }
 ```
 
-
-@Styles can also be used inside the StateStyles attribute to assign state-specific attributes to components.
+**@Styles** can also be used inside the **StateStyles** attribute to assign state-specific attributes to components.
 
 
-In StateStyles, styles defined outside the component can be directly called. However, the keyword this must be used to call styles defined in the component.
+In **StateStyles**, styles defined outside the component can be directly called. However, the keyword **this** must be used to call styles defined in the component.
 
 
 
@@ -53,7 +51,7 @@ In StateStyles, styles defined outside the component can be directly called. How
 @Entry
 @Component
 struct FancyUse {
-  @Styles function componentFancy() {
+  @Styles componentFancy() {
     .width(50)
     .height(50)
   }