Merge branch 'OpenHarmony-4.0-Beta2' of gitee.com:openharmony/docs into weekly

Signed-off-by: Nxieqiongyang <xieqiongyang@huawei.com>

zh-cn/application-dev/application-models/atomic-services-support-sharing.md → en/application-dev/application-models/atomic-services-support-sharing.md

-# 设置原子化服务支持分享
-## 原子化服务分享
+# Setting Atomic Services to Support Sharing
+## How to Develop
 
-1. UIAbility组件提供了[UIAbility.onShare()](../reference/apis/js-apis-app-ability-uiAbility.md#onshare)生命周期方法，应用可通过此方法设置要分享的数据。其中，ohos.extra.param.key.contentTitle表示分享框中对分享内容title的描述，ohos.extra.param.key.shareAbstract表示分享框中对携带内容的摘要描述，ohos.extra.param.key.shareUrl表示服务的在线地址。以上三项分享数据均是开发者填充，且为Object对象，对象的key分别为title，abstract，url。
+1. An application calls [UIAbility.onShare()](../reference/apis/js-apis-app-ability-uiAbility.md#onshare), a lifecycle callback provided by the UIAbility component, to set the data to share. In this lifecycle callback, **ohos.extra.param.key.contentTitle** indicates the title of the content to share in the sharing box, **ohos.extra.param.key.shareAbstract** provides an abstract description of the content, and **ohos.extra.param.key.shareUrl** indicates the online address of the service. You need to set these three items as objects, with the key set to **title**, **abstract**, and **url**, respectively.
 
    ```ts
    import AbilityConstant from '@ohos.app.ability.AbilityConstant';
@@ -15,7 +15,7 @@
    }
    ```
 
-2. 系统弹框调用[abilityManager.acquireShareData()](../reference/apis/js-apis-app-ability-abilityManager.md#acquiresharedata)接口发起原子化服务共享，根据missionId找到对应的UIAbility，调用其OnShare生命周期，收到共享数据。
+2. A system dialog box calls [abilityManager.acquireShareData()](../reference/apis/js-apis-app-ability-abilityManager.md#acquiresharedata) to obtain data shared through atomic service sharing. Specifically, the system finds the UIAbility based on the mission ID and calls the **OnShare()** lifecycle of the UIAbility to obtain the shared data.
 
    ```ts
    import abilityManager from '@ohos.app.ability.abilityManager';

en/application-dev/arkts-utils/linear-container.md

@@ -44,14 +44,14 @@ The APIs provided by **Vector** are deprecated since API version 9. You are advi
 | Accessing elements| Use **vec\[index]** to obtain the value at a given position (specified by **index**).|
 | Accessing elements| Use **get(index: number)** to obtain the element at a given position (specified by **index**).|
 | Accessing elements| Use **getLastElement()** to obtain the last element in this container.|
-| Accessing elements| Use **getlndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
-| Accessing elements| Use **getLastlndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
+| Accessing elements| Use **getIndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
+| Accessing elements| Use **getLastIndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
 | Accessing elements| Use **forEach(callbackFn: (value: T, index?: number, Vector?: Vector<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator<T>** for data access.|
 | Modifying elements| Use **vec\[index]=xxx** to change the value at a given position (specified by **index**).|
 | Modifying elements| Use **set(index: number, element: T)** to replace an element at a given position (specified by **index**) with a given element.|
 | Modifying elements| Use **setLength(newSize: number)** to set the size of this container.|
-| Deleting elements| Use **removeBylndex(index: number)** to remove the value at a given position (specified by **index**).|
+| Deleting elements| Use **removeByIndex(index: number)** to remove the value at a given position (specified by **index**).|
 | Deleting elements| Use **remove(element: T)** to remove the first occurrence of the specified element.|
 | Deleting elements| Use **removeByRange(fromIndex: number, toIndex: number)** to remove all of the elements within a range.|
 
@@ -74,14 +74,14 @@ You are advised to use **List** for frequent insertion and removal operations.
 | Accessing elements| Use **get(index: number)** to obtain the element at a given position (specified by **index**).|
 | Accessing elements| Use **getFirst()** to obtain the first element in this container.|
 | Accessing elements| Use **getLast()** to obtain the last element in this container.|
-| Accessing elements| Use **getlndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
-| Accessing elements| Use **getLastlndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
+| Accessing elements| Use **getIndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
+| Accessing elements| Use **getLastIndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
 | Accessing elements| Use **forEach(callbackfn: (value: T, index?: number, list?: List<T>)=> void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator<T>** for data access.|
 | Modifying elements| Use **list\[index] = xxx** to change the value at a given position (specified by **index**).|
 | Modifying elements| Use **set(index: number, element: T)** to replace an element at a given position (specified by **index**) with a given element.|
 | Modifying elements| Use **replaceAllElements(callbackFn:(value: T,index?: number,list?: List<T>)=>T,thisArg?: Object)** to replace all elements in this container with new elements.|
-| Deleting elements| Use **removeBylndex(index: number)** to remove the value at a given position (specified by **index**).|
+| Deleting elements| Use **removeByIndex(index: number)** to remove the value at a given position (specified by **index**).|
 | Deleting elements| Use **remove(element: T)** to remove the first occurrence of the specified element.|
 
 
@@ -105,13 +105,13 @@ You are advised to use **LinkedList** for frequent insertion and removal operati
 | Accessing elements| Use **get(index: number)** to obtain the element at a given position (specified by **index**).|
 | Accessing elements| Use **getFirst()** to obtain the first element in this container.|
 | Accessing elements| Use **getLast()** to obtain the last element in this container.|
-| Accessing elements| Use **getlndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
-| Accessing elements| Use **getLastlndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
+| Accessing elements| Use **getIndexOf(element: T)** to obtain the index of the first occurrence of the specified element.|
+| Accessing elements| Use **getLastIndexOf(element: T)** to obtain the index of the last occurrence of the specified element.|
 | Accessing elements| Use **forEach(callbackFn: (value: T, index?: number, list?: LinkedList<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator<T>** for data access.|
 | Modifying elements| Use **list\[index]=xxx** to change the value at a given position (specified by **index**).|
 | Modifying elements| Use **set(index: number, element: T)** to replace an element at a given position (specified by **index**) with a given element.|
-| Deleting elements| Use **removeBylndex(index: number)** to remove the value at a given position (specified by **index**).|
+| Deleting elements| Use **removeByIndex(index: number)** to remove the value at a given position (specified by **index**).|
 | Deleting elements| Use **remove(element: T)** to remove the first occurrence of the specified element.|
 
 

en/application-dev/arkts-utils/multi-thread-concurrency-overview.md

@@ -12,7 +12,7 @@ Due to the memory isolation feature of the actor model, cross-thread serializati
 
 ## Data Transfer Objects
 
-Data objects that can be transferred are classified into three types: [common objects](#common-objects), [transferable objects](#transferable-objects), and [shared objects](#shared-objects).
+Data objects that can be transferred are classified into the following types: [common objects](#common-objects), [transferable objects](#transferable-objects), [shared objects](#shared-objects), and [native binding objects](#native-binding-objects).
 
 
 ### Common Objects
@@ -24,7 +24,7 @@ The following object types are supported: basic types except Symbol, Date, Strin
 
 ### Transferable Objects
 
-Transferable objects are serialized through address transfer. It transfers the ownership of an object of the ArrayBuffer type object, rather than the content in it. After the ownership is transferred, the object becomes unavailable in the sender and can be used only in the receiver.
+Transferable objects are serialized through address transfer. It transfers the ownership of an object of the ArrayBuffer type, rather than the content in it. After the ownership is transferred, the object becomes unavailable in the sender and can be used only in the receiver.
 
 
 ```js
@@ -47,6 +47,15 @@ If multiple operations are simultaneously performed to modify data stored in an
 let sharedBuffer = new SharedArrayBuffer(1024);
 ```
 
+### Native Binding Objects
+
+Native binding objects are provided by the system. They are bound to underlying system services and enables direct access to these services.
+
+Currently, native bound objects that support serialization include [Context](../application-models/application-context-stage.md) and [RemoteObject](../reference/apis/js-apis-rpc.md#remoteobject).
+
+The **Context** object provides the context information about an application component. It provides a way to access system services and resources so that the application component can interact with the system. For details about how to obtain context information, see [Context (Stage Model)](../application-models/application-context-stage.md).
+
+The **RemoteObject** object implements remote communication. It transfers the reference of an object between processes so that these processes can share the status and methods of the object. The service provider must inherit this class. For details about how to create a **RemoteObject** object, see [RemoteObject](../reference/apis/js-apis-rpc.md#remoteobject).
 
 ## TaskPool and Worker
 

en/application-dev/arkts-utils/nonlinear-container.md

@@ -52,9 +52,9 @@ You are advised to use **HashSet** when you need a set that has only unique elem
 | Adding elements| Use **add(value: T)** to add a value to this container.|
 | Accessing elements| Use **values()** to return an iterator that contains all the values in this container.|
 | Accessing elements| Use **entries()** to return an iterator that contains all the elements in this container.|
-| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: HashSet<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
+| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: HashSet\<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator&lt;T&gt;** for data access.|
-| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: HashSet<T>) => void, thisArg?: Object)** to change a value in this container.|
+| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: HashSet\<T>) => void, thisArg?: Object)** to change a value in this container.|
 | Deleting elements| Use **remove(value: T)** to remove a value.|
 | Deleting elements| Use **clear()** to clear this container.|
 
@@ -109,9 +109,9 @@ You are advised to use **TreeSet** when you need to store data in sorted order.
 | Accessing elements| Use **entries()** to return an iterator that contains all the elements in this container.|
 | Accessing elements| Use **getFirstValue()** to obtain the first value in this container.|
 | Accessing elements| Use **getLastValue()** to obtain the last value in this container.|
-| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: TreeSet<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
+| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: TreeSet\<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator&lt;T&gt;** for data access.|
-| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: TreeSet<T>) => void, thisArg?: Object)** to change a value in this container.|
+| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: TreeSet\<T>) => void, thisArg?: Object)** to change a value in this container.|
 | Deleting elements| Use **remove(value: T)** to remove a value.|
 | Deleting elements| Use **clear()** to clear this container.|
 
@@ -169,9 +169,9 @@ You are advised to use **LightWeightSet** when you need a set that has only uniq
 | Accessing elements| Use **values()** to return an iterator that contains all the values in this container.|
 | Accessing elements| Use **entries()** to return an iterator that contains all the elements in this container.|
 | Accessing elements| Use **getValueAt(index: number)** to obtain the value of an element at a given position (specified by **index**).|
-| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: LightWeightSet<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
+| Accessing elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: LightWeightSet\<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator&lt;T&gt;** for data access.|
-| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: LightWeightSet<T>) => void, thisArg?: Object)** to change a value in this container.|
+| Modifying elements| Use **forEach(callbackFn: (value?: T, key?: T, set?: LightWeightSet\<T>) => void, thisArg?: Object)** to change a value in this container.|
 | Deleting elements| Use **remove(key: K)** to remove an element with the specified key.|
 | Deleting elements| Use **removeAt(index: number)** to remove an element at a given position (specified by **index**).|
 | Deleting elements| Use **clear()** to clear this container.|
@@ -197,10 +197,10 @@ You are advised to use PlainArray when you need to store KV pairs whose keys are
 | Accessing elements| Use **getIndexOfValue(value: T)** to obtain the index of the specified value.|
 | Accessing elements| Use **getKeyAt(index: number)** to obtain the key of an element at a given position (specified by **index**).|
 | Accessing elements| Use **getValueAt(index: number)** to obtain the value of an element at a given position (specified by **index**).|
-| Accessing elements| Use **forEach(callbackFn: (value: T, index?: number, PlainArray?: PlainArray<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
+| Accessing elements| Use **forEach(callbackFn: (value: T, index?: number, PlainArray?: PlainArray\<T>) => void, thisArg?: Object)** to traverse the elements in this container.|
 | Accessing elements| Use **\[Symbol.iterator]():IterableIterator&lt;[number, T]&gt;** for data access.|
 | Modifying elements| Use **setValueAt(index:number, value: T)** to change the value of an element at a given position (specified by **index**).|
-| Modifying elements| Use **forEach(callbackFn: (value: T, index?: number, PlainArray?: PlainArray<T>) => void, thisArg?: Object)** to modify an element in this container.|
+| Modifying elements| Use **forEach(callbackFn: (value: T, index?: number, PlainArray?: PlainArray\<T>) => void, thisArg?: Object)** to modify an element in this container.|
 | Deleting elements| Use **remove(key: number)** to remove an element with the specified key.|
 | Deleting elements| Use **removeAt(index: number)** to remove an element at a given position (specified by **index**).|
 | Deleting elements| Use **removeRangeFrom(index: number, size: number)** to remove elements in a specified range.|

en/application-dev/arkts-utils/xml-parsing.md

@@ -4,7 +4,7 @@
 Data transferred in XML format must be parsed in actual use. Generally, three types of elements need to be parsed, as described in [Parsing XML Tags and Tag Values](#parsing-xml-tags-and-tag-values), [Parsing XML Attributes and Attribute Values](#parsing-xml-attributes-and-attribute-values), and [Parsing XML Event Types and Element Depths](#parsing-xml-event-types-and-element-depths).
 
 
-The **xml** module provides the **XmlPullParser** class to parse XML files. The input is an object of the ArrayBufffer or DataView type containing XML text, and the output is the parsed information.
+The **xml** module provides the **XmlPullParser** class to parse XML files. The input is an object of the ArrayBuffer or DataView type containing XML text, and the output is the parsed information.
 
 
 **Table 1** XML parsing options

en/application-dev/faqs/faqs-arkui-animation-interactive-event.md

@@ -38,8 +38,9 @@ Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
 **Solution**
 
-- Add **focusable\(true\)** to the list item to enable it to obtain focus.
+ Use either of the following:
 
+- Add **focusable\(true\)** to the list item to enable it to obtain focus.
 - Nest a focusable component, for example, **\<Button>**, at the outer layer of each item.
 
 ## Why is the click event not triggered for the focused component upon the press of the Enter key after keyboard navigation?
@@ -139,6 +140,8 @@ Currently, the menu is displayed when the bound component is clicked or long pre
 
 Applicable to: OpenHarmony 3.2 Beta5 (API version 9)
 
+**Solution**
+
 Set the **focusable** attribute of the **\<TextInput>** component to **false**. In this way, the component is not focusable and therefore will not bring up the keyboard.
 
 ## How do I implement the slide up and slide down effect for page transition?
@@ -199,7 +202,7 @@ Applicable to: OpenHarmony 3.2 Beta5 (API version 9)
 
 **Symptom**
 
-Custom components A and B need to deliver the following effects: When custom component A, displayed at the bottom of the screen by default, is touched, it is hidden, and custom component B slides in from the bottom. When custom component B is touched, it is hidden, and custom component A slides in from the bottom.
+Custom components A and B need to deliver the following effects: When custom component A, displayed at the bottom of the screen by default, is touched, it is hidden, and custom component B slides in from the bottom; when custom component B is touched, it is hidden, and custom component A slides in from the bottom.
 
 **Solution**
 
@@ -266,4 +269,4 @@ struct ComponentChild2 {
 
 **Reference**
 
-[Transition Animation Within the Component](../ui/arkts-enter-exit-transition.md)
+[Enter/Exit Transition](../ui/arkts-enter-exit-transition.md)

en/application-dev/napi/native-buffer-guidelines.md

@@ -26,6 +26,13 @@ For details about the APIs, see [native_buffer](../reference/native-apis/_o_h___
 
 The following describes how to use the native APIs provided by **NativeBuffer** to create an **OH_NativeBuffer** instance, obtain memory properties, and map the corresponding ION memory to the process address space.
 
+**Adding Dynamic Link Libraries**
+
+Add the following library to **CMakeLists.txt**:
+```txt
+libnative_buffer.so
+```
+
 **Header File**
 ```c++
 #include <native_buffer/native_buffer.h>
@@ -52,7 +59,7 @@ The following describes how to use the native APIs provided by **NativeBuffer**
         std::cout << "OH_NativeBuffer_Map Failed" << std::endl;
     }
     
-    // Unmap the ION memory from the process address space when it is no longer needed.
+// Unmap the ION memory from the process address space when it is no longer needed.
     ret = OH_NativeBuffer_Unmap(buffer);
     if (ret != 0) {
         std::cout << "OH_NativeBuffer_Unmap Failed" << std::endl;

en/application-dev/napi/native-image-guidelines.md

@@ -27,6 +27,17 @@ For details about the APIs, see [native_image](../reference/native-apis/_o_h___n
 
 The following steps describe how to use the native APIs provided by **NativeImage** to create an **OH_NativeImage** instance as the consumer and update the data to a OpenGL external texture.
 
+**Adding Dynamic Link Libraries**
+
+Add the following libraries to **CMakeLists.txt**:
+```txt
+libEGL.so
+libGLESv3.so
+libnative_image.so
+libnative_window.so
+libnative_buffer.so
+```
+
 **Header File**
 ```c++
 #include <EGL/egl.h>
@@ -159,6 +170,7 @@ The following steps describe how to use the native APIs provided by **NativeImag
 
 4. Write the produced content to a **NativeWindowBuffer** instance.
     1. Obtain a NativeWindowBuffer instance from the NativeWindow instance.
+    
        ```c++
        OHNativeWindowBuffer* buffer = nullptr;
        int fenceFd;
@@ -171,7 +183,9 @@ The following steps describe how to use the native APIs provided by **NativeImag
        int32_t height = 0x100;
        ret = OH_NativeWindow_NativeWindowHandleOpt(nativeWindow, code, width, height);
        ```
-    3. Write the produced content to the **NativeWindowBuffer** instance.
+    
+    2. Write the produced content to the **NativeWindowBuffer** instance.
+    
        ```c++
        static uint32_t value = 0x00;
        value++;
@@ -182,14 +196,18 @@ The following steps describe how to use the native APIs provided by **NativeImag
            }
        }
        ```
-    4. Flush the **NativeWindowBuffer** to the **NativeWindow**.
+    
+    3. Flush the **NativeWindowBuffer** to the **NativeWindow**.
+    
        ```c++
        // Set the refresh region. If Rect in Region is a null pointer or rectNumber is 0, all contents in the NativeWindowBuffer are changed.
        Region region{nullptr, 0};
        // Flush the buffer to the consumer through OH_NativeWindow_NativeWindowFlushBuffer, for example, by displaying it on the screen.
        OH_NativeWindow_NativeWindowFlushBuffer(nativeWindow, buffer, fenceFd, region);
    ```
-    5. Destroy the **NativeWindow** instance when it is no longer needed.
+    
+    4. Destroy the **NativeWindow** instance when it is no longer needed.
+    
        ```c++
        OH_NativeWindow_DestroyNativeWindow(nativeWindow);
        ```

en/application-dev/napi/native-vsync-guidelines.md

@@ -6,11 +6,11 @@ The **NativeVSync** module is used to obtain virtual synchronization (VSync) sig
 
 ## Available APIs
 
-| API| Description:|
+| API| Description| 
 | -------- | -------- |
 | OH_NativeVSync_Create (const char \*name, unsigned int length) | Creates an **OH_NativeVSync** instance. A new **OH_NativeVSync** instance is created each time this function is called.| 
 | OH_NativeVSync_Destroy (OH_NativeVSync \*nativeVsync) | Destroys an **OH_NativeVSync** instance.| 
-| OH_NativeVSync_FrameCallback (long long timestamp, void \*data) | Sets a callback function. **timestamp** indicates the timestamp, and **data** indicates the input parameter of the callback function. |
+| OH_NativeVSync_FrameCallback (long long timestamp, void \*data) | Sets a callback function. **timestamp** indicates the timestamp, and **data** indicates the input parameter of the callback function.| 
 | OH_NativeVSync_RequestFrame (OH_NativeVSync \*nativeVsync, OH_NativeVSync_FrameCallback callback, void \*data) | Requests the next VSync signal. When the signal arrives, a callback function is invoked.| 
 
 For details about the APIs, see [native_vsync](../reference/native-apis/_native_vsync.md).
@@ -19,6 +19,13 @@ For details about the APIs, see [native_vsync](../reference/native-apis/_native_
 
 The following steps describe how to use the native APIs provided by **NativeVSync** to create and destroy an **OH_NativeVSync** instance and set the VSync callback function.
 
+**Adding Dynamic Link Libraries**
+
+Add the following library to **CMakeLists.txt**:
+```txt
+libnative_vsync.so
+```
+
 **Header File**
 ```c++
 #include <native_vsync/native_vsync.h>

en/application-dev/napi/native-window-guidelines.md

@@ -159,5 +159,3 @@ libnative_window.so
         // munmap failed
     }
     ```
-
- <!--no_check--> 
\ No newline at end of file

en/application-dev/napi/vulkan-guidelines.md

@@ -18,6 +18,15 @@ For details about the APIs, see [Vulkan](../reference/native-lib/third_party_vul
 
 The following steps illustrate how to create a **VkSurfaceKHR** instance.
 
+**Adding Dynamic Link Libraries**
+
+Add the following libraries to **CMakeLists.txt**:
+```txt
+libace_ndk.z.so
+libnative_window.so
+libvulkan.so
+```
+
 **Header File**
 ```c++
 #include <ace/xcomponent/native_interface_xcomponent.h>

en/application-dev/quick-start/introduction-to-arkts.md

@@ -48,12 +48,17 @@ applications in ArkTS.
 
 ## Declarations
 
-Declarations in ArkTS introduce variables, constants, functions and types.
+Declarations in ArkTS introduce:
+
+- variables,
+- constants,
+- functions, and
+- types.
 
 ### Variable Declaration
 
-Declaration started with keyword `let` introduces a variable which can have different values
-during program execution.
+A declaration starting with the keyword `let` introduces a variable which
+can have different values during program execution.
 
 ```typescript
 let hi: string = "hello"
@@ -62,18 +67,19 @@ hi = "hello, world"
 
 ### Constant Declaration
 
-Declaration started with keyword `const` introduces a read-only constant that can be assigned only once.
+A declaration starting with the keyword `const` introduces a read-only
+constant that can be assigned only once.
 
 ```typescript
 const hello: string = "hello"
 ```
 
-Assigning a new value to a constant is a compile-time error.
+A compile-time error occurs if a new value is assigned to a constant.
 
 ### Automatic Type Inference
 
 As ArkTS is a statically typed language, the types of all entities, like
-variables and constants have to be known at compile time.
+variables and constants, have to be known at compile time.
 
 However, developers do not need to explicitly specify the type of a declared
 entity if a variable or a constant declaration contains an initial value.
@@ -90,8 +96,8 @@ let hi2 = "hello, world"
 
 ## Types
 
-`Class`, `interface`, `function`, `enum`, `union` types and type `aliases` are
-described in the corresponding sections.
+`Class`, `interface`, `function`, `enum`, `union` types, and type
+`aliases` are described in the corresponding sections.
 
 ### Numeric Types
 
@@ -104,9 +110,9 @@ with the decimal base.
 Integer literals include the following:
 
 * decimal integers that consist of a sequence of digits. For example: `0`, `117`, `-345`;
-* hexadecimal integers that start with 0x (or 0X) and can contain digits (0-9) and letters a-f or A-F. For example: `0x1123`, `0x00111`, `-0xF1A7`;
+* hexadecimal integers that start with 0x (or 0X), and can contain digits (0-9) and letters a-f or A-F. For example: `0x1123`, `0x00111`, `-0xF1A7`;
 * octal integers that start with 0o (or 0O) and can only contain digits (0-7). For example: `0o777`;
-* binary integers that start with 0b (or 0B) and can only contain the digits 0 and 1. For example: `0b11`, `0b0011`, `-0b11`.
+* binary integers that start with 0b (or 0B), and can only contain the digits 0 and 1. For example: `0b11`, `0b0011`, `-0b11`.
 
 A floating-point literal includes the following:
 
@@ -150,13 +156,12 @@ if (isDone) {
 
 ### `String`
 
-A `string` is a sequence of characters; some characters can be set using
-escape-sequences.
+A `string` is a sequence of characters; some characters can be set by using
+escape sequences.
 
-A `string` literal consists of zero or more characters
-enclosed between single (’) or
-double quotes (“). The special form of a string literals are template literals
-enclosed in backtick quotes (\`).
+A `string` literal consists of zero or more characters enclosed in single
+(’) or double quotes (“). The special form of string literals are template
+literals enclosed in backtick quotes (\`).
 
 ```typescript
 let s1 = "Hello, world!\n"
@@ -168,9 +173,8 @@ let s3 = `The result is ${a}`
 ### `Void` Type
 
 The `void` type is used to specify that a function does not return a value.
-This type has the only one value,
-which is also `void`. As `void` is reference type, it can be used as type
-argument for generic types.
+This type has the only one value which is also `void`. As `void` is
+a reference type, it can be used as type argument for generic types.
 
 ```typescript
 class Class<T> {
@@ -181,19 +185,18 @@ let instance: Class <void>
 
 ### `Object` Type
 
-An `Object` class type is a base type for all reference types. Any value, including
-values of primitive types (they will be automatically boxed), can be directly assigned
-to variables of type `Object`.
+An `Object` class type is a base type for all reference types. Any value,
+including values of primitive types (they will be automatically boxed), can
+be directly assigned to variables of the type `Object`.
 
 ### `Array` Type
 
 An `array` is an object comprised of elements of data types assignable to
 the element type specified in the array declaration.
-A value of an `array` is set using *array composite literal*, that is a list
-of zero or more expressions
-enclosed in square brackets ([]). Each expression represents an element of the
-`array`. The length of the `array` is set by the number of expressions. Index of
-the first array element is 0.
+A value of an `array` is set by using *array composite literal*, that is a
+list of zero or more expressions enclosed in square brackets ([]). Each
+expression represents an element of the `array`. The length of the `array`
+is set by the number of expressions. Index of the first array element is 0.
 
 The following example creates the `array` with three elements:
 
@@ -205,15 +208,16 @@ let names: string[] = ["Alice", "Bob", "Carol"]
 
 An `enum` type is a value type with a defined set of named values called
 enum constants.
-To be used, an `enum` constant must be prefixed with an enum `type` name.
+In order to be used, an `enum` constant must be prefixed with an enum
+`type` name.
 
 ```typescript
 enum Color { Red, Green, Blue }
 let c: Color = Color.Red
 ```
 
-A constant expression can be
-used to explicitly set the value of an enum constant.
+A constant expression can be used to explicitly set the value of an `enum`
+constant.
 
 ```typescript
 enum Color { White = 0xFF, Grey = 0x7F, Black = 0x00 }
@@ -222,8 +226,9 @@ let c: Color = Color.Black
 
 ### `Union` Type
 
-An `union` type is a reference type which is created as a combination of other types. Values of the union types
-can be valid values of all types union was created from.
+A `union` type is a reference type which is created as a combination
+of other types. Values of union types can be valid values of all types
+a union was created from.
 
 ```typescript
 class Cat {
@@ -244,7 +249,8 @@ animal = 42
 // One may assign the variable of the union type with any valid value
 ```
 
-There are different mechanisms how to get a value of the particular type from the union.
+There are different mechanisms to get a value of a particular type from a union.
+
 For example
 
 ```typescript
@@ -267,8 +273,8 @@ animal.sleep () // Any animal can sleep
 
 ### Type `Aliases`
 
-Type `aliases` provide names for anonymous types (array, function, object literal or union
-types) or alternative names for existing types.
+Type `aliases` provide names for anonymous types (array, function, object
+literal or union types) or alternative names for existing types.
 
 ```typescript
 type Matrix = number[][]
@@ -284,7 +290,7 @@ type NullableObject = Object | null
 Simple assignment operator ‘=’ is used as in “x = y”.
 
 Compound assignment operators combine an assignment with an operator, where
-`x op = y` equals to `x = x op y`.
+`x op = y` equals `x = x op y`.
 
 Compound assignment operators are as follows: `+=`, `-=`, `*=`, `/=`,
 `%=`, `<<=`, `>>=`, `>>>=`, `&=`, `|=`, `^=`.
@@ -299,10 +305,9 @@ Compound assignment operators are as follows: `+=`, `-=`, `*=`, `/=`,
 | `>=`       | returns true if the left operand is greater than or equal to the right |
 | `<`        | returns true if the left operand is less then the right                |
 | `<=`       | returns true if the left operand is less than or equal to the right    |
-
 ### Arithmetic Operators
 
-Unary operators are `-`, `+`, `--`, `++`.
+Unary operators are `-`, `+`, `--` and `++`.
 
 Binary operators are as follows:
 
@@ -313,7 +318,6 @@ Binary operators are as follows:
 | `*`        | multiplication           |
 | `/`        | division                 |
 | `%`        | remainder after division |
-
 ### Bitwise Operators
 
 | Operator   | Description                                                                                                     |
@@ -325,7 +329,6 @@ Binary operators are as follows:
 | `a << b`   | Shift left: shifts the binary representation of *a* to the left by *b* bits.                                    |
 | `a >> b`   | Arithmetic right shift: shifts the binary representation of *a* to the right by *b* bits with sign-extension.   |
 | `a >>> b`  | Logical right shift: shifts the binary representation of *a* to the right by *b* bits with zero-extension.      |
-
 ### Logical Operators
 
 | Operator   | Description   |
@@ -333,16 +336,15 @@ Binary operators are as follows:
 | `a && b`   | logical AND   |
 | `a \|\| b`   | logical OR    |
 | `! a`      | logical NOT   |
-
 ## Control Flow
 
 ### `If` Statements
 
-Use `if` statement to execute a sequence of statements when a logical
-condition is true, or another set of statements (if provided) otherwise.
-`else` part may contain more `if` statements as well.
+An `if` statement is used to execute a sequence of statements when a logical
+condition is `true`, or another set of statements (if provided) otherwise.
+The `else` part can also contain more `if` statements.
 
-The `if` statement looks as follows:
+An `if` statement looks as follows:
 
 ```typescript
 if (condition1) {
@@ -354,7 +356,7 @@ if (condition1) {
 }
 ```
 
-All conditional expressions should be of the type `boolean` or other types
+All conditional expressions must be of the type `boolean` or other types
 (`string`, `number`, etc.). For types other than `boolean`, implicit
 conversion rules apply:
 
@@ -372,10 +374,10 @@ if (s2.length != 0) {
 
 ### `Switch` Statements
 
-Use `switch` statement to execute a sequence of statements that match the
-value of the switch expression.
+A `switch` statement is used to execute a sequence of statements that match
+the value of a switch expression.
 
-The `switch` statement looks as follows:
+A `switch` statement looks as follows:
 
 ```typescript
 switch (expression) {
@@ -396,7 +398,7 @@ default:
 ```
 
 The `switch` expression type must be of `number`, `enum` or `string`
-type.
+types.
 
 Each label must be either a constant expression or the name of an enum constant.
 
@@ -409,14 +411,15 @@ default statements are executed.
 An optional `break` statement allows to break out of the `switch` and
 continue executing the statement that follows the `switch`.
 
-If there is no break, then the next statements in the `switch` is executed.
+If there is no `break`, then the next statements in the `switch` is
+executed.
 
 ### Conditional Expressions
 
-The conditional expression `?` : uses the `boolean` value of the first
+The conditional expression `? :` uses the `boolean` value of the first
 expression to decide which of two other expressions to evaluate.
 
-It looks as follows:
+A conditional expression looks as follows:
 
 ```typescript
 condition ? expression1 : expression2
@@ -435,8 +438,10 @@ let message = isValid ? 'Valid' : 'Failed'
 
 ### `For` Statements
 
-A `for` statement is executed repeatedly until the specified loop exit condition
-is `false`. A `for` statement looks as follows:
+A `for` statement is executed repeatedly until the specified loop exit
+condition is `false`.
+
+A `for` statement looks as follows:
 
 ```typescript
 for ([init]; [condition]; [update]) {
@@ -446,10 +451,15 @@ for ([init]; [condition]; [update]) {
 
 When a `for` statement is executed, the following process takes place:
 
-1. An `init` expression is executed, if any. This expression usually initializes one or more loop counters.
-2. The condition is evaluated. If the value of condition is `true`, or if the conditional expression is omitted, then the statements in the for body are to be executed. If the value of condition is `false`, the `for` loop terminates.
+1. An `init` expression is executed, if any. This expression usually
+   initializes one or more loop counters.
+2. The condition is evaluated. If the value of condition is `true`, or
+   if the conditional expression is omitted, then the statements in the
+   `for` body are to be executed. If the value of condition is `false`,
+   then the `for` loop terminates.
 3. The statements of the `for` body are executed.
-4. If there is an `update` expression, the `update` expression is executed.
+4. If there is an `update` expression, then the `update` expression
+   is executed.
 5. Go back to step 2.
 
 Example:
@@ -463,8 +473,9 @@ for (let i = 0; i < 10; i += 2) {
 
 ### `For-of` Statements
 
-Use `for-of` statements to iterate over an array or string. A `for-of`
-statement looks as follows:
+`for-of` statements are used to iterate over an array or string.
+
+A `for-of` statement looks as follows:
 
 ```typescript
 for (forVar of expression) {
@@ -480,8 +491,10 @@ for (let ch of "a string object") { /* process ch */ }
 
 ### `While` Statements
 
-A `while` statement has its body statements executed as long as the specified condition
-evaluates to `true`. It looks as follows:
+A `while` statement has its body statements executed as long as the
+specified condition evaluates to `true`.
+
+A `while` statement looks as follows:
 
 ```typescript
 while (condition) {
@@ -504,8 +517,10 @@ while (n < 3) {
 
 ### `Do-while` Statements
 
-The `do-while` statements are executed repetitively until the specified
-condition evaluates to false. It looks as follows:
+`do-while` statements are executed repetitively until a specified
+condition evaluates to false.
+
+A `do-while` statement looks as follows:
 
 ```typescript
 do {
@@ -526,7 +541,7 @@ do {
 
 ### `Break` Statements
 
-Use a `break` statement to terminate any `loop` statement or `switch`.
+A `break` statement is used to terminate any `loop` statement or `switch`.
 
 Example:
 
@@ -558,8 +573,8 @@ label: while (true) {
 
 ### `Continue` Statements
 
-A `continue` statement stops the execution of the current loop iteration and
-passes control to the next iteration.
+A `continue` statement stops the execution of the current loop iteration
+and passes control to the next iteration.
 
 Example:
 
@@ -575,13 +590,13 @@ for (let x = 0; x < 100; x++) {
 
 ### `Throw` and `Try` Statements
 
-A `throw` statement is used to throw an exception or error:
+A `throw` statement is used to throw an exception or an error:
 
 ```typescript
 throw new Error("this error")
 ```
 
-A `try` statement is used to catch and handle an exception or error:
+A `try` statement is used to catch and handle an exception or an error:
 
 ```typescript
 try {
@@ -672,7 +687,7 @@ function hello(name?: string) {
 
 Another form contains an expression that specifies a default value.
 If the corresponding argument to such parameter is omitted in a function call,
-then this parameter has the default value.
+then this parameter’s value is default.
 
 ```typescript
 function multiply(n: number, coeff: number = 2): number {
@@ -701,7 +716,8 @@ sum(1, 2, 3) // returns 6
 
 ## Return Types
 
-If function return type can be inferred from its body content then it can be omitted from the function declaration.
+If function return type can be inferred from its body content, then it can
+be omitted from the function declaration.
 
 ```typescript
 // Explicit return type
@@ -711,7 +727,9 @@ function foo(): string { return "foo" }
 function goo() { return "goo" }
 ```
 
-The return type of a function that does not need to return a value may be explicitly specified as `void` or omitted altogether. No return statement is needed for such functions.
+The return type of a function that does not need to return a value can be
+explicitly specified as `void` or omitted altogether. No return statement
+is needed for such functions.
 
 Both notations below are valid:
 
@@ -722,13 +740,16 @@ function hi2(): void { console.log("hi") }
 
 ## Function Scope
 
-Variables and other entities defined in a function are local to the function and cannot be accessed outside.
+Variables and other entities defined in a function are local to the function
+and cannot be accessed from the outside.
 
-If the name of a variable defined in the function is equal to the name of an entity in the outer scope, then the local definition shadows outer entity.
+If the name of a variable defined in the function is equal to the name of an
+entity in the outer scope, then the local definition shadows the outer entity.
 
 ## Function Calls
 
-Calling a function actually leads to its body execution while arguments of the call are assigned to function parameters.
+Calling a function actually leads to the execution of its body, while
+the arguments of the call are assigned to the function parameters.
 
 If the function is defined as follows:
 
@@ -770,9 +791,11 @@ let sum = (x: number, y: number): number => {
 }
 ```
 
-An arrow function return type may be omitted; in this case it is inferred from the function body.
+An arrow function return type can be omitted; in such case, it is inferred
+from the function body.
 
-An expression can be specified as an arrow function, making notation shorter, so the following two notations are equivalent:
+An expression can be specified as an arrow function to make the notation
+shorter, i.e., the following two notations are equivalent:
 
 ```typescript
 let sum1 = (x: number, y: number) => { return x + y }
@@ -781,10 +804,12 @@ let sum2 = (x: number, y: number) => x + y
 
 ## Closure
 
-An arrow function is usually defined inside another function. As an inner function, it can access all variables and functions defined in the outer functions.
+An arrow function is usually defined inside another function. As an inner
+function, it can access all variables and functions defined in the outer
+functions.
 
 To capture the context, an inner function forms a closure of its environment.
-The closure allows accessing such inner function outside its own environment.
+The closure allows accessing such an inner function outside its own environment.
 
 ```typescript
 function f(): () => number {
@@ -801,7 +826,10 @@ In the sample above, the arrow function closure captures the `count` variable.
 
 ## Function Overload Signatures
 
-A function can be specified to be called in different ways by writing overload signatures. To do so, several functions headers are written that they have the same name but different signatures, immediately followed by the single implementing function.
+A function can be specified to be called in different ways by writing
+overload signatures. To do so, several functions’ headers that have the
+same name but different signatures are written and immediately followed
+by the single implementation function.
 
 ```typescript
 function foo(): void;            /* 1st signature */
@@ -814,13 +842,15 @@ foo()     // ok, 1st signature is used
 foo("aa") // ok, 2nd signature is used
 ```
 
-It is an error if two overload signatures have identical parameter lists.
+An error occurs if two overload signatures have identical parameter lists.
 
 # Classes
 
-A class declaration introduces a new type and defines its fields, methods and constructors.
+A class declaration introduces a new type and defines its fields, methods
+and constructors.
 
-In the following example, class `Person` is defined, which has fields ‘name’ and ‘surname’, constructor and a method `fullName`:
+In the following example, class `Person` is defined, which has fields
+‘name’ and ‘surname’, constructor, and a method `fullName`:
 
 ```typescript
 class Person {
@@ -836,21 +866,22 @@ class Person {
 }
 ```
 
-After the class is defined, its instances can be created using the keyword `new`:
+After the class is defined, its instances can be created by using
+the keyword `new`:
 
 ```typescript
 let p = new Person("John", "Smith")
 console.log(p.fullName())
 ```
 
-Or an instance can be created using object literals:
+or an instance can be created by using object literals:
 
 ```typescript
 class Point {
     x: number = 0
     y: number = 0
 }
-let p: Point = {42 ,42}
+let p: Point = {x: 42, y: 42}
 ```
 
 ## Fields
@@ -877,7 +908,7 @@ let p1 = new Person("Alice", 25)
 let p2 = new Person("Bob", 28)
 ```
 
-To access an instance field, use an instance of the class:
+An instance of the class is used to access an instance field:
 
 ```typescript
 p1.name
@@ -886,10 +917,11 @@ this.name
 
 ### Static Fields
 
-Use the keyword `static` to declare a field as static. Static fields belong
-to the class itself, and all instances of the class share one static field.
+The keyword `static` is used to declare a field as static. Static fields
+belong to the class itself, and all instances of the class share one static
+field.
 
-To access a static field, use the class name:
+The class name is used to access a static field:
 
 ```typescript
 class Person {
@@ -906,9 +938,11 @@ console.log(Person.numberOfPersons)
 
 ### Getters and Setters
 
-Setters and getters can be used to provide controlled access to object properties.
+Setters and getters can be used to provide controlled access to object
+properties.
 
-In the following example, a setter is used to forbid setting invalid values of the ‘age’ property:
+In the following example, a setter is used to forbid setting invalid
+values of the ‘age’ property:
 
 ```typescript
 class Person {
@@ -928,19 +962,22 @@ console.log (p.age) // 0 will be printed out
 p.age = -42 // Error will be thrown as an attempt to set incorrect age
 ```
 
-A class may define a getter, a setter or both.
+A class can define a getter, a setter or both.
 
 ## Methods
 
 A method is a function that belongs to a class.
 A class can define instance methods, static methods or both.
-A static method belongs to the class itself, and can have access to static fields only.
-While instance method has access to both static (class) fields and instance fields including private ones of its class.
+A static method belongs to the class itself, and can have access to static
+fields only.
+A `while` instance method has access to both static (class) fields and
+instance fields including private ones of its class.
 
 ### Instance Methods
 
-Example below illustrates how instanced methods work.
-The `calculateArea` method calculates the area of a rectangle by multiplying the height by the width:
+The example below illustrates how instanced methods work.
+The `calculateArea` method calculates the area of a rectangle by
+multiplying the height by the width:
 
 ```typescript
 class Rectangle {
@@ -955,20 +992,21 @@ class Rectangle {
 }
 ```
 
-To use an instance method, call it on an instance of the class:
+To use an instance method, it must be called on an instance of the class:
 
 ```typescript
-let r = new Rectangle(10, 10)
+let square = new Rectangle(10, 10)
 console.log(square.calculateArea()) // output: 100
 ```
 
 ### Static Methods
 
-Use the keyword `static` to declare a method as static. Static methods belong to the class itself and have access to static fields only.
+The keyword `static` is used to declare a method as static. Static methods
+belong to the class itself and have access to static fields only.
 A static method defines a common behavior of the class as a whole.
 All instances have access to static methods.
 
-To call a static method, use the class name:
+The class name is used to call a static method:
 
 ```typescript
 class Cl {
@@ -981,7 +1019,8 @@ console.log(Cl.staticMethod())
 
 ### Inheritance
 
-A class can extend another class (called base class) and implement several interfaces using the following syntax:
+A class can extend another class (called base class) and implement several
+interfaces by using the following syntax:
 
 ```typescript
 class [extends BaseClassName] [implements listOfInterfaces] {
@@ -989,9 +1028,12 @@ class [extends BaseClassName] [implements listOfInterfaces] {
 }
 ```
 
-The extended class inherits fields and methods from the base class, but not constructors, and can add its own fields and methods as well as override methods defined by the base class.
+The extended class inherits fields and methods from the base class, but
+not constructors, and can add its own fields and methods as well as override
+methods defined by the base class.
 
-The base class is also called ‘parent class’ or ‘superclass’. The extended class also called ‘derived class’ or ‘subclass’.
+The base class is also called ‘parent class’ or ‘superclass’.
+The extended class also called ‘derived class’ or ‘subclass’.
 
 Example:
 
@@ -1011,7 +1053,9 @@ class Employee extends Person {
 }
 ```
 
-A class containing the `implements` clause must implement all methods defined in all listed interfaces, except the methods defined with default implementation.
+A class containing the `implements` clause must implement all methods
+defined in all listed interfaces, except the methods defined with default
+implementation.
 
 ```typescript
 interface DateInterface {
@@ -1027,9 +1071,11 @@ class MyDate implements DateInterface {
 
 ### Access to Super
 
-The keyword `super` can be used to access instance fields, instance methods and constructors from the super class.
+The keyword `super` can be used to access instance fields, instance methods
+and constructors from the super class.
 
-It is often used to extend basic functionality of subclass with the required behavior taken from the super class:
+It is often used to extend basic functionality of subclass with the required
+behavior taken from the super class:
 
 ```typescript
 class Rectangle {
@@ -1062,9 +1108,11 @@ class FilledRectangle extends Rectangle {
 
 ### Override Methods
 
-A subclass may override implementation of a method defined in its superclass.
-An overridden method may be marked with the keyword `override`, to improve readability.
-An overridden method must have the same types of parameters and same or derived return type as the original method.
+A subclass can override implementation of a method defined in its superclass.
+An overridden method can be marked with the keyword `override` to improve
+readability.
+An overridden method must have the same types of parameters, and same or
+derived return type as the original method.
 
 ```typescript
 class Rectangle {
@@ -1084,7 +1132,10 @@ class Square extends Rectangle {
 
 ### Method Overload Signatures
 
-A method can be specified to can be called in different ways by writing overload signatures. To do so, several method headers are written that have the same name but different signatures, immediately followed by the single implementation method.
+A method can be specified to be called in different ways by writing overload
+signatures. To do so, several method headers that have the same name but
+different signatures are written and immediately followed by the single
+implementation method.
 
 ```typescript
 class C {
@@ -1099,13 +1150,15 @@ c.foo()     // ok, 1st signature is used
 c.foo("aa") // ok, 2nd signature is used
 ```
 
-It is an error if two overload signatures have the same name and identical parameter lists.
+An error occurs if two overload signatures have the same name and identical
+parameter lists.
 
 ## Constructors
 
-A class declaration may contain a constructor that is used to initialize object state.
+A class declaration may contain a constructor that is used to initialize
+object state.
 
-Constructor is defined as follows:
+A constructor is defined as follows:
 
 ```typescript
 constructor ([parameters]) {
@@ -1113,7 +1166,8 @@ constructor ([parameters]) {
 }
 ```
 
-If no constructor is defined, then a default constructor with an empty parameter list is created automatically, for example:
+If no constructor is defined, then a default constructor with an empty
+parameter list is created automatically, for example:
 
 ```typescript
 class Point {
@@ -1123,11 +1177,13 @@ class Point {
 let p = new Point()
 ```
 
-In this case the default constructor fills the instance fields with default values for the field types.
+In this case the default constructor fills the instance fields with
+default values for the field types.
 
 ### Constructors in Derived Class
 
-The first statement of a constructor body can use the keyword `super` to explicitly call a constructor of the direct superclass.
+The first statement of a constructor body can use the keyword `super`
+to explicitly call a constructor of the direct superclass.
 
 ```typescript
 class Rectangle {
@@ -1142,11 +1198,16 @@ class Square extends Rectangle {
 }
 ```
 
-If a constructor body does not begin with such an explicit call of a superclass constructor, then the constructor body implicitly begins with a superclass constructor call `super()`.
+If a constructor body does not begin with such an explicit call of a
+superclass constructor, then the constructor body implicitly begins
+with a superclass constructor call `super()`.
 
 ### Constructor Overload Signatures
 
-A constructor can be specified to can be called in different ways by writing overload signatures. To do so, several constructor headers are written that have the same name but different signatures, immediately followed by the single implementation constructor.
+A constructor can be specified to be called in different ways by writing
+overload signatures. To do so, several constructor headers that have the
+same name but different signatures are written and immediately followed
+by the single implementation constructor.
 
 ```typescript
 class C {
@@ -1160,23 +1221,33 @@ let c1 = new C()      // ok, 1st signature is used
 let c2 = new C("abc") // ok, 2nd signature is used
 ```
 
-It is an error if two overload signatures have the same name and identical parameter lists.
+An error occurs if two overload signatures have the same name and
+identical parameter lists.
 
 ## Visibility Modifiers
 
 Both methods and properties of a class can have visibility modifiers.
 
-There are several visibility modifiers: `private`, `protected`,
-`public`, and `internal`. The default visibility is `public`.
-`internal` allows to limit visibility within the current package.
+There are several visibility modifiers:
+
+- `private`,
+- `protected`,
+- `public`, and
+- `internal`.
+
+The default visibility is `public`.
+The modifier `internal` allows to limit visibility within
+the current package.
 
 ### Public Visibility
 
-The `public` members (fields, methods, constructors) of a class are visible in any part of the program, where their class is visible.
+The `public` members (fields, methods, constructors) of a class are
+visible in any part of the program, where their class is visible.
 
 ### Private Visibility
 
-A `private` member cannot be accessed outside the class in which it is declared, for example:
+A `private` member cannot be accessed outside the class it is declared in,
+for example:
 
 ```typescript
 class C {
@@ -1193,8 +1264,8 @@ c.y = "b" // compile-time error: 'y' is not visible
 
 ### Protected Visibility
 
-The `protected` modifier acts much like the `private` modifier, but
-`protected` members are also accessible in derived classes, for example:
+The modifier `protected` acts much like the modifier `private`, but
+the `protected` members are also accessible in derived classes, for example:
 
 ```typescript
 class Base {
@@ -1211,9 +1282,12 @@ class Derived extends Base {
 
 ## Object Literals
 
-An object literal is an expression that can be used to create a class instance and provide some initial values. It can be used instead of `new` expression as it is more convenient in some cases.
+An object literal is an expression that can be used to create a class instance
+and provide some initial values. It can be used instead of the expression
+`new` as it is more convenient in some cases.
 
-A class composite is written as a comma-separated list of name-value pairs enclosed in ‘{’ and ‘}’.
+A class composite is written as a comma-separated list of name-value pairs
+enclosed in ‘{’ and ‘}’.
 
 ```typescript
 class C {
@@ -1224,7 +1298,9 @@ class C {
 let c: C = {n: 42, s: "foo"}
 ```
 
-Due to static typing of the ArkTS the object literals can be used in context where the class or interface type of the object literal can be inferred as in the example above. Other valid cases:
+Due to the static typing of the ArkTS, object literals can be used in a
+context where the class or interface type of the object literal can be
+inferred as in the example above. Other valid cases are illustrated below:
 
 ```typescript
 class C {
@@ -1244,7 +1320,7 @@ function bar(): C {
 }
 ```
 
-Type of an array element or a type of a class field also can be used:
+The type of an array element or of a class field can also be used:
 
 ```typescript
 class C {
@@ -1254,10 +1330,12 @@ class C {
 let cc: C[] = [{n: 1, s: "a"}, {n: 2, s: "b"}]
 ```
 
-### Object Literals of the Record Type
+### Object Literals of Record Type
+
+The generic Record<K, V> type is used to map the properties of a type
+(Key type) to another type (Value type).
 
-The generic Record<K, V> type is used to map the properties of a type (Key type) to another type (Value type).
-A special form of an object literal is used to initialize the value of such type:
+A special form of object literal is used to initialize the value of such type:
 
 ```typescript
 let map: Record<string, number> = {
@@ -1283,9 +1361,11 @@ let map: Record<string, PersonInfo> = {
 
 # Interfaces
 
-An interface declaration introduces a new type. Interfaces are a common way of defining contracts between various part of codes.
+An interface declaration introduces a new type. Interfaces are a common way
+of defining contracts between various part of codes.
 
-Interfaces are used to write polymorphic code, which can be applied to any class instances that implement a particular interface.
+Interfaces are used to write polymorphic code, which can be applied to any
+class instances that implement a particular interface.
 
 An interface usually contains properties and method headers.
 
@@ -1326,9 +1406,11 @@ class Rectangle implements Area {
 
 ## Interface Properties
 
-An interface property can be in a form of field, getter, setter or both getter and setter.
+An interface property can be in a form of field, getter, setter, or both
+getter and setter.
 
-A property field is just a shortcut notation of a getter/setter pair, and the following notations are equal:
+A property field is just a shortcut notation of a getter/setter pair, and
+the following notations are equal:
 
 ```typescript
 interface Style {
@@ -1381,28 +1463,31 @@ interface ExtendedStyle extends Style {
 }
 ```
 
-An extended interface contains all properties and methods of the interface it extends and may also add its own properties and methods.
+An extended interface contains all properties and methods of the
+interface it extends, and can also add its own properties and methods.
 
 ## Interface Visibility Modifiers
 
 Properties and methods are `public`.
 
-Only methods with default implementation may be defined as `private`.
+Only methods with default implementation can be defined as `private`.
 
 # Generic Types and Functions
 
-Generic types and functions allow creating the code capable to work over a variety of types rather than a single one.
+Generic types and functions allow creating the code capable to work over a
+variety of types rather than a single type.
 
 ## Generic Classes and Interfaces
 
-A class and an interface can be defined as generics, adding parameters to the type definition, like the type parameter `Element` in the following example:
+A class and an interface can be defined as generics, adding parameters to the
+type definition, like the type parameter `Element` in the following example:
 
 ```typescript
 class Stack<Element> {
     public pop(): Element {
         // ...
     }
-    public push(e: Element) {
+    public push(e: Element): void {
         // ...
     }
 }
@@ -1415,7 +1500,8 @@ let s = new Stack<string>
 s.push("hello")
 ```
 
-Compiler ensures type safety while working with generic types and functions. See below
+Compiler ensures type safety while working with generic types and functions.
+See below:
 
 ```typescript
 let s = new Stack<string>
@@ -1424,7 +1510,9 @@ s.push(55) // That will be a compile-time error
 
 ## Generic Constraints
 
-Type parameters of generic types can be bounded. For example, the `Key` type parameter in the `HashMap<Key, Value>` container must have a hash method, i.e., it should be hashable.
+Type parameters of generic types can be bounded. For example, the `Key`
+type parameter in the `HashMap<Key, Value>` container must have a hash
+method, i.e., it must be hashable.
 
 ```typescript
 interface Hashable {
@@ -1438,11 +1526,13 @@ class HasMap<Key extends Hashable, Value> {
 }
 ```
 
-In the above example, the `Key` type extends `Hashable`, and all methods of `Hashable` interface can be called for keys.
+In the above example, the `Key` type extends `Hashable`, and all methods
+of `Hashable` interface can be called for keys.
 
 ## Generic Functions
 
-Use a generic function to create a more universal code. Consider a function that returns the last element of the array:
+Use a generic function to create a more universal code. Consider a function
+that returns the last element of the array:
 
 ```typescript
 function last(x: number[]): number {
@@ -1451,7 +1541,8 @@ function last(x: number[]): number {
 console.log(last([1, 2, 3])) // output: 3
 ```
 
-If the same function needs to be defined for any array, define it as generic with a type parameter:
+If the same function needs to be defined for any array, then define it as
+a generic with a type parameter:
 
 ```typescript
 function last<T>(x: T[]): T {
@@ -1461,7 +1552,7 @@ function last<T>(x: T[]): T {
 
 Now, the function can be used with any array.
 
-In a function call, type argument may be set explicitly or implicitly:
+In a function call, type argument can be set explicitly or implicitly:
 
 ```typescript
 // Explicit type argument
@@ -1476,7 +1567,8 @@ console.log(last([1, 2, 3]))
 ## Generic Defaults
 
 Type parameters of generic types can have defaults.
-It allows not specifying the actual type arguments but using just the generic type name.
+It allows using just the generic type name instead of specifying the actual
+type arguments.
 Example below illustrates this for both classes and functions.
 
 ```typescript
@@ -1497,9 +1589,10 @@ foo<number>()
 
 # Null Safety
 
-All types in ArkTS by default are non-nullable, so the value of a type cannot be null.
+All types in ArkTS by default are non-nullable, so the value of a type
+cannot be null.
 It is similar to TypeScript behavior in strict null checking mode
-(`strictNullChecks`), but the rules are stricter, and the there is no `undefined` type in ArkTS.
+(`strictNullChecks`), but the rules are stricter.
 
 In the example below, all lines cause a compile-time error:
 
@@ -1522,7 +1615,8 @@ if (x != null) { /* do something */ }
 
 A postfix operator `!` can be used to assert that its operand is non-null.
 
-If applied to a null value, the operator throws an error. Otherwise, the type of the value is changed from `T | null` to `T`:
+If applied to a null value, the operator throws an error. Otherwise, the
+type of the value is changed from `T | null` to `T`:
 
 ```typescript
 let x: number | null = 1
@@ -1533,12 +1627,15 @@ y = x! + 1 // ok
 
 ## Null-Coalescing Operator
 
-The null-coalescing binary operator `??` checks whether the evaluation of the left-hand-side expression is equal to null.
-If it is, then the result of the expression is the right-hand-side expression; otherwise, it is the left-hand-side expression.
+The null-coalescing binary operator `??` checks whether the evaluation
+of the left-hand-side expression is equal to null.
+If it is, then the result of the expression is the right-hand-side expression;
+otherwise, it is the left-hand-side expression.
 
 In other words, `a ?? b` equals the ternary operator `a != null ? a : b`.
 
-In the following example, the method `getNick` returns a nickname if it is set; otherwise, empty string is returned:
+In the following example, the method `getNick` returns a nickname if it is
+set; otherwise, an empty string is returned:
 
 ```typescript
 class Person {
@@ -1552,46 +1649,72 @@ class Person {
 
 ## Optional Chaining
 
-Optional chaining operator `?.` allows writing code where the evaluation stops of an expression that is partially evaluated to `null`.
+Optional chaining operator `?.` allows writing code where the evaluation
+stops at an expression that is partially evaluated to `null` or `undefined`.
 
 ```typescript
 class Person {
-    // ...
-    spouse: Person | null = null
-    nick: string | null = null
-    getSpouseNick(): string | null {
+    nick    : string | null = null
+    spouse ?: Person
+
+    setSpouse(spouse: Person) : void {
+        this.spouse = spouse
+    }
+
+    getSpouseNick(): string | null | undefined {
         return this.spouse?.nick
     }
+
+    constructor(nick: string) {
+        this.nick = nick
+        this.spouse = undefined
+    }
 }
 ```
 
-**Note**: that the return type of `getSpouseNick` must be `string | null`, as the method may return null.
+**Note**: the return type of `getSpouseNick` must be `string | null | undefined`, as
+the method can return null or undefined.
 
-An optional chain may be of any length and contain any number of `?.`
+An optional chain can be of any length and contain any number of `?.`
 operators.
 
-In the following sample, the output is a person’s spouse nickname if the person has a spouse, and the spouse has a nickname.
+In the following sample, the output is a person’s spouse nickname if that
+person has a spouse, and the spouse has a nickname.
 
-Otherwise, the output is `null`:
+Otherwise, the output is `undefined`:
 
 ```typescript
-let p: Person = ...
-console.log(p?.spouse?.nick)
+class Person {
+    nick    : string | null = null
+    spouse ?: Person
+
+    constructor(nick: string) {
+        this.nick = nick
+        this.spouse = undefined
+    }
+}
+
+let p: Person = new Person("Alice")
+console.log(p.spouse?.nick) // print: undefined
 ```
 
 # Modules
 
 Programs are organized as sets of compilation units or modules.
 
-Each module creates its own scope, i.e., any declarations (variables, functions, classes, etc.) declared in the module are not visible outside that module unless they are explicitly exported.
+Each module creates its own scope, i.e., any declarations (variables,
+functions, classes, etc.) declared in the module are not visible outside
+that module unless they are explicitly exported.
 
-Conversely, a variable, function, class, interface, etc. exported from another module must first be imported to a module.
+Conversely, a variable, function, class, interface, etc. exported from
+another module must first be imported to a module.
 
 ## Export
 
 A top-level declaration can be exported by using the keyword `export`.
 
-A declared name that is not exported is considered private and can be used only in the module where it is declared.
+A declared name that is not exported is considered private and can be used
+only in the module where it is declared.
 
 ```typescript
 export class Point {
@@ -1610,16 +1733,21 @@ export function Distance(p1: Point, p2: Point): number {
 
 ## Import
 
-Import declarations are used to import entities exported from other modules and provide their bindings in the current module. An import declaration consists of two parts:
+Import declarations are used to import entities exported from other modules
+and provide their bindings in the current module. An import declaration
+consists of two parts:
 
 * Import path that determines the module to import from;
-* Import bindings that define the set of usable entities in the imported module and the form of use i.e., qualified or unqualified use.
+* Import bindings that define the set of usable entities in the imported
+  module, and the form of use (i.e., qualified or unqualified use).
 
 Import bindings may have several forms.
 
 Let’s assume a module has the path ‘./utils’ and export entities ‘X’ and ‘Y’.
 
-An import binding of the form `* as A` binds the name ‘A’, and all entities exported from the module defined by the import path can be accessed by using the qualified name `A.name`:
+An import binding of the form `* as A` binds the name ‘A’, and all entities
+exported from the module defined by the import path can be accessed by using
+the qualified name `A.name`:
 
 ```typescript
 import * as Utils from "./utils"
@@ -1627,7 +1755,8 @@ Utils.X // denotes X from Utils
 Utils.Y // denotes Y from Utils
 ```
 
-An import binding of the form `{ ident1, ..., identN }` binds an exported entity with a specified name, which can be used as a simple name:
+An import binding of the form `{ ident1, ..., identN }` binds an exported
+entity with a specified name, which can be used as a simple name:
 
 ```typescript
 import { X, Y } from "./utils"
@@ -1635,7 +1764,8 @@ X // denotes X from Utils
 Y // denotes Y from Utils
 ```
 
-If a list of identifiers contains aliasing of the form `ident as alias`, then entity `ident` is bound under the name `alias`:
+If a list of identifiers contains aliasing of the form `ident as alias`,
+then entity `ident` is bound under the name `alias`:
 
 ```typescript
 import { X as Z, Y } from "./utils"
@@ -1648,12 +1778,17 @@ X // Compile-time error: 'X' is not visible
 
 A module can contain any statements at the module level, except `return` ones.
 
-If a module contains a `main` function (program entry point) then top-level statements of the module are executed immediately before the body of this function.
-Otherwise, they are executed before execution of any other function of the module.
+If a module contains a `main` function (program entry point), then
+top-level statements of the module are executed immediately before
+the body of this function.
+Otherwise, they are executed before execution of any other function
+of the module.
 
 ## Program Entry Point
 
-An entry point of a program (application) is the top-level `main` function. The `main` function should have either an empty parameter list or a single parameter of `string[]` type.
+An entry point of a program (application) is the top-level `main` function.
+The `main` function must have either an empty parameter list or a single
+parameter of `string[]` type.
 
 ```typescript
 function main() {
@@ -1664,16 +1799,16 @@ function main() {
 # Support for ArkUI
 
 This section demonstrates mechanisms that ArkTS provides for
-creating graphical user interface (GUI) programs. The section is based on the
-ArkUI declarative framework. ArkUI provides a set of extensions of the standard
-TypeScript to declaratively describe the GUI of the applications and the interaction
-between the GUI components.
+creating graphical user interface (GUI) programs. The section is based on
+the ArkUI declarative framework. ArkUI provides a set of extensions of
+the standard TypeScript to declaratively describe the GUI of the applications
+and the interaction between the GUI components.
 
 ## ArkUI Example
 
 The following example provides a complete ArkUI-based application as an
-illustration of GUI programming capabilities. For more details about ArkUI
-features, please refer to the ArkUI
+illustration of GUI programming capabilities. For more details of the
+ArkUI features, refer to the ArkUI
 [tutorial](arkts-get-started.md).
 
 ```typescript

en/application-dev/quick-start/start-with-ets-stage.md

@@ -5,7 +5,7 @@
 > 
 > To use ArkTS, your DevEco Studio must be V3.0.0.900 Beta3 or later.
 > 
->  In this document, DevEco Studio 4.0 Beta1 is used. You can download it [here](../../release-notes/OpenHarmony-v4.0-beta1.md#version-mapping).
+> In this document, DevEco Studio 4.0 Beta2 is used. You can download it [here](../../release-notes/OpenHarmony-v4.0-beta2.md#version-mapping).
 
 ## Creating an ArkTS Project
 
@@ -21,7 +21,9 @@ The following describes how to create the OpenHarmony projects of API 10 and API
 
    ![createProject](figures/createProject.png)
 
-3. On the project configuration page, set **Compile SDK** to **3.1.0(API 9** and retain the default values for other parameters.
+3. On the project configuration page, set **Compile SDK** to **3.1.0(API 9)** and retain the default values for other parameters.
+
+   The **Node** parameter sets the Node.js version to use for the project. You can use an existing version or download a new one.
 
    ![chooseStageModel](figures/chooseStageModel.png)
 
@@ -43,12 +45,13 @@ The following describes how to create the OpenHarmony projects of API 10 and API
 
    ![targetSdkVersion](figures/targetSdkVersion.png)
 
-7. Delete the **runtimeOS** configuration from the **targets** field in all module-level **build-profile.json5** files.
+7. Delete the **runtimeOS** configuration from the **targets** field in the module-level **build-profile.json5** files.
 
    ![deleteRuntimeOS](figures/deleteRuntimeOS.png)
 
 8. Click **Sync Now** and wait until the synchronization is complete. A project of API version 10 is now created.
 
+
 ### Creating a Project of API Version 9
 
 1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar.
@@ -57,7 +60,9 @@ The following describes how to create the OpenHarmony projects of API 10 and API
 
    ![createProject](figures/createProject.png)
 
-3. On the project configuration page, set **Compile SDK** to **3.1.0(API 9** and retain the default values for other parameters.
+3. On the project configuration page, set **Compile SDK** to **3.1.0(API 9)** and retain the default values for other parameters.
+
+   The **Node** parameter sets the Node.js version to use for the project. You can use an existing version or download a new one.
 
    ![chooseStageModel](figures/chooseStageModel.png)
 
@@ -78,11 +83,11 @@ The following describes how to create the OpenHarmony projects of API 10 and API
 
 ## ArkTS Project Directory Structure (Stage Model, API Version 10)
 
-![en-us_image_0000001364054489](figures/en-us_image_0000001364054489.png)
+![project](figures/project.png)
 
 - **AppScope > app.json5**: application-level configuration information.
 
-- **entry**: OpenHarmony project module, which can be built into an OpenHarmony Ability Package ([HAP](../../glossary.md#hap)).
+- **entry**: OpenHarmony project module, which can be built into an ability package (HAP).
   - **src > main > ets**: a collection of ArkTS source code.
   
   - **src > main > ets > entryability**: entry to your application/service.
@@ -99,17 +104,18 @@ The following describes how to create the OpenHarmony projects of API 10 and API
 
 - **oh_modules**: third-party library dependency information. For details about how to adapt a historical npm project to ohpm, see [Manually Migrating Historical Projects](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/project_overview-0000001053822398-V3#section108143331212).
 
-- **build-profile.json5**: application-level configuration options, including **signingConfigs** and **products**. The **runtimeOS** field in **products** indicates the runtime OS. Its default value is **HarmonyOS**. If you are developing an OpenHarmony application, change the value to **OpenHarmony**.
+- **build-profile.json5**: application-level configuration information, including the **signingConfigs** and **products** configuration. The **runtimeOS** field in **products** indicates the runtime OS. Its default value is **HarmonyOS**. If you are developing an OpenHarmony application, change the value to **OpenHarmony**.
 
 - **hvigorfile.ts**: application-level build script.
 
+
 ## ArkTS Project Directory Structure (Stage Model, API Version 9)
 
-![en-us_image_0000001364054489](figures/en-us_image_0000001364054489.png)
+![project](figures/project.png)
 
 - **AppScope > app.json5**: application-level configuration information.
 
-- **entry**: OpenHarmony project module, which can be built into an OpenHarmony Ability Package ([HAP](../../glossary.md#hap)).
+- **entry**: OpenHarmony project module, which can be built into an ability package (HAP).
   - **src > main > ets**: a collection of ArkTS source code.
   
   - **src > main > ets > entryability**: entry to your application/service.
@@ -267,7 +273,7 @@ You can implement page redirection through the [page router](../reference/apis/j
 
 1. Implement redirection from the first page to the second page.
 
-   In the **index.ets** file of the first page, bind the **onClick** event to the **Next** button so that clicking the button redirects the user to the second page. The sample code in the **Index.ets** file is shown below:
+   In the **Index.ets** file of the first page, bind the **onClick** event to the **Next** button so that clicking the button redirects the user to the second page. The sample code in the **Index.ets** file is shown below:
    
    ```ts
    // Index.ets

en/application-dev/quick-start/typescript-to-arkts-migration-guide.md

@@ -12,22 +12,24 @@ categories:
 2. **Partially supported features**: some minor code refactoring is needed.
    Example: The keyword `let` must be used in place of `var` to declare
    variables. Please note that your code will still remain a valid TypeScript code
-   after rewriting according to our recipes.
+   after rewriting by our recipes.
 3. **Unsupported features**: a greater code refactoring effort can be required.
    Example: The type `any` is unsupported, and you are to introduce explicit
    typing to your code everywhere `any` is used.
 
+PageBreak
+
 # How to Use The Cookbook
 
 The main goal of this cookbook is to provide recipes for all partially
 supported features and explicitly list all unsupported features.
 
-The document is built on the feature-by-feature basis, and if you do not find
-some feature, you can safely consider it **supported**. Otherwise, a recipe
-will give you a suggestion on how to rewrite your code and work around an
-unsupported case.
+The document is built on the feature-by-feature basis, and if you do not
+find some feature, then you can safely consider it **supported**. Otherwise,
+a recipe will give you a suggestion on how to rewrite your code and work
+around an unsupported case.
 
-## Recipe explained
+## Recipe Explained
 
 The original TypeScript code containing the keyword `var`:
 
@@ -38,7 +40,7 @@ function addTen(x: number): number {
 }
 ```
 
-This code must be rewritten as follows:
+must be rewritten as follows:
 
 ```typescript
 // Important! This is still valid TypeScript.
@@ -50,40 +52,40 @@ function addTen(x: number): number {
 
 ## Status of Unsupported Features
 
-Currently unsupported are mainly the features which
+Currently unsupported are mainly the features which:
 
 - relate to dynamic typing that degrades runtime performance, or
 - require extra support in the compiler, thus degrading project build time.
 
 However, the ArkTS team reserves the right to reconsider the list and
-**shrink** it in the future releases based on the feedback from the developers
-and more real-world data experiments.
+**shrink** it in the future releases based on the feedback from the developers,
+and on more real-world data experiments.
+
+PageBreak
 
 # Recipes Summarized
 
-This documents provides an informal summary of TypeScript features that ArkTS either
-does not support or supports with limitations. For the full list, with more
-detailed code examples and workaround suggestions, please see
-[this section](#recipes).
+This document provides an informal summary of TypeScript features that ArkTS either
+can support with limitations, or cannot support. See [Recipes](#recipes) for the
+full list with more detailed code examples and workaround suggestions.
 
-## Static typing is enforced
+## Static Typing is Enforced
 
-ArkTS was designed with following goals in mind:
+ArkTS was designed with the following goals in mind:
 
-- It should be easy for developers to read and understand ArkTS programs,
-  because the code is read more often than written;
-- ArkTS should execute fast with as little power consumption as possible,
-  which is critical for mobile devices which ArkTS targets.
+- ArkTS programs must be easy for developers to read and understand because
+  the code is read more often than written;
+- ArkTS must execute fast and consume as little power as possible because
+  it is particularly critical on mobile devices which ArkTS targets.
 
-Static typing is one of the most important features of ArkTS, which helps
-achieve both goals. Indeed, if your program is statically typed, i.e. all
-types are known at the compile time, it’s much easier to understand which data
-structures are used in the code. At the same time, since all types are known
-before the program actually runs, code correctness can be verified by the
-compiler, which eliminates many runtime type checks and improves the
-performance.
+One of the most important features of ArkTS that helps achieving both goals
+is static typing. Indeed, if a program is statically typed, i.e. all types
+are known at compile time, then it is much easier to understand what data
+structures are used in the code. That all types are known before the program
+actually runs results in the compiler to verify code correctness, thus
+eliminating many runtime type checks and improving performance.
 
-Therefore, it was decided to prohibit usage of the type `any`.
+Therefore, the usage of the type `any` in ArkTS is prohibited.
 
 ### Example
 
@@ -112,26 +114,27 @@ if (!res.succeeded()) {
 }
 ```
 
-### Rationale and impact
+### Rationale and Impact
 
-Our research and experiments let us conclude that this feature is already
-not welcome in the modern TypeScript. According to our measurements, it is used
-in approximately 1% of TypeScript code bases. Moreover, code linters (e.g., ESLint)
-already include a set of rules that prohibit usage of `any`. Thus, although
-prohibiting `any` requires code refactoring, we consider it a low-effort
-change with the high impact result.
+Our research and experiments let us conclude that `any` is already not welcome
+in TypeScript. According to our measurements, `any` is used in approximately 1% of
+TypeScript codebases. Moreover, today’s code linters (e.g., ESLint) include a set
+of rules that prohibit the usage of `any`.
 
-## Changing object layout in runtime is prohibited
+Prohibiting `any` results in a strong positive impact on performance at the
+cost of low-effort code refactoring.
 
-To achieve maximum performance benefits, ArkTS requires that layout of objects
-does not change during program execution. In other words, it is prohibited to:
+## Changing Object Layout in Runtime Is Prohibited
 
-- add new properties or methods to the objects;
-- delete existing properties or methods from the objects;
+To achieve maximum performance benefits, ArkTS requires the layout of objects
+to not change during program execution. In other words, it is prohibited to:
+
+- add new properties or methods to objects;
+- delete existing properties or methods from objects;
 - assign values of arbitrary types to object properties.
 
-It’s worth noticing that many such operations are already prohibited by the TypeScript
-compiler. However, it still can be “tricked” by e.g. `as any` casts, wchich
+It is noteworthy that many such operations are already prohibited by the TypeScript
+compiler. However, it still can be “tricked”, e.g., by `as any` casts that
 ArkTS does not support (see the detailed example below).
 
 ### Example
@@ -193,29 +196,27 @@ let p6 = new Point(6.0, 6.0)
 console.log("Distance between p5 and p6: " + distance(p5, p6))
 ```
 
-### Rationale and impact
+### Rationale and Impact
 
 Unpredictable changing of object layout contradicts both good readability and
-good performance of the code. Indeed, having class definition at one place and
+good performance of code. Indeed, having class definition at one place and
 modifying actual object layout elsewhere is confusing and error-prone from the
-developer’s point of view. Additionally, it requires extra runtime support,
-which brings undesired execution overhead. Moreover, it contradicts the idea of
-static typing. If we want to make typing as explicit as possible, why would we
-need to add or remove additional properties?
+developer’s point of view. It opposes the idea of static typing (why adding
+or removing additional properties if typing is to be as explicit as possible?)
+and requires extra runtime support that causes undesired execution overhead.
 
-At the same time, according to our observations and experiments, this feature
-is already not welcome in the modern TypeScript. It is used in the marginal number of
-cases in real-world projects and state of the art linters have rules to
-prohibit its usage.
+According to our observations and experiments, this feature is already not
+welcome in TypeScript: it is used in a marginal number of real-world projects,
+and state-of-the-art linters have rules to prohibit its usage.
 
-Thus, we conclude that prohibiting runtime changes to objects’ layout results
-in low-effort refactoring with the high positive impact on performance.
+We conclude that prohibiting runtime changes to object layouts results in a
+strong positive impact on performance at the cost of low-effort refactoring.
 
-## Semantics of operators is restricted
+## Semantics of Operators Is Restricted
 
 To achieve better performance and encourage developers write clearer code,
-ArkTS restricts semantics of some operators. A couple of examples are given
-below, and the full list of restrictions is outlined [here](#recipes).
+ArkTS restricts the semantics of some operators. A couple of examples are
+given below, and the full list of restrictions is outlined in [Recipes](#recipes).
 
 ### Example
 
@@ -229,24 +230,23 @@ let c2 : C = new C()
 console.log(c1 + c2) // Compile-time error
 ```
 
-### Rationale and impact
+### Rationale and Impact
 
-Overloading language operators with extra semantics complicates language
-specification and makes developers remember about all possible corner cases
-and their handling rules. Besides, in certain cases it incurs some runtime
-overhead, which is undesired.
+Loading language operators with extra semantics complicates the language
+specification, and forces developers to remember all possible corner cases with
+appropriate handling rules. Besides, in certain cases it causes some undesired
+runtime overhead.
 
 At the same time, according to our observations and experiments, this feature
-is not popular in the modern TypeScript. It is used in less than 1% of real-world
-code bases. Besides, such cases are very easy to refactor.
+is not popular in TypeScript. It is used in less than 1% of real-world codebases,
+and such cases are easy to refactor.
 
-Thus, although restricting semantics of operators requires changing the code,
-this is a low-effort change which results in a clearer and more performant code.
+Restricting the operator semantics results in a clearer and more performant
+at the cost of low-effort changes in code.
 
-## Structural typing is not supported (yet)
+## Structural Typing Is Not Supported (Yet)
 
-Let’s consider a situation when two unrelated classes `T` and `U` have the
-same public API:
+Assuming that two unrelated classes `T` and `U` have the same public API:
 
 ```typescript
 class T {
@@ -284,31 +284,34 @@ let t : T = new T()
 greeter(t) // Is this allowed?
 ```
 
-Or, in other words, which approach will we take:
+In other words, which approach will we take:
 
 - `T` and `U` are not related by inheritance or any common interface, but
-  since they have the same public API, they are “somewhat equivalent”, so the
-  answer to both questions above is “yes”;
+  they are “somewhat equivalent” since they have the same public API, and so
+  the answer to both questions above is “yes”;
 - `T` and `U` are not related by inheritance or any common interface, and
-  should always be considered as totally different types, so the
-  answer to both questions above is “no”.
-
-Languages that take the first approach are said to support structural typing,
-while languages that take the second approach do not support it. Currently,
-TypeScript supports structural typing, and ArkTS does not.
-
-It is debatable if structural typing helps produce clear and
-understandable code, arguments can be found both for and against it.
-Moreover, structural typing does not harm program performance (at least in some
-cases). Why is it not supported then?
-
-The answer is that support for structural typing is a major feature which needs
-lots of consideration and careful implementation in language specification,
-compiler and runtime. Safe and efficient implementation requires that other
-aspects (static typing, restrictions on changing object layout) are also
-taken into account. That’s why support for this feature is postponed. The team
-will be ready to reconsider based on real-world scenarios and feedback. More
-cases and suggested workarounds can be found in [Recipes](#recipes).
+  always must be considered as totally different types, so that the answer to
+  both questions above is “no”.
+
+The languages that take the first approach are said to support structural
+typing, while the languages that take the second approach do not support it.
+Currently, TypeScript supports structural typing, and ArkTS does not.
+
+It is debatable whether or not structural typing helps to produce code that
+is clearer and more understandable, and both *pro* and *contra* arguments can
+be found. Moreover, structural typing does not harm program performance (at
+least in some cases). Why not support it then?
+
+The answer is that supporting structural typing is a major feature that needs
+a lot of consideration and careful implementation in language specification,
+compiler and runtime. As safe and efficient implementation requires taking
+other aspects (static typing, restrictions on changing object layout) into
+account, the support to this feature is postponed.
+
+The ArkTS team is ready to reconsider based on real-world scenarios and
+feedback. More cases and suggested workarounds can be found in [Recipes](#recipes).
+
+PageBreak
 
 # Recipes
 
@@ -335,9 +338,9 @@ console.log(x[2])
 
 ```typescript
 class X {
-    public name: number
+    public name: number = 0
 }
-let x = {name: 1}
+let x:X = {name: 1}
 console.log(x.name)
 
 let y = [1, 2, 3]
@@ -372,7 +375,7 @@ console.log(z.get(2))
 TypeScript has `Symbol()` API, which can be used among other things to generate
 unique property names at runtime. ArkTS does not support `Symbol()` API
 because its most popular use cases make no sense in the statically typed
-environment. In particular, the object layout is defined at compile time
+environment. In particular, the object layout is defined at compile time,
 and cannot be changed at runtime.
 
 **TypeScript**
@@ -388,7 +391,7 @@ let o = {
 
 ```typescript
 class SomeClass {
-    public someProperty : string
+    public someProperty : string = ""
 }
 let o = new SomeClass()
 ```
@@ -410,15 +413,18 @@ let o = new SomeClass()
 
 **Severity: error**
 
-ArkTS does not private identifiers started with `#` symbol, use `private`
-keyword instead.
+ArkTS does not use private identifiers starting with the symbol `#`. Use
+the keyword  `private` instead.
 
 **TypeScript**
 
 ```typescript
+/*
+ * Such notation for private fields is not supported:
 class C {
     #foo: number = 42
 }
+*/
 ```
 
 **ArkTS**
@@ -458,7 +464,7 @@ type T = number[] // X is not allowed here to avoid name collisions
 
 **Severity: error**
 
-ArkTS does not support `var`, always use `let` instead.
+ArkTS does not support `var`. Use `let` instead.
 
 **TypeScript**
 
@@ -507,59 +513,40 @@ scoped_var = 5
 scoped_let = 5 // Compile-time error
 ```
 
-## Recipe: Use explicit types instead of `any`, `undefined`, `unknown`
+## Recipe: Use explicit types instead of `any`, `unknown`
 
-**Rule `arkts-no-any-undefined-unknown`**
+**Rule `arkts-no-any-unknown`**
 
 **Severity: error**
 
-ArkTS does not support `any`, `undefined`, and `unknown` types.
-Specify types explicitly.
+ArkTS does not support the types `any` and `unknown`. Specify
+types explicitly.
 
 **TypeScript**
 
 ```typescript
-var x
-console.log(x) // undefined
+let value1 : any
+value1 = true
+value1 = 42
 
-var y: any
-console.log(y) // undefined
+let value2 : unknown
+value2 = true
+value2 = 42
 ```
 
 **ArkTS**
 
 ```typescript
-// All variables should have their types specified explicitly:
-let x: Object = {}
-console.log(x) // {}
+let value_b: boolean = true // OR: let value_b = true
+let value_n: number = 42 // OR: let value_n = 42
+let value_o1: Object = true
+let value_o2: Object = 42
 ```
 
 **See also**
 
 * Recipe: Use Object[] instead of tuples
-
-## Recipe: `bigint` is not a builtin type, suffix `n` for numeric literals is not supported
-
-**Rule `arkts-no-n-suffix`**
-
-**Severity: error**
-
-ArkTS supports `bigint` as a part of the standard library, not as a builtin
-type. `n` suffix for numeric literals is not supported, `BigInt` factory
-function can be used to produce values of `bigint` type.
-
-**TypeScript**
-
-```typescript
-let a: bigint = 1n
-```
-
-**ArkTS**
-
-```typescript
-let a = BigInt(1)
-let b: bigint = BigInt(2)
-```
+* Recipe: Strict type checking is enforced
 
 ## Recipe: Use `Object[]` instead of tuples
 
@@ -567,7 +554,7 @@ let b: bigint = BigInt(2)
 
 **Severity: error**
 
-Currently, ArkTS does not support tuples. You can use arrays of `Object`
+Currently, ArkTS does not support tuples. Use arrays of `Object`
 (`Object[]`) to emulate tuples.
 
 **TypeScript**
@@ -679,8 +666,8 @@ function fn(s: string): SomeObject {
 
 **Severity: error**
 
-ArkTS does not allow to have sevaral static block for class initialization,
-combine static blocks statements to the one static block.
+ArkTS does not allow having sevaral static blocks for class initialization.
+Combine static block statements into one static block.
 
 **TypeScript**
 
@@ -716,7 +703,7 @@ class C {
 
 **Severity: error**
 
-ArkTS does not allow indexed signatures, use arrays instead.
+ArkTS does not allow indexed signatures. Use arrays instead.
 
 **TypeScript**
 
@@ -738,7 +725,7 @@ const secondItem = myArray[1]
 
 ```typescript
 class X {
-    public f: string[]
+    public f: string[] = []
 }
 
 let myArray: X = new X()
@@ -751,8 +738,8 @@ const secondItem = myArray.f[1]
 
 **Severity: error**
 
-Currently, ArkTS does not support intersection types. You can use inheritance
-as a work-around.
+Currently, ArkTS does not support intersection types. Use inheritance
+as a workaround.
 
 **TypeScript**
 
@@ -764,7 +751,7 @@ interface Identity {
 
 interface Contact {
     email: string
-    phone: string
+    phoneNumber: string
 }
 
 type Employee = Identity & Contact
@@ -780,15 +767,15 @@ interface Identity {
 
 interface Contact {
     email: string
-    phone: string
+    phoneNumber: string
 }
 
 interface Employee extends Identity,  Contact {}
 ```
 
-## Recipe: Returning `this` type is not supported
+## Recipe: Type notation using `this` is not supported
 
-**Rule `arkts-no-this-as-return-type`**
+**Rule `arkts-no-typing-with-this`**
 
 **Severity: error**
 
@@ -800,6 +787,14 @@ ArkTS does not support the returning `this` type. Use explicit type instead.
 interface ListItem {
     getHead(): this
 }
+
+class C {
+    n: number = 0
+
+    m(c: this) {
+        console.log(c)
+    }
+}
 ```
 
 **ArkTS**
@@ -808,6 +803,14 @@ interface ListItem {
 interface ListItem {
     getHead(): ListItem
 }
+
+class C {
+    n: number = 0
+
+    m(c: C) {
+        console.log(c)
+    }
+}
 ```
 
 ## Recipe: Conditional types are not supported
@@ -817,8 +820,8 @@ interface ListItem {
 **Severity: error**
 
 ArkTS does not support conditional type aliases. Introduce a new type with
-constraints explicitly or rewrite logic with use of `Object`. `infer`
-keyword is not supported.
+constraints explicitly, or rewrite logic using `Object`. The keyword
+`infer` is not supported.
 
 **TypeScript**
 
@@ -842,44 +845,6 @@ type X2<T> = Object
 type YI<Item, T extends Array<Item>> = Item
 ```
 
-## Recipe: Optional parameters are not supported for primitive types
-
-**Rule `arkts-no-opt-params`**
-
-**Severity: error**
-
-ArkTS does not support optional parameters of primitive types.
-You can use default parameter values or reference types. For reference types,
-non-specified optional parameter is set to `null`.
-
-**TypeScript**
-
-```typescript
-// x is an optional parameter:
-function f(x?: number) {
-    console.log(x) // log undefined or number
-}
-
-// x is a required parameter with the default value:
-function g(x: number = 1) {
-    console.log(x)
-}
-```
-
-**ArkTS**
-
-```typescript
-// You can use reference type (will be set to null if missing):
-function f(x?: Number) {
-    console.log(x) // log null or some number
-}
-
-// You can use a required parameter with the default value:
-function g(x: number = 1) {
-    console.log(x)
-}
-```
-
 ## Recipe: Declaring fields in `constructor` is not supported
 
 **Rule `arkts-no-ctor-prop-decls`**
@@ -887,7 +852,7 @@ function g(x: number = 1) {
 **Severity: error**
 
 ArkTS does not support declaring class fields in the `constructor`.
-You must declare them inside the `class` declaration instead.
+Declare  class fields inside the `class` declaration instead.
 
 **TypeScript**
 
@@ -929,7 +894,7 @@ class Person {
 }
 ```
 
-## Recipe: Construct signatures not supported in interfaces
+## Recipe: Construct signatures are not supported in interfaces
 
 **Rule `arkts-no-ctor-signatures-iface`**
 
@@ -1019,11 +984,11 @@ let x = p.x
 **Severity: error**
 
 Currently, ArkTS does not support structural identity, i.e., the compiler
-cannot compare two types’ public APIs and decide whether such types are
+cannot compare public APIs of two types and decide whether such types are
 identical. Use other mechanisms (inheritance, interfaces or type aliases)
 instead.
 
-For the examples below, types `X` and `Y` are equivalent (interchangeble)
+In the examples below, types `X` and `Y` are equivalent (interchangeble)
 in TypeScript, while in ArkTS they are not.
 
 **TypeScript**
@@ -1061,7 +1026,7 @@ type Y = X // Y is equal to X
 **Severity: error**
 
 Currently, ArkTS does not check structural equivalence for type inference,
-i.e., the compiler cannot compare two types’ public APIs and decide whether
+i.e., the compiler cannot compare public APIs of two types and decide whether
 such types are identical. Use other mechanisms (inheritance or interfaces)
 instead.
 
@@ -1135,8 +1100,8 @@ x = y // ok, X is the super class of Y
 **Severity: error**
 
 Currently, ArkTS does not check structural equivalence when checking if types
-are assignable to each other, i.e., the compiler cannot compare two types’
-public APIs and decide whether such types are identical. Use other mechanisms
+are assignable to each other, i.e., the compiler cannot compare public APIs of
+two types and decide whether such types are identical. Use other mechanisms
 (inheritance or interfaces) instead.
 
 **TypeScript**
@@ -1208,56 +1173,6 @@ x = y // ok, both are of the same type
 * Recipe: Structural typing is not supported for subtyping / supertyping
 * Recipe: Structural typing is not supported for type inference
 
-## Recipe: Optional properties are not supported for primitive types
-
-**Rule `arkts-no-opt-props`**
-
-**Severity: error**
-
-ArkTS does not support optional properties of primitive types. You can use
-properties with default values or reference types. For reference types,
-non-specified optional property is set to `null`. This rule applies both to
-classes and interfaces.
-
-**TypeScript**
-
-```typescript
-class CompilerOptions {
-    strict?: boolean
-    sourcePath?: string
-    targetPath?: string
-}
-
-let options: CompilerOptions = {
-    strict: true,
-    sourcePath: "./src"
-}
-
-if (options.targetPath == undefined) {
-    // Some logic
-}
-```
-
-**ArkTS**
-
-```typescript
-class CompilerOptions {
-    strict: boolean = false
-    sourcePath: string = ""
-    targetPath?: string
-}
-
-let options: CompilerOptions = {
-    strict: true,
-    sourcePath: "./src"
-    // targetPath is implicitly set to null
-}
-
-if (options.targetPath == null) {
-    // Some logic
-}
-```
-
 ## Recipe: Type inference in case of generic function calls is limited
 
 **Rule `arkts-no-inferred-generic-params`**
@@ -1265,8 +1180,8 @@ if (options.targetPath == null) {
 **Severity: error**
 
 ArkTS allows to omit generic type parameters if it is possible to infer
-the concrete types from the parameters passed to the function. Otherwise a
-compile-time error occurs. In particular, inference of generic type parameters
+the concrete types from the parameters passed to the function. A compile-time
+error occurs otherwise. In particular, inference of generic type parameters
 based only on function return types is prohibited.
 
 **TypeScript**
@@ -1282,7 +1197,7 @@ let y = choose("10", 20) // Compile-time error
 function greet<T>(): T {
     return "Hello" as T
 }
-let z = greet() // Type of x is inferred as "unknown"
+let z = greet() // Type of T is inferred as "unknown"
 ```
 
 **ArkTS**
@@ -1308,7 +1223,7 @@ let z = greet<string>()
 **Severity: error**
 
 Currently, ArkTS does not support structural typing, i.e., the compiler cannot
-compare two types’ public APIs and decide whether such types are identical.
+compare public APIs of two types and decide whether such types are identical.
 Use inheritance and interfaces to specify the relation between the types
 explicitly.
 
@@ -1402,8 +1317,8 @@ bar(new Y(2))
 
 **Severity: error**
 
-Currently, ArkTS does not support RegExp literals. Use library call with string
-literals instead.
+Currently, ArkTS does not support RegExp literals. Use library call with
+string literals instead.
 
 **TypeScript**
 
@@ -1424,9 +1339,9 @@ let regex: RegExp = new RegExp("/bc*d/")
 **Severity: error**
 
 ArkTS supports usage of object literals if the compiler can infer to what
-classes or interfaces such literals correspond to. Otherwise, a compile-time
-error occurs. Specifically, using literals to initialize classes and interfaces
-is not supported in following contexts:
+classes or interfaces such literals correspond to. A compile-time error
+occurs otherwise. Using literals to initialize classes and interfaces is
+specifically not supported in the following contexts:
 
 * Initialization of anything that has `any`, `Object`, or `object` type
 * Initialization of classes or interfaces with methods
@@ -1579,8 +1494,8 @@ type S = Set<{x: number, y: number}>
 
 ```typescript
 class O {
-    x: number
-    y: number
+    x: number = 0
+    y: number = 0
 }
 
 let o: O = {x: 2, y: 3}
@@ -1600,8 +1515,8 @@ type S = Set<O>
 **Severity: error**
 
 Basically, ArkTS infers the type of an array literal as a union type of its
-contents. But if there is at least one element with a non-inferrable type
-(e.g. untyped object literal), a compile-time error occurs.
+contents. However, a compile-time error occurs if there is at least one
+element with a non-inferrable type (e.g. untyped object literal).
 
 **TypeScript**
 
@@ -1638,7 +1553,8 @@ to be explicitly specified.
 **TypeScript**
 
 ```typescript
-let f = (s) => { // type any is assumed
+// Compile-time error only with noImplicitAny:
+let f = (s /* type any is assumed */) => {
     console.log(s)
 }
 ```
@@ -1658,8 +1574,8 @@ let f = (s: string) => {
 
 **Severity: error**
 
-ArkTS does not support function expressions, use arrow functions instead
-to be explicitly specified.
+ArkTS does not support function expressions. Use arrow functions instead
+to specify explicitly.
 
 **TypeScript**
 
@@ -1710,19 +1626,19 @@ generic_func<String>("string")
 
 **Severity: error**
 
-ArkTS does not support class literals. A new named class type must be
-introduced explicitly.
+ArkTS does not support class literals. Introduce new named class types
+explicitly.
 
 **TypeScript**
 
 ```typescript
 const Rectangle = class {
     constructor(height: number, width: number) {
-        this.heigth = height
+        this.height = height
         this.width = width
     }
 
-    heigth
+    height
     width
 }
 
@@ -1734,11 +1650,11 @@ const rectangle = new Rectangle(0.0, 0.0)
 ```typescript
 class Rectangle {
     constructor(height: number, width: number) {
-        this.heigth = height
+        this.height = height
         this.width = width
     }
 
-    heigth: number
+    height: number
     width: number
 }
 
@@ -1770,7 +1686,7 @@ class C1 implements C {
 
 ```typescript
 interface C {
-  foo()
+  foo(): void
 }
 
 class C1 implements C {
@@ -1786,7 +1702,7 @@ class C1 implements C {
 
 ArkTS supports accessing only those class properties that are either declared
 in the class, or accessible via inheritance. Accessing any other properties is
-prohibited and causes compile-time errors. Use proper types to check property
+prohibited, and causes compile-time errors. Use proper types to check property
 existence during compilation.
 
 **TypeScript**
@@ -1796,7 +1712,7 @@ let person = {name: "Bob", isEmployee: true}
 
 let n = person["name"]
 let e = person["isEmployee"]
-let s = person["office"] // undefined
+let s = person["office"] // Compile-time error only with noImplicitAny
 ```
 
 **ArkTS**
@@ -1835,10 +1751,13 @@ let s = person.office // Compile-time error
 
 **Severity: error**
 
-ArkTS supports `as` keyword as the only syntax for type casts.
+ArkTS supports the keyword `as` as the only syntax for type casts.
 Incorrect cast causes a compile-time error or runtime `ClassCastException`.
 `<type>` syntax for type casts is not supported.
 
+Use the expression `new ...` instead of `as` if a **primitive** type
+(e.g., a `number` or a `boolean`) must be cast to the reference type.
+
 **TypeScript**
 
 ```typescript
@@ -1858,6 +1777,14 @@ let c2 = createShape() as Circle
 // nor during runtime if cast is wrong:
 let c3 = createShape() as Square
 console.log(c3.y) // undefined
+
+// Important corner case for casting primitives to the boxed counterparts:
+// The left operand is not properly boxed here in in runtime
+// because "as" has no runtime effect in TypeScript
+let e1 = (5.0 as Number) instanceof Number // false
+
+// Number object is created and instanceof works as expected:
+let e2 = (new Number(5.0)) instanceof Number // true
 ```
 
 **ArkTS**
@@ -1875,6 +1802,9 @@ let c2 = createShape() as Circle
 
 // ClassCastException during runtime is thrown:
 let c3 = createShape() as Square
+
+// Number object is created and instanceof works as expected:
+let e2 = (new Number(5.0)) instanceof Number // true
 ```
 
 ## Recipe: JSX expressions are not supported
@@ -1906,38 +1836,7 @@ let d = -"5" // -5 as number
 let e = ~5        // -6 as number
 let f = ~"5"      // -6 as number
 let g = +"string" // NaN as number
-```
-
-**ArkTS**
 
-```typescript
-let a = +5   // 5 as number
-let b = +"5" // Compile-time error
-let c = -5   // -5 as number
-let d = -"5" // Compile-time error
-let e = ~5   // -6 as number
-let f = ~"5" // Compile-time error
-let g = +"string" // Compile-time error
-```
-
-**See also**
-
-* Recipe: Binary operators \*, /, %, -, <<, >>, >>>, &, ^ and | work only on numeric types
-* Recipe: Binary + operator supports implicit casts only for numbers and strings
-
-## Recipe: Unary `+` cannot be used for casting to `number`
-
-**Rule `arkts-no-unary-plus-cast`**
-
-**Severity: error**
-
-ArkTS does not support casting from any type to a numeric type
-by using the unary `+` operator, which can be applied only to
-numeric types.
-
-**TypeScript**
-
-```typescript
 function returnTen(): string {
     return "-10"
 }
@@ -1946,13 +1845,21 @@ function returnString(): string {
     return "string"
 }
 
-let a = +returnTen()    // -10 as number
-let b = +returnString() // NaN
+let x = +returnTen()    // -10 as number
+let y = +returnString() // NaN
 ```
 
 **ArkTS**
 
 ```typescript
+let a = +5        // 5 as number
+let b = +"5"      // Compile-time error
+let c = -5        // -5 as number
+let d = -"5"      // Compile-time error
+let e = ~5        // -6 as number
+let f = ~"5"      // Compile-time error
+let g = +"string" // Compile-time error
+
 function returnTen(): string {
     return "-10"
 }
@@ -1961,16 +1868,10 @@ function returnString(): string {
     return "string"
 }
 
-let a = +returnTen()    // Compile-time error
-let b = +returnString() // Compile-time error
+let x = +returnTen()    // Compile-time error
+let y = +returnString() // Compile-time error
 ```
 
-**See also**
-
-* Recipe: Unary operators +, - and ~ work only on numbers
-* Recipe: Binary operators \*, /, %, -, <<, >>, >>>, &, ^ and | work only on numeric types
-* Recipe: Binary + operator supports implicit casts only for numbers and strings
-
 ## Recipe: `delete` operator is not supported
 
 **Rule `arkts-no-delete`**
@@ -1999,8 +1900,8 @@ delete p.y
 // and assign null to mark value absence:
 
 class Point {
-    x: number | null
-    y: number | null
+    x: number | null = 0
+    y: number | null = 0
 }
 
 let p = new Point()
@@ -2023,8 +1924,8 @@ p.y = null
 
 **Severity: error**
 
-ArkTS supports `typeof` operator only in the expression context. Specifying
-type notations using `typeof` is not supported.
+ArkTS supports `typeof` operator only in the expression context. Using
+`typeof` to specify type notations is not supported.
 
 **TypeScript**
 
@@ -2059,77 +1960,19 @@ let s2: string
 * Recipe: Dynamic property declaration is not supported
 * Recipe: Usage of standard library is restricted
 
-## Recipe: Binary operators `*`, `/`, `%`, `-`, `<<`, `>>`, `>>>`, `&`, `^` and `|` work only on numeric types
-
-**Rule `arkts-no-polymorphic-binops`**
-
-**Severity: error**
-
-ArkTS allows applying binary operators `*`, `/`, `%`, `-`, `<<`,
-`>>`, `>>>`, `&`, `^` and `|` only to values of numeric types.
-Implicit casts from other types to numeric types are prohibited and cause
-compile-time errors.
-
-**TypeScript**
-
-```typescript
-let a = (5 & 5)     // 5
-let b = (5.5 & 5.5) // 5, not 5.5
-let c = (5 | 5)     // 5
-let d = (5.5 | 5.5) // 5, not 5.5
-
-enum Direction {
-    Up = -1,
-    Down
-}
-let e = Direction.Up >> 1 // -1
-let f = Direction.Up >>> 1 // 2147483647
-
-let g = ("10" as any) << 1  // 20
-let h = ("str" as any) << 1 // 0
-
-let i = 10 * 5
-let j = 10 / 5
-let k = 10 % 5
-let l = 10 - 5
-```
-
-**ArkTS**
-
-```typescript
-let a = (5 & 5)     // 5
-let b = (5.5 & 5.5) // Compile-time error
-let c = (5 | 5)     // 5
-let d = (5.5 | 5.5) // Compile-time error
-
-enum Direction {
-    Up,
-    Down
-}
-
-let e = Direction.Up >> 1  // 0
-let f = Direction.Up >>> 1 // 0
-
-let i = 10 * 5
-let j = 10 / 5
-let k = 10 % 5
-let l = 10 - 5
-```
-
-**See also**
-
-* Recipe: Unary operators +, - and ~ work only on numbers
-* Recipe: Unary + cannot be used for casting to number
-* Recipe: Binary + operator supports implicit casts only for numbers and strings
-
-## Recipe: Binary `+` operator supports implicit casts only for numbers and strings
+## Recipe: Binary `+` operator supports implicit casts only for numbers, enums and strings
 
 **Rule `arkts-no-polymorphic-plus`**
 
 **Severity: error**
 
-ArkTS supports implicit casts for `+` only for strings and numbers.
-Elsewhere, any form of an explicit cast to string is required.
+If one of the operands of the binary `+` operator is of the string type
+(including enum string constant), then the other operand can be of any type,
+and its value is implicitly converted to string.
+Otherwise, ArkTS supports implicit casts with `+` only for numbers and
+numeric enum constants.
+ArkTS, like TypeScript, does not support the operator `+` for the booleans.
+Elsewhere, any form of an explicit cast is required.
 
 **TypeScript**
 
@@ -2145,6 +1988,10 @@ let e = "Hello, " + "world!" // "Hello, world!"
 let f = "string" + true // "stringtrue"
 
 let g = (new Object()) + "string" // "[object Object]string"
+
+let i = true + true // JS: 2, TS: compile-time error
+let j = true + 2 // JS: 3, TS: compile-time error
+let k = E.E1 + true // JS: 1, TS: compile-time error
 ```
 
 **ArkTS**
@@ -2161,13 +2008,16 @@ let e = "Hello, " + "world!" // "Hello, world!"
 let f = "string" + true // "stringtrue"
 
 let g = (new Object()).toString() + "string"
+
+
+let i = true + true // compile-time error
+let j = true + 2 // compile-time error
+let k = E.E1 + true // compile-time error
 ```
 
 **See also**
 
 * Recipe: Unary operators +, - and ~ work only on numbers
-* Recipe: Unary + cannot be used for casting to number
-* Recipe: Binary operators \*, /, %, -, <<, >>, >>>, &, ^ and | work only on numeric types
 
 ## Recipe: `instanceof` operator is partially supported
 
@@ -2175,40 +2025,38 @@ let g = (new Object()).toString() + "string"
 
 **Severity: error**
 
-In TypeScript, the left-hand side of an `instanceof` expression must be of type
-`any`, an object type or a type parameter, otherwise the result is `false`.
-In ArkTS, the left-hand side expression may be of any reference type, otherwise
-a compile-time error occurs. In addition, the left operand in ArkTS cannot be
-a type.
+In TypeScript, the left-hand side of an `instanceof` expression must be of the type
+`any`, an object type or a type parameter; the result is `false` otherwise.
+In ArkTS, the left-hand side expression may be of any reference type;
+a compile-time error occurs otherwise. In addition, the left operand in ArkTS
+cannot be a type.
 
 **TypeScript**
 
 ```typescript
-class X {}
+class X {
+    // ...
+}
 
 let a = (new X()) instanceof Object // true
 let b = (new X()) instanceof X      // true
-// left operand is a type:
-let c = X instanceof Object // true
-let d = X instanceof X // false
 
-// left operand is not of type any
-let e = (5.0 as Number) instanceof Number // false
+let c = X instanceof Object // true, left operand is a type
+let d = X instanceof X      // false, left operand is a type
 ```
 
 **ArkTS**
 
 ```typescript
-class X {}
+class X {
+    // ...
+}
 
 let a = (new X()) instanceof Object // true
 let b = (new X()) instanceof X      // true
-// left operand is a type:
-let c = X instanceof Object // Compile-time error
-let d = X instanceof X // Compile-time error
 
-// left operand may be of any reference type, like number
-let e = (5.0 as Number) instanceof Number // true
+let c = X instanceof Object // Compile-time error, left operand is a type
+let d = X instanceof X      // Compile-time error, left operand is a type
 ```
 
 ## Recipe: `in` operator is not supported
@@ -2217,9 +2065,9 @@ let e = (5.0 as Number) instanceof Number // true
 
 **Severity: error**
 
-ArkTS does not support the `in` operator. However, this operator makes
-little sense since the object layout is known at compile time and cannot
-be modified at runtime. Use `instanceof` as a work-around if you still need
+ArkTS does not support the operator `in`. However, this operator makes
+little sense since the object layout is known at compile time, and cannot
+be modified at runtime. Use `instanceof` as a workaround if you still need
 to check whether certain class members exist.
 
 **TypeScript**
@@ -2261,8 +2109,8 @@ let b = p instanceof Person // true, and "name" is guaranteed to be present
 
 **Severity: error**
 
-ArkTS does not support destructuring assignment. Other idioms (e.g.,
-using a temporary variable, where applicable) can be used for replacement.
+ArkTS does not support destructuring assignment. Use other idioms (e.g.,
+a temporary variable, where applicable) for replacement.
 
 **TypeScript**
 
@@ -2285,11 +2133,11 @@ let tmp = one
 one = two
 two = tmp
 
-let data: Number[] = [1,2,3,4]
+let data: Number[] = [1, 2, 3, 4]
 let head = data[0]
-let tail = new Number[data.length - 1]
+let tail: Number[] = []
 for (let i = 1; i < data.length; ++i) {
-    tail[i - 1] = data[i]
+    tail.push(data[i])
 }
 ```
 
@@ -2378,9 +2226,9 @@ let y = zp.y
 
 **Severity: error**
 
-Currently, ArkTS does not support inference of implied types. Use explicit
-type notation instead. Use `Object[]` if you need containers that hold
-data of mixed types.
+Currently, ArkTS does not support inference of implied types.
+Use explicit type notation instead.
+Use `Object[]` if you need containers that hold data of mixed types.
 
 **TypeScript**
 
@@ -2407,9 +2255,8 @@ let c1 = arr[2]
 
 **Severity: error**
 
-In TypeScript catch clause variable type annotation must be `any` or `unknown`
-if specified. As ArkTS does not support these types, a type annotation should
-be omitted.
+In TypeScript, catch clause variable type annotation must be `any` or `unknown`
+if specified. As ArkTS does not support these types, omit type annotations.
 
 **TypeScript**
 
@@ -2417,7 +2264,9 @@ be omitted.
 try {
     // some code
 }
-catch (a: unknown) {}
+catch (a: unknown) {
+    // handle error
+}
 ```
 
 **ArkTS**
@@ -2426,7 +2275,9 @@ catch (a: unknown) {}
 try {
     // some code
 }
-catch (a) {}
+catch (a) {
+    // handle error
+}
 ```
 
 **See also**
@@ -2441,8 +2292,8 @@ catch (a) {}
 
 ArkTS does not support the iteration over object contents by the
 `for .. in` loop. For objects, iteration over properties at runtime is
-considered redundant because object layout is known at compile time and cannot
-change at runtime. For arrays, you can iterate with the regular `for` loop.
+considered redundant because object layout is known at compile time, and
+cannot change at runtime. For arrays, iterate with the regular `for` loop.
 
 **TypeScript**
 
@@ -2469,7 +2320,7 @@ for (let i = 0; i < a.length; ++i) {
 
 ## Recipe: Iterable interfaces are not supported
 
-**Rule `arkts-noiterable`**
+**Rule `arkts-no-iterable`**
 
 **Severity: error**
 
@@ -2505,7 +2356,7 @@ for (let s of a) {
 
 ```typescript
 let a: Set<number> = new Set([1, 2, 3])
-let numbers = a.values()
+let numbers = Array.from(a.values())
 for (let n of numbers) {
     console.log(n)
 }
@@ -2523,7 +2374,7 @@ for (let n of numbers) {
 **Severity: error**
 
 ArkTS does not support mapped types. Use other language idioms and regular
-classes to achieve the same behaviour.
+classes to achieve that same behaviour.
 
 **TypeScript**
 
@@ -2558,7 +2409,23 @@ class CFlags {
 **Severity: error**
 
 ArkTS does not support the `with` statement. Use other language idioms
-(including fully qualified names of functions) to achieve the same behaviour.
+(including fully qualified names of functions) to achieve that same behaviour.
+
+**TypeScript**
+
+```typescript
+with (Math) { // Compile-time error, but JavaScript code still emitted
+    let r: number = 42
+    console.log("Area: ", PI * r * r)
+}
+```
+
+**ArkTS**
+
+```typescript
+let r: number = 42
+console.log("Area: ", Math.PI * r * r)
+```
 
 ## Recipe: Values computed at runtime are not supported in `case` statements
 
@@ -2688,6 +2555,7 @@ explicitly.
 **TypeScript**
 
 ```typescript
+// Compile-time error with noImplicitAny
 function f(x: number) {
     if (x <= 0) {
         return x
@@ -2695,6 +2563,7 @@ function f(x: number) {
     return g(x)
 }
 
+// Compile-time error with noImplicitAny
 function g(x: number) {
     return f(x - 1)
 }
@@ -2718,8 +2587,8 @@ function f(x: number) : number {
     return g(x)
 }
 
-// Explicit return type is required:
-function g(x: number) : number {
+// Return type may be omitted, it is inferred from f's explicit type:
+function g(x: number) {
     return f(x - 1)
 }
 
@@ -2738,8 +2607,8 @@ console.log(doOperation(2, 3))
 
 **Severity: error**
 
-ArkTS requires that parameters must be passed directly to the function, and
-local names must be assigned manually.
+ArkTS requires parameters to be passed directly to the function, and
+local names to be assigned manually.
 
 **TypeScript**
 
@@ -2824,7 +2693,7 @@ ArkTS does not support the usage of `this` inside stand-alone functions.
 
 ```typescript
 function foo(i: number) {
-    this.count = i
+    this.count = i // Compile-time error only with noImplicitThis
 }
 
 class A {
@@ -2983,7 +2852,7 @@ function main(): void {
 **Severity: error**
 
 ArkTS has no keyof operator because the object layout is defined
-at compile time and cannot be changed at runtime. Object fields can only be
+at compile time, and cannot be changed at runtime. Object fields can only be
 accessed directly.
 
 **TypeScript**
@@ -3021,7 +2890,6 @@ function getPropertyValue(obj: Point, key: string): number {
         return obj.y
     }
     throw new Error()  // No such property
-    return 0
 }
 
 function main(): void {
@@ -3038,7 +2906,7 @@ function main(): void {
 **Severity: error**
 
 The only supported scenario for the spread operator is to spread an array into
-the rest parameter. Otherwise manually “unpack” data from arrays and objects,
+the rest parameter. Otherwise, manually “unpack” data from arrays and objects,
 where necessary.
 
 **TypeScript**
@@ -3097,15 +2965,15 @@ console.log(p3d.x, p3d.y, p3d.z)
 
 ## Recipe: Interface declarations (extends same property)
 
-**Rule `arkts-no-extend-same-property`**
+**Rule `arkts-no-extend-same-prop`**
 
 **Severity: error**
 
-In TypeScript, an interface that extends two other interfaces with the same method,
+In TypeScript, an interface that extends two other interfaces with the same method
 must declare that method with a combined result type. It is not allowed in
 ArkTS because ArkTS does not allow an interface to contain two methods with
 signatures that are  not distinguishable, e.g., two methods that have the same
-parameter lists, but different return types.
+parameter lists but different return types.
 
 **TypeScript**
 
@@ -3198,8 +3066,8 @@ class C implements Mover, Shaker {
 
 **Severity: error**
 
-ArkTS does not support merging declratations. All definitions of classes,
-interfaces and so on must be kept compact in the code base.
+ArkTS does not support merging declratations. Keep all definitions of classes,
+interfaces and so on compact in the codebase.
 
 **TypeScript**
 
@@ -3270,11 +3138,13 @@ interface SelectableControl extends Control {
 
 **Severity: error**
 
-ArkTS requires that object layout is determined in compile-time and cannot
-be changed at runtime. There for no runtime property-based checks are supported.
-If you need to do a type cast, use `as` operator and use desired properties
-and methods. If some property doesn’t exist then an attempt to reference it
-will result in a compile-time error.
+ArkTS requires that object layout is determined at compile time, and cannot
+be changed at runtime. Therefore, property-based runtime checks are not
+supported.
+If you need to do a type cast, use the operator `as` with desired properties
+and methods.
+If some property does not exist, then an attempt to refer to it causes a
+compile-time error.
 
 **TypeScript**
 
@@ -3385,10 +3255,10 @@ const person = createPerson(Impersonizer, "John", 30)
 
 **Severity: error**
 
-ArkTS does not support dynamic property declaration. All object properties must
-be declared immediately in the class. While it can be replaced with an array
-of objects, it is still better to adhere to the static language paradigm and
-declare fields, their names and types explicitly.
+ArkTS does not support dynamic property declaration. Declare all object
+properties immediately in the class. While replacement for an array of
+objects is possible, it is still better to adhere to the static language
+paradigm, and declare fields, their names and types explicitly.
 
 **TypeScript**
 
@@ -3403,7 +3273,7 @@ const person: Person = {
     name: "John",
     age: 30,
     email: "john@example.com",
-    phone: 1234567890,
+    phoneNumber: 1234567890,
 }
 ```
 
@@ -3414,13 +3284,13 @@ class Person {
     name: string
     age: number
     email: string
-    phone: number
+    phoneNumber: number
 
-    constructor(name: string, age: number, email: string, phone: number) {
+    constructor(name: string, age: number, email: string, phoneNumber: number) {
         this.name = name
         this.age = age
         this.email = email
-        this.phone = phone
+        this.phoneNumber = phoneNumber
     }
 }
 
@@ -3448,7 +3318,7 @@ function main(): void {
 
 ArkTS does not support initializing members of enumerations with expressions
 that are evaluated during program runtime. Besides, all explicitly set
-initializers must be of the same time.
+initializers must be of the same type.
 
 **TypeScript**
 
@@ -3494,8 +3364,8 @@ enum E2 {
 
 **Severity: error**
 
-ArkTS does not support merging declratations for `enum`.
-The declaration of each `enum` must be kept compact in the code base.
+ArkTS does not support merging declratations for `enum`. Keep the
+declaration of each `enum` compact in the codebase.
 
 **TypeScript**
 
@@ -3555,26 +3425,6 @@ namespace MyNamespace {
 MyNamespace.x = 2
 ```
 
-## Recipe: Scripts and modules
-
-**Rule `arkts-no-scripts`**
-
-**Severity: error**
-
-In general, scripts and modules in ArkTS are very close to TypeScript.
-Differences are described in separate recipes.
-
-**See also**
-
-* Recipe: Special import type declarations are not supported
-* Recipe: Importing a module for side-effects only is not supported
-* Recipe: import default as ... is not supported
-* Recipe: require is not supported
-* Recipe: Renaming in export declarations is not supported
-* Recipe: Export list declaration is not supported
-* Recipe: Re-exporting is not supported
-* Recipe: export = ... assignment is not supported
-
 ## Recipe: Non-declaration statements in namespaces are not supported
 
 **Rule `arkts-no-ns-statements`**
@@ -3621,23 +3471,23 @@ Use ordinary import instead.
 
 ```typescript
 // Re-using the same import
-import { APIResponseType } from "./api"
+import { APIResponseType } from "api"
 
 // Explicitly use import type
-import type { APIResponseType } from "./api"
+import type { APIResponseType } from "api"
 ```
 
 **ArkTS**
 
 ```typescript
-import { APIResponseType } from "./api"
+import { APIResponseType } from "api"
 ```
 
 **See also**
 
 * Recipe: Importing a module for side-effects only is not supported
 * Recipe: import default as ... is not supported
-* Recipe: require is not supported
+* Recipe: require and import assignment are not supported
 
 ## Recipe: Importing a module for side-effects only is not supported
 
@@ -3689,13 +3539,15 @@ import { default as d } from "mod"
 import d from "mod"
 ```
 
-## Recipe: `require` is not supported
+## Recipe: `require` and `import` assignment are not supported
 
 **Rule `arkts-no-require`**
 
 **Severity: error**
 
-ArkTS does not support importing via `require`. Use `import` instead.
+ArkTS does not support importing via `require`.
+`import` assignments are not supported either.
+Use regular `import` instead.
 
 **TypeScript**
 
@@ -3709,139 +3561,59 @@ import m = require("mod")
 import * as m from "mod"
 ```
 
-## Recipe: Renaming in export declarations is not supported
-
-**Rule `arkts-no-export-renaming`**
-
-**Severity: error**
-
-ArkTS does not support renaming in export declarations. Similar effect
-can be achieved through setting an alias for the exported entity.
-
-**TypeScript**
-
-```typescript
-// file1.ts
-class MyClass {
-    // ...
-}
-
-export { MyClass as RenamedClass }
-
-// file2.ts
-import { RenamedClass } from "./file1"
-
-function main(): void {
-    const myObject = new RenamedClass()
-    // ...
-}
-```
-
-**ArkTS**
-
-```typescript
-// module1
-class MyClass {
-    // ...
-}
-
-export type RenamedClass = MyClass
-
-// module2
-import { RenamedClass } from "./module1"
-
-function main(): void {
-    const myObject = new RenamedClass()
-    // ...
-}
-```
-
-**See also**
-
-* Recipe: Export list declaration is not supported
-* Recipe: Re-exporting is not supported
-* Recipe: export = ... assignment is not supported
-
-## Recipe: Export list declaration is not supported
-
-**Rule `arkts-no-export-list-decl`**
-
-**Severity: error**
-
-ArkTS does not support syntax of export list declarations. All exported
-entities must be explicitly annotated with the `export` keyword.
-
-**TypeScript**
-
-```typescript
-export { x }
-export { x } from "mod"
-export { x, y as b, z as c }
-```
-
-**ArkTS**
-
-```typescript
-let x = 1
-class MyClass {}
-export let y = x, z: number = 2
-export RenamedClass = MyClass
-```
-
 **See also**
 
-* Recipe: Renaming in export declarations is not supported
-* Recipe: Re-exporting is not supported
 * Recipe: export = ... assignment is not supported
 
-## Recipe: Re-exporting is not supported
+## Recipe: Re-exporting is supported with restrictions
 
-**Rule `arkts-no-reexport`**
+**Rule `arkts-limited-reexport`**
 
 **Severity: error**
 
-ArkTS does not support re-exporting. All desired entities must be
-imported explicitly from the modules that export them.
+ArkTS supports re-exporting syntax which covers most common cases of re-export:
+re-exporting imported entities and re-exporting which is combined with renaming.
+Other syntax flavors like `export * as ...` are not supported.
 
 **TypeScript**
 
 ```typescript
 // module1
-export class MyClass {
+export class Class1 {
+    // ...
+}
+export class Class2 {
     // ...
 }
 
 // module2
-export { MyClass } from "module1"
+export * as utilities from "module1"
 
 // consumer module
-import { MyClass } from "module2"
-
-const myInstance = new MyClass()
+import { utilities } from "module2"
 ```
 
 **ArkTS**
 
 ```typescript
 // module1
-export class MyClass {
+export class Class1 {
+    // ...
+}
+export class C2 {
     // ...
 }
 
 // module2
-// some stuff
+export { Class1 } from "module1"
+export { C2 as Class2 } from "module1"
 
 // consumer module
-import { MyClass } from "module1"
-import * from "module2"
-
-const myInstance = new MyClass()
+import { Class1, Class2 } from "module2"
 ```
 
 **See also**
 
-* Recipe: Renaming in export declarations is not supported
-* Recipe: Export list declaration is not supported
 * Recipe: export = ... assignment is not supported
 
 ## Recipe: `export = ...` assignment is not supported
@@ -3887,30 +3659,47 @@ let p = Pt.origin
 
 **See also**
 
-* Recipe: Renaming in export declarations is not supported
-* Recipe: Export list declaration is not supported
-* Recipe: Re-exporting is not supported
+* Recipe: require and import assignment are not supported
+* Recipe: Re-exporting is supported with restrictions
 
-## Recipe: Special export type declarations are not supported
+## Recipe: Special `export type` declarations are not supported
 
 **Rule `arkts-no-special-exports`**
 
 **Severity: error**
 
-ArkTS does not have a special notation for exporting types.
-Use ordinary export instead.
+ArkTS does not have a special notation for exporting types through
+`export type ...`. Use ordinary export instead.
 
 **TypeScript**
 
 ```typescript
-class C {}
-export type { C }
+// Explicitly exported class:
+export class Class1 {
+    // ...
+}
+
+// Declared class later exported through export type ...
+class Class2 {
+    // ...
+}
+
+// This is not supported:
+export type { Class2 }
 ```
 
 **ArkTS**
 
 ```typescript
-export class C {}
+// Explicitly exported class:
+export class Class1 {
+    // ...
+}
+
+// Explicitly exported class:
+export class Class2 {
+    // ...
+}
 ```
 
 ## Recipe: Ambient module declaration is not supported
@@ -3934,7 +3723,7 @@ declare module "someModule" {
 
 ```typescript
 // Import what you need from the original module
-import { normalize } from "../someModule"
+import { normalize } from "someModule"
 ```
 
 **See also**
@@ -3948,16 +3737,34 @@ import { normalize } from "../someModule"
 
 **Severity: error**
 
-ArkTS does not supported wildcards in module names because in ArkTS, import
-is a compile-time, not a runtime feature. Use ordinary export syntax instead.
+ArkTS does not support wildcards in module names because in the language
+import is a compile-time, not a runtime feature.
+Use ordinary export syntax instead.
 
 **TypeScript**
 
 ```typescript
+// Declaration:
 declare module "*!text" {
     const content: string
     export default content
 }
+
+// Consuming code:
+import fileContent from "some.txt!text"
+```
+
+**ArkTS**
+
+```typescript
+// Declaration:
+declare namespace N {
+    function foo(x: number): number
+}
+
+// Consuming code:
+import * from "module"
+console.log("N.foo called: ", N.foo(42))
 ```
 
 **See also**
@@ -3972,10 +3779,10 @@ declare module "*!text" {
 
 **Severity: error**
 
-ArkTS does not support universal module definitions (UMD) because in ArkTS
-there is no concept of “script” (as opposed to “module”). Besides, in ArkTS
-import is a compile-time, not a runtime feature. Use ordinary syntax for
-`export` and `import` instead.
+ArkTS does not support universal module definitions (UMD) because in the
+language there is no concept of “script” (as opposed to “module”).
+Besides, in ArkTS import is a compile-time, not a runtime feature.
+Use ordinary syntax for `export` and `import` instead.
 
 **TypeScript**
 
@@ -3997,7 +3804,7 @@ namespace mathLib {
 }
 
 // in program
-import { mathLib } from "./math-lib"
+import { mathLib } from "math-lib"
 mathLib.isPrime(2)
 ```
 
@@ -4011,19 +3818,19 @@ mathLib.isPrime(2)
 
 **Severity: error**
 
-ArkTS does not allow to use `.js` extension in module identifiers because it
-has its own mechanisms for interoperating with JavaScript.
+ArkTS does not allow using `.js` extension in module identifiers because
+it has its own mechanisms for interoperating with JavaScript.
 
 **TypeScript**
 
 ```typescript
-import { something } from "./module.js"
+import { something } from "module.js"
 ```
 
 **ArkTS**
 
 ```typescript
-import { something } from "./module"
+import { something } from "module"
 ```
 
 **See also**
@@ -4039,7 +3846,7 @@ import { something } from "./module"
 
 ArkTS does not support `new.target` because there is no concept of runtime
 prototype inheritance in the language. This feature is considered not applicable
-to the statically typing.
+to static typing.
 
 **TypeScript**
 
@@ -4055,6 +3862,20 @@ class CustomError extends Error {
 }
 ```
 
+**ArkTS**
+
+```typescript
+class CustomError extends Error {
+    constructor(message?: string) {
+        // Call parent's constructor, inheritance chain is static and
+        // cannot be modified in runtime
+        super(message)
+        console.log(this instanceof Error) // true
+    }
+}
+let ce = new CustomError()
+```
+
 **See also**
 
 * Recipe: Prototype assignment is not supported
@@ -4066,19 +3887,19 @@ class CustomError extends Error {
 **Severity: error**
 
 ArkTS does not support such “runtime” import expressions as `await import...`
-because in ArkTS import is a compile-time, not a runtime feature. Use regular
-import syntax instead.
+because in the language import is a compile-time, not a runtime feature.
+Use regular import syntax instead.
 
 **TypeScript**
 
 ```typescript
-const zipUtil = await import("./utils/create-zip-file")
+const zipUtil = await import("utils/create-zip-file")
 ```
 
 **ArkTS**
 
 ```typescript
-import { zipUtil } from "./utils/create-zip-file"
+import { zipUtil } from "utils/create-zip-file"
 ```
 
 **See also**
@@ -4094,8 +3915,8 @@ import { zipUtil } from "./utils/create-zip-file"
 **Severity: error**
 
 ArkTS does not support definite assignment assertions `let v!: T` because
-they are considered an excessive compiler hint. Use declaration with
-initialization instead.
+they are considered an excessive compiler hint.
+Use declaration with initialization instead.
 
 **TypeScript**
 
@@ -4129,17 +3950,18 @@ console.log("x = " + x)
 
 **Severity: error**
 
-ArkTS does not support IIFEs as namespace declarations because in ArkTS,
-anonymous functions cannot serve as namespaces. Use regular syntax for
-namespaces instead.
+ArkTS does not support IIFEs as namespace declarations because anonymous
+functions in the language cannot serve as namespaces.
+Use regular syntax for namespaces instead.
 
 **TypeScript**
 
 ```typescript
 var C = (function() {
-    function C(n) {
-        this.p = n
+    function C(n: number) {
+        this.p = n // Compile-time error only with noImplicitThis
     }
+    C.staticProperty = 0
     return C
 })()
 C.staticProperty = 1
@@ -4161,13 +3983,14 @@ namespace C {
 
 ArkTS does not support prototype assignment because there is no concept of
 runtime prototype inheritance in the language. This feature is considered not
-applicable to the static typing.
+applicable to static typing. Mechanism of classes and / or interfaces must
+be used instead to statically “combine” methods to data together.
 
 **TypeScript**
 
 ```typescript
-var C = function(p) {
-    this.p = p
+var C = function(p: number) {
+    this.p = p // Compile-time error only with noImplicitThis
 }
 
 C.prototype = {
@@ -4176,8 +3999,22 @@ C.prototype = {
     }
 }
 
-C.prototype.q = function(r) {
-    return this.p === r
+C.prototype.q = function(r: number) {
+    return this.p == r
+}
+```
+
+**ArkTS**
+
+```typescript
+class C {
+    p: number = 0
+    m() {
+        console.log(this.p)
+    }
+    q(r: number) {
+        return this.p == r
+    }
 }
 ```
 
@@ -4211,7 +4048,7 @@ globalThis.abc = 200
 export let abc : number = 0
 
 // file2
-import * as M from "../file1"
+import * as M from "file1"
 
 M.abc = 200
 ```
@@ -4221,15 +4058,18 @@ M.abc = 200
 * Recipe: Declaring properties on functions is not supported
 * Recipe: Usage of standard library is restricted
 
-## Recipe: Utility types are not supported
+## Recipe: Some of utility types are not supported
 
 **Rule `arkts-no-utility-types`**
 
 **Severity: error**
 
 Currently ArkTS does not support utility types from TypeScript extensions to the
-standard library (`Omit`, `Partial`, `Readonly`, `Record`, `Pick`,
-etc.).
+standard library (`Omit`, `Pick`, etc.). Exceptions are: `Partial`,
+`Record`.
+
+For the type *Record<K, V>*, the type of an indexing expression *rec[index]* is
+of the type *V | undefined*.
 
 **TypeScript**
 
@@ -4241,20 +4081,55 @@ type Person = {
 }
 
 type QuantumPerson = Omit<Person, "location">
+
+let persons : Record<string, Person> = {
+    "Alice": {
+        name: "Alice",
+        age: 32,
+        location: "Shanghai"
+    },
+    "Bob": {
+        name: "Bob",
+        age: 48,
+        location: "New York"
+    }
+}
+console.log(persons["Bob"].age)
+console.log(persons["Rob"].age) // Runtime exception
 ```
 
 **ArkTS**
 
 ```typescript
 class Person {
-    name: string
-    age: number
-    location: string
+    name: string = ""
+    age: number = 0
+    location: string = ""
 }
 
 class QuantumPerson {
-    name: string
-    age: number
+    name: string = ""
+    age: number = 0
+}
+
+type OptionalPerson = Person | undefined
+let persons : Record<string, OptionalPerson> = {
+// Or:
+// let persons : Record<string, Person | undefined> = {
+    "Alice": {
+        name: "Alice",
+        age: 32,
+        location: "Shanghai"
+    },
+    "Bob": {
+        name: "Bob",
+        age: 48,
+        location: "New York"
+    }
+}
+console.log(persons["Bob"]!.age)
+if (persons["Rob"]) { // Explicit value check, no runtime exception
+    console.log(persons["Rob"].age)
 }
 ```
 
@@ -4303,15 +4178,17 @@ class MyImage {
     // ...
 }
 
-function readImage(
+async function readImage(
     path: string, callback: (err: Error, image: MyImage) => void
 ) : Promise<MyImage>
 {
-    // async implementation
+    // In real world, the implementation is more complex,
+    // involving real network / DB logic, etc.
+    return await new MyImage()
 }
 
 function readImageSync(path: string) : MyImage {
-    // sync implementation
+    return new MyImage()
 }
 ```
 
@@ -4325,12 +4202,12 @@ function readImageSync(path: string) : MyImage {
 
 **Severity: error**
 
-ArkTS does not allow to use standard library functions `Function.apply`,
-`Function.bind`, `Function.call`. These APIs are needed in the standard
+ArkTS does not allow using standard library functions `Function.apply`,
+`Function.bind` and `Function.call`. These APIs are needed in the standard
 library to explicitly set `this` parameter for the called function.
-In ArkTS semantics of `this` is restricted to the conventional OOP style,
-and usage of `this` in stand-alone functions is prohibited. Thus these
-functions are excessive.
+In ArkTS the semantics of `this` is restricted to the conventional OOP
+style, and the usage of `this` in stand-alone functions is prohibited.
+Thus these functions are excessive.
 
 **TypeScript**
 
@@ -4382,7 +4259,7 @@ console.log(person1.fullName())
 
 **Severity: error**
 
-Currently ArkTS supports `readonly` for properties, but not for parameters.
+Currently, ArkTS supports `readonly` for properties, but not for parameters.
 
 **TypeScript**
 
@@ -4435,7 +4312,7 @@ let x : string = "hello"
 let y : number[] = [10, 20]
 
 class Label {
-    text : string
+    text : string = ""
 }
 
 // Type 'Label':
@@ -4450,7 +4327,7 @@ let z : Label = {
 
 **Severity: error**
 
-ArkTS does not support import assertions because in ArkTS, import is a
+ArkTS does not support import assertions because in the language import is a
 compile-time, not a runtime feature. So asserting correctness of imported APIs
 in runtime does not make sense for the statically typed language. Use ordinary
 `import` syntax instead.
@@ -4458,14 +4335,14 @@ in runtime does not make sense for the statically typed language. Use ordinary
 **TypeScript**
 
 ```typescript
-import { obj } from "./something.json" assert { type: "json" }
+import { obj } from "something.json" assert { type: "json" }
 ```
 
 **ArkTS**
 
 ```typescript
 // Correctness of importing T will be checked in compile-time:
-import { something } from "./module"
+import { something } from "module"
 ```
 
 **See also**
@@ -4480,10 +4357,10 @@ import { something } from "./module"
 
 **Severity: error**
 
-ArkTS does not allow usage of some APIs from the TypeScript/JavaScript standard library.
-The most part of the restricted APIs relates to manipulating objects in
-dynamic manner, which is not compatible with the static typing. Following APIs
-are prohibited from usage:
+ArkTS does not allow using some APIs from the TypeScript/JavaScript standard library.
+The most part of the restricted APIs relates to manipulating objects in a
+dynamic manner, which is not compatible with static typing. The usage of
+the following APIs is prohibited:
 
 Properties and functions of the global object: `eval`,
 `Infinity`, `NaN`, `isFinite`, `isNaN`, `parseFloat`, `parseInt`,
@@ -4526,3 +4403,161 @@ Properties and functions of the global object: `eval`,
 * Recipe: Dynamic property declaration is not supported
 * Recipe: globalThis is not supported
 
+## Recipe: Strict type checking is enforced
+
+**Rule `arkts-strict-typing`**
+
+**Severity: error**
+
+Type checker in ArkTS is not optional, the code must be explicitly and
+correctly types to be compiled and run. When porting from the standard TypeScript,
+turn on the following flags: `noImplicitReturns`, `strictFunctionTypes`,
+`strictNullChecks`, `strictPropertyInitialization`.
+
+**TypeScript**
+
+```typescript
+class C {
+    n: number // Compile-time error only with strictPropertyInitialization
+    s: string // Compile-time error only with strictPropertyInitialization
+}
+
+// Compile-time error only with noImplicitReturns
+function foo(s: string): string {
+    if (s != "") {
+        console.log(s)
+        return s
+    } else {
+        console.log(s)
+    }
+}
+
+let n: number = null // Compile-time error only with strictNullChecks
+```
+
+**ArkTS**
+
+```typescript
+class C {
+    n: number = 0
+    s: string = ""
+}
+
+function foo(s: string): string {
+    console.log(s)
+    return s
+}
+
+let n1: number | null = null
+let n2: number = 0
+```
+
+**See also**
+
+* Recipe: Use explicit types instead of any, unknown
+* Recipe: Switching off type checks with in-place comments is not allowed
+
+## Recipe: Switching off type checks with in-place comments is not allowed
+
+**Rule `arkts-strict-typing-required`**
+
+**Severity: error**
+
+Type checker in ArkTS is not optional, the code must be explicitly and
+correctly typed to be compiled and run. “Suppressing” type checker in-place
+with special comments is not allowed. In particular, `@ts-ignore` and
+`@ts-nocheck` annotations are not supported.
+
+**TypeScript**
+
+```typescript
+// @ts-nocheck
+// ...
+// Some code with switched off type checker
+// ...
+
+let s1: string = null // No error, type checker suppressed
+
+// @ts-ignore
+let s2: string = null // No error, type checker suppressed
+```
+
+**ArkTS**
+
+```typescript
+let s1: string | null = null // No error, properly types
+let s2: string = null // Compile-time error
+```
+
+**See also**
+
+* Recipe: Use explicit types instead of any, unknown
+* Recipe: Strict type checking is enforced
+
+## Recipe: No dependencies on TypeScript code are currently allowed
+
+**Rule `arkts-no-ts-deps`**
+
+**Severity: error**
+
+Currently, the codebase implemented in the standard TypeScript language must not
+depend on ArkTS through importing the ArkTS codebase. Imports in reverse
+direction are supported.
+
+**TypeScript**
+
+```typescript
+// app.ets
+export class C {
+    // ...
+}
+
+// lib.ts
+import { C } from "app"
+```
+
+**ArkTS**
+
+```typescript
+// lib1.ets
+export class C {
+    // ...
+}
+
+// lib2.ets
+import { C } from "lib1"
+```
+
+## Recipe: No decorators except ArkUI decorators are currently allowed
+
+**Rule `arkts-no-decorators-except-arkui`**
+
+**Severity: error**
+
+Currently, only ArkUI decorators are allowed  in the ArkTS.
+Any other decorator will cause a compile-time error.
+
+**TypeScript**
+
+```typescript
+function classDecorator(x: any, y: any): void {
+    //
+}
+
+@classDecorator
+class BugReport {
+}
+```
+
+**ArkTS**
+
+```typescript
+function classDecorator(x: any, y: any): void {
+    //
+}
+
+@classDecorator // compile-time error: unsupported decorator
+class BugReport {
+}
+```
+

en/application-dev/reference/apis/Readme-EN.md

@@ -16,6 +16,8 @@
     - [@ohos.app.ability.ServiceExtensionAbility (ServiceExtensionAbility)](js-apis-app-ability-serviceExtensionAbility.md)
     - [@ohos.app.ability.StartOptions (StartOptions)](js-apis-app-ability-startOptions.md)
     - [@ohos.app.ability.UIAbility (UIAbility)](js-apis-app-ability-uiAbility.md)
+    - [@ohos.app.ability.UIExtensionAbility (Base Class for ExtensionAbilities with UI)](js-apis-app-ability-uiExtensionAbility.md)
+    - [@ohos.app.ability.UIExtensionContentSession (UI Operation Class for ExtensionAbilities with UI)](js-apis-app-ability-uiExtensionContentSession.md)
     - [@ohos.app.form.FormExtensionAbility (FormExtensionAbility)](js-apis-app-form-formExtensionAbility.md)
     - [@ohos.application.DataShareExtensionAbility (DataShareExtensionAbility)](js-apis-application-dataShareExtensionAbility.md)
     - [@ohos.application.StaticSubscriberExtensionAbility (StaticSubscriberExtensionAbility)](js-apis-application-staticSubscriberExtensionAbility.md)
@@ -106,6 +108,7 @@
       - [ProcessInformation](js-apis-inner-application-processInformation.md)
       - [ServiceExtensionContext](js-apis-inner-application-serviceExtensionContext.md)
       - [UIAbilityContext](js-apis-inner-application-uiAbilityContext.md)
+      - [UIExtensionContext](js-apis-inner-application-uiExtensionContext.md)
       - [shellCmdResult](js-apis-inner-application-shellCmdResult.md)
       - [WindowExtensionContext](js-apis-inner-application-windowExtensionContext.md)
     - wantAgent
@@ -205,12 +208,13 @@
   - [@ohos.curves (Interpolation Calculation)](js-apis-curve.md)
   - [@ohos.font (Custom Font Registration)](js-apis-font.md)
   - [@ohos.matrix4 (Matrix Transformation)](js-apis-matrix4.md)
+  - [@ohos.measure (Text Measurement)](js-apis-measure.md)
   - [@ohos.mediaquery (Media Query)](js-apis-mediaquery.md)
   - [@ohos.pluginComponent (PluginComponentManager)](js-apis-plugincomponent.md)
   - [@ohos.promptAction (Prompt)](js-apis-promptAction.md)
   - [@ohos.router (Page Routing)](js-apis-router.md)
-  - [@ohos.measure (Text Measurement)](js-apis-measure.md)
   - [@ohos.uiAppearance (UI Appearance)](js-apis-uiappearance.md)
+
 - Graphics
   - [@ohos.animation.windowAnimationManager (Window Animation Management)](js-apis-windowAnimationManager.md)
   - [@ohos.application.WindowExtensionAbility (WindowExtensionAbility)](js-apis-application-windowExtensionAbility.md)
@@ -225,12 +229,15 @@
     - [WebGL2](js-apis-webgl2.md)
 
 - Multimedia
+  - [@ohos.app.ability.MediaControlExtensionAbility (ExtensionAbility for Media Playback Control)](js-apis-app-ability-MediaControlExtensionAbility.md)
   - [@ohos.multimedia.audio (Audio Management)](js-apis-audio.md)
   - [@ohos.multimedia.avsession (AVSession Management)](js-apis-avsession.md)
   - [@ohos.multimedia.camera (Camera Management)](js-apis-camera.md)
   - [@ohos.multimedia.image (Image Processing)](js-apis-image.md)
   - [@ohos.multimedia.media (Media)](js-apis-media.md)
   - [@ohos.multimedia.systemSoundManager (System Sound Management)](js-apis-systemSoundManager.md)
+  - application
+    - [MediaControlExtensionContext (ExtensionAbility Context for Media Playback Control)](js-apis-inner-application-MediaControlExtensionContext.md)
   - multimedia
     - [ringtonePlayer (Ringtone Player)](js-apis-inner-multimedia-ringtonePlayer.md)
 

en/application-dev/reference/apis/js-apis-app-ability-MediaControlExtensionAbility.md

+# @ohos.app.ability.MediaControlExtensionAbility (ExtensionAbility for Media Playback Control)
+
+The **MediaControlExtensionAbility** module, inherited from [UIExtensionAbility](js-apis-app-ability-uiExtensionAbility.md), provides ExtensionAbilities for media playback control. No APIs are added. During actual development, you need to implement the APIs in the parent class to use the lifecycle and capabilities of UIExtensionAbilities. You cannot directly call the base class.
+
+**System capability**: SystemCapability.Multimedia.AVSession.Core
+
+> **NOTE**
+>
+> - The initial APIs of this module are supported since API version 10. Newly added APIs will be marked with a superscript to indicate their earliest API version.
+> - The APIs of this module can be used only in the stage model.
+> - The APIs provided by this module are system APIs.
+
+## Modules to Import
+
+```js
+import MediaControlExtensionAbility from @ohos.app.ability.MediaControlExtensionAbility;
+```

en/application-dev/reference/apis/js-apis-camera.md

@@ -32,7 +32,7 @@ Obtains a **CameraManager** instance. This API returns the result synchronously.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -267,7 +267,7 @@ Creates a **CameraInput** instance with the specified **CameraDevice** object. T
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -311,7 +311,7 @@ Creates a **CameraInput** instance with the specified camera position and type.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -355,7 +355,7 @@ Creates a **PreviewOutput** instance. This API returns the result synchronously.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -397,7 +397,7 @@ Creates a **PhotoOutput** instance. This API returns the result synchronously.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -439,7 +439,7 @@ Creates a **VideoOutput** instance. This API returns the result synchronously.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -480,7 +480,7 @@ Creates a **MetadataOutput** instance. This API returns the result synchronously
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -515,7 +515,7 @@ Creates a **CaptureSession** instance. This API returns the result synchronously
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -606,7 +606,7 @@ Checks whether a camera supports prelaunch. This API is called in prior to **set
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -640,7 +640,7 @@ setPrelaunchConfig(prelaunchConfig: PrelaunchConfig): void
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -706,7 +706,7 @@ Creates a deferred **PreviewOutput** instance and adds it to the data stream ins
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -868,7 +868,7 @@ Opens this camera. This API uses an asynchronous callback to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -904,7 +904,7 @@ Opens this camera. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -938,7 +938,7 @@ Closes this camera. This API uses an asynchronous callback to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -972,7 +972,7 @@ Closes this camera. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1096,7 +1096,7 @@ Starts configuration for the session.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1129,7 +1129,7 @@ Commits the configuration for this **CaptureSession** instance. This API uses an
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1164,7 +1164,7 @@ Commits the configuration for this **CaptureSession** instance. This API uses a
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1204,7 +1204,7 @@ Adds a [CameraInput](#camerainput) instance to the session.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1244,7 +1244,7 @@ Removes a [CameraInput](#camerainput) instance from the session.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1284,7 +1284,7 @@ Adds a [CameraOutput](#cameraoutput) instance to the session.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1324,7 +1324,7 @@ Removes a [CameraOutput](#cameraoutput) instance from the session.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1358,7 +1358,7 @@ Starts this **CaptureSession**. This API uses an asynchronous callback to return
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1393,7 +1393,7 @@ Starts this **CaptureSession**. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1426,7 +1426,7 @@ Stops this **CaptureSession**. This API uses an asynchronous callback to return
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1460,7 +1460,7 @@ Stops this **CaptureSession**. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1492,7 +1492,7 @@ Releases this **CaptureSession**. This API uses an asynchronous callback to retu
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1526,7 +1526,7 @@ Releases this **CaptureSession**. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1558,7 +1558,7 @@ Checks whether the device has flash. This API uses an asynchronous callback to r
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1597,7 +1597,7 @@ Checks whether a flash mode is supported.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1641,7 +1641,7 @@ Before the setting, do the following checks:
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1674,7 +1674,7 @@ Obtains the flash mode in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1713,7 +1713,7 @@ Checks whether an exposure mode is supported.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1746,7 +1746,7 @@ Obtains the exposure mode in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1785,7 +1785,7 @@ Sets an exposure mode for the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1818,7 +1818,7 @@ Obtains the metering point of the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1859,7 +1859,7 @@ The coordinate system is based on the horizontal device direction with the devic
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1893,7 +1893,7 @@ Obtains the exposure compensation values of the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1928,7 +1928,7 @@ Before the setting, you are advised to use **[getExposureBiasRange](#getexposure
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -1962,7 +1962,7 @@ Obtains the exposure value in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2001,7 +2001,7 @@ Checks whether a focus mode is supported.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2042,7 +2042,7 @@ Before the setting, use **[isFocusModeSupported](#isfocusmodesupported)** to che
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2075,7 +2075,7 @@ Obtains the focus mode in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2116,7 +2116,7 @@ The coordinate system is based on the horizontal device direction with the devic
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2150,7 +2150,7 @@ Obtains the focal point of the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2183,7 +2183,7 @@ Obtains the focal length of the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2216,7 +2216,7 @@ Obtains the supported zoom ratio range.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2255,7 +2255,7 @@ Sets a zoom ratio, with a maximum precision of two decimal places.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2289,7 +2289,7 @@ Obtains the zoom ratio in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2328,7 +2328,7 @@ Checks whether the specified video stabilization mode is supported.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2361,7 +2361,7 @@ Obtains the video stabilization mode in use.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2400,7 +2400,7 @@ Sets a video stabilization mode for the device.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2487,7 +2487,7 @@ Starts to output preview streams. This API uses an asynchronous callback to retu
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2521,7 +2521,7 @@ Starts to output preview streams. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2603,7 +2603,7 @@ Releases output resources. This API uses an asynchronous callback to return the
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2637,7 +2637,7 @@ Releases output resources. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2740,7 +2740,7 @@ Adds a surface for delayed preview. This API can run after **session.commitConfi
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2836,7 +2836,7 @@ Captures a photo with the default shooting parameters. This API uses an asynchro
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2871,7 +2871,7 @@ Captures a photo with the default shooting parameters. This API uses a promise t
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2905,7 +2905,7 @@ Captures a photo with the specified shooting parameters. This API uses an asynch
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -2958,7 +2958,7 @@ Captures a photo with the specified shooting parameters. This API uses a promise
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3023,7 +3023,7 @@ Releases output resources. This API uses an asynchronous callback to return the
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3057,7 +3057,7 @@ Releases output resources. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3187,7 +3187,7 @@ This API takes effect after **CaptureSession.addOutput** and **CaptureSession.ad
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3233,7 +3233,7 @@ This API takes effect after **CaptureSession.addOutput** and **CaptureSession.ad
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3356,7 +3356,7 @@ Starts video recording. This API uses an asynchronous callback to return the res
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3391,7 +3391,7 @@ Starts video recording. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3474,7 +3474,7 @@ Releases output resources. This API uses an asynchronous callback to return the
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3508,7 +3508,7 @@ Releases output resources. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3613,7 +3613,7 @@ Starts to output metadata. This API uses an asynchronous callback to return the
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |
@@ -3648,7 +3648,7 @@ Starts to output metadata. This API uses a promise to return the result.
 
 **Error codes**
 
-For details about the error codes, see [CameraErrorCode](#cameraerrorcode).
+For details about the error codes, see [Camera Error Codes](../errorcodes/errorcode-camera.md).
 
 | ID        | Error Message       |
 | --------------- | --------------- |

en/application-dev/reference/apis/js-apis-file-fs.md

@@ -2687,7 +2687,7 @@ Represents detailed file information. Before calling any API of the **Stat()** c
 | Name    | Type  | Readable  | Writable  | Description                                      |
 | ------ | ------ | ---- | ---- | ---------------------------------------- |                        
 | ino    | number | Yes   | No   | File ID. Different files on the same device have different **ino**s.|                 |
-| mode   | number | Yes   | No   | File permissions. The meaning of each bit is as follows:<br>- **0o400**: The owner has the read permission on a regular file or a directory entry.<br>- **0o200**: The owner has the permission to write a regular file or create and delete a directory entry.<br>- **0o100**: The owner has the permission to execute a regular file or search for the specified path in a directory.<br>- **0o040**: The user group has the read permission on a regular file or a directory entry.<br>- **0o020**: The user group has the permission to write a regular file or create and delete a directory entry.<br>- **0o010**: The user group has the permission to execute a regular file or search for the specified path in a directory.<br>- **0o004**: Other users have the permission to read a regular file or read a directory entry.<br>- **0o002**: Other users have the permission to write a regular file or create and delete a directory entry.<br>- **0o001**: Other users have the permission to execute a regular file or search for the specified path in a directory.|
+| mode   | number | Yes   | No   | File permissions. The meaning of each bit is as follows:<br>**NOTE**<br>The following values are in octal format. The returned values are in decimal format. You need to convert the values.<br>- **0o400**: The owner has the permission to read a regular file or a directory entry.<br>- **0o200**: The owner has the permission to write a regular file or create and delete a directory entry.<br>- **0o100**: The owner has the permission to execute a regular file or search for the specified path in a directory.<br>- **0o040**: The user group has the permission to read a regular file or a directory entry.<br>- **0o020**: The user group has the permission to write a regular file or create and delete a directory entry.<br>- **0o010**: The user group has the permission to execute a regular file or search for the specified path in a directory.<br>- **0o004**: Other users have the permission to read a regular file or a directory entry.<br>- **0o002**: Other users have the permission to write a regular file or create and delete a directory entry.<br>- **0o001**: Other users have the permission to execute a regular file or search for the specified path in a directory.|
 | uid    | number | Yes   | No   | ID of the file owner.|
 | gid    | number | Yes   | No   | ID of the user group of the file.|
 | size   | number | Yes   | No   | File size, in bytes. This parameter is valid only for regular files. |

en/application-dev/reference/apis/js-apis-inner-ability-want.md

@@ -26,7 +26,7 @@ import Want from '@ohos.app.ability.Want';
 | flags        | number               | No  | How the **Want** object will be handled. By default, numbers are passed in. For details, see [flags](js-apis-ability-wantConstant.md#wantconstantflags).|
 | action      | string               | No  | Action to take, such as viewing and sharing application details. In implicit Want, you can define this field and use it together with **uri** or **parameters** to specify the operation to be performed on the data. For details, see [action](js-apis-ability-wantConstant.md#wantconstantaction). For details about the definition and matching rules of implicit Want, see [Matching Rules of Explicit Want and Implicit Want](../../application-models/explicit-implicit-want-mappings.md).                          |
 | parameters   | {[key: string]: Object} | No  | Want parameters in the form of custom key-value (KV) pairs. By default, the following keys are carried:<br>- **ohos.aafwk.callerPid**: PID of the caller.<br>- **ohos.aafwk.param.callerToken**: token of the caller.<br>- **ohos.aafwk.param.callerUid**: UID in [bundleInfo](js-apis-bundle-BundleInfo.md#bundleinfo), that is, the application UID in the bundle information.<br>- **component.startup.newRules**: whether to enable the new control rule.<br>- **moduleName**: module name of the caller. No matter what this field is set to, the correct module name will be sent to the peer.<br>- **ohos.dlp.params.sandbox**: available only for DLP files.                                      |
-| entities    | Array\<string>       | No  | Additional category information (such as browser and video player) of the target ability. It is a supplement to **action** in implicit Want and is used to filter ability types. For details, see [entity](js-apis-app-ability-wantConstant.md#wantconstantentity).                                   |
+| entities    | Array\<string>       | No  | Additional category information (such as browser and video player) of the target ability. It is a supplement to **action** in implicit Want and is used to filter ability types.                                   |
 | moduleName<sup>10+</sup> | string | No   | Module to which the ability belongs.|
 
 **Example**

en/application-dev/reference/apis/js-apis-inner-application-MediaControlExtensionContext.md

+# MediaControlExtensionContext (ExtensionAbility Context for Media Playback Control)
+
+**MediaControlExtensionContext**, inherited from [UIExtensionContext](js-apis-inner-application-uiExtensionContext.md), provides the context environment for [MediaControlExtensionAbility](js-apis-app-ability-MediaControlExtensionAbility.md). It provides MediaControlExtensionAbility-related configuration and APIs for operating the MediaControlExtensionAbility. For example, you can use the APIs to start a MediaControlExtensionAbility.
+
+**System capability**: SystemCapability.Multimedia.AVSession.Core
+
+> **NOTE**
+>
+> - The initial APIs of this module are supported since API version 10. Newly added APIs will be marked with a superscript to indicate their earliest API version.
+> - The APIs of this module can be used only in the stage model.
+> - The APIs provided by this module are system APIs.

en/application-dev/reference/apis/js-apis-request.md

@@ -286,6 +286,10 @@ on(type: 'progress', callback:(uploadedSize: number, totalSize: number) => vo
 
 Subscribes to upload progress events. This API uses a callback to return the result synchronously.
 
+> **NOTE**
+>
+> To maintain a balance between power consumption and performance, this API cannot be called when the application is running in the background.
+
 **Required permissions**: ohos.permission.INTERNET
 
 **System capability**: SystemCapability.MiscServices.Upload
@@ -863,6 +867,10 @@ on(type: 'progress', callback:(receivedSize: number, totalSize: number) => vo
 
 Subscribes to download progress events. This API uses a callback to return the result synchronously.
 
+> **NOTE**
+>
+> To maintain a balance between power consumption and performance, this API cannot be called when the application is running in the background.
+
 **Required permissions**: ohos.permission.INTERNET
 
 **System capability**: SystemCapability.MiscServices.Download

en/application-dev/reference/arkui-ts/ts-container-columnsplit.md

 # ColumnSplit
 
-The **\<ColumnSplit>** component lays out child components vertically and inserts a horizontal divider between components.
+The **\<ColumnSplit>** component lays out child components vertically and inserts a horizontal divider between every two child components.
 
 >  **NOTE**
 >
 > This component is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
-
-
 ## Child Components
 
 Supported
 
-
 ## APIs
 
 ColumnSplit()
@@ -20,17 +17,24 @@ ColumnSplit()
 
 ## Attributes
 
-| Name| Type| Description|
-| -------- | -------- | -------- |
+| Name                  | Type                                                             | Description                            |
+|-----------------------|-------------------------------------------------------------------|---------------------------------|
 | resizeable            | boolean                                                           | Whether the divider can be dragged.<br/>Default value: **false**  |
+| divider<sup>10+</sup> | [ColumnSplitDividerStyle](#columnsplitdividerstyle10) \| null | Margin of the divider.<br>- **DividerStyle**: distance between the divider and the child component above or below it.<br>- Default value: **null**, indicating that the top and bottom margins of the divider are 0.|
+
+## ColumnSplitDividerStyle<sup>10+</sup>
+
+| Name       | Type     | Mandatory| Description                      |
+| ----------- | ------------- | ---- |--------------------------|
+| startMargin | [Dimension](ts-types.md#dimension10)       | No  | Distance between the divider and the child component above it.<br>Default value: **0**|
+| endMargin   | [Dimension](ts-types.md#dimension10)       | No  | Distance between the divider and the child component below it.<br>Default value: **0**|
 
 >  **NOTE**
 >
-> Similar to **\<RowSplit>**, the divider of **\<ColumnSplit>** can be dragged to a position that just fully holds a component.
->
-> Dragging is not supported in the Previewer. Check the drag effect on a real device.
+> Similar to **\<RowSplit>**, the divider of **\<ColumnSplit>** can change the height of the upper and lower child components, but only to the extent that the resultant height falls within the maximum and minimum heights of the child components.
 >
-> The universal attributes **clip** and **margin** are not supported.
+> Universal attributes such as **clip** and **margin** are supported. If **clip** is not set, the default value **true** is used.
+
 
 ## Example
 

en/application-dev/reference/arkui-ts/ts-container-rowsplit.md

 # RowSplit
 
-The **\<RowSplit>** lays out child components horizontally and inserts a vertical divider between child components.
+The **\<RowSplit>** lays out child components horizontally and inserts a vertical divider between every two child components.
 
 >  **NOTE**
 >
@@ -19,15 +19,13 @@ RowSplit()
 
 | Name| Type| Description|
 | -------- | -------- | -------- |
-| resizeable | boolean | Whether the divider can be dragged.<br>Default value: **false** |
+| resizeable | boolean | Whether the divider can be dragged.<br/>Default value: **false** |
 
 >  **NOTE**
 >
-> Similar to **\<RowSplit>**, the divider of **\<RowSplit>** can be dragged to a position that just fully holds a component.
+> The divider of **\<RowSplit>** can change the width of the left and right child components, but only to the extent that the resultant width falls within the maximum and minimum widths of the child components.
 >
-> Dragging is not supported in the Previewer. Check the drag effect on a real device.
->
-> The universal attributes **clip** and **margin** are not supported.
+> Universal attributes such as **clip** and **margin** are supported. If **clip** is not set, the default value **true** is used.
 
 
 ## Example
@@ -54,4 +52,4 @@ struct RowSplitExample {
 }
 ```
 
-![en-us_image_0000001212058482](figures/en-us_image_0000001212058482.gif)
+![en-us_image_0000001219982729](figures/en-us_image_0000001219982729.gif)

en/application-dev/reference/errorcodes/Readme-EN.md

@@ -24,7 +24,8 @@
   - [Audio Error Codes](errorcode-audio.md)
   - [Media Error Codes](errorcode-media.md)
   - [AVSession Management Error Codes](errorcode-avsession.md)
-- Resource Manager
+  - [Camera Error Codes](errorcode-camera.md)
+- Resource Management
   - [I18N Error Codes](errorcode-i18n.md)
   - [Resource Manager Error Codes](errorcode-resource-manager.md)
 - Background Task
@@ -55,6 +56,7 @@
   - [Network Connection Management Error Codes](errorcode-net-connection.md)
   - [Ethernet Connection Error Codes](errorcode-net-ethernet.md)
   - [Network Sharing Error Codes](errorcode-net-sharing.md)
+  - [Policy Management Error Codes](errorcode-net-policy.md)
   - [mDNS Error Codes](errorcode-net-mdns.md)
   - [Traffic Management Error Codes](errorcode-net-statistics.md)
 - Connectivity
@@ -86,7 +88,7 @@
   - [Device Management Error Codes](errorcode-device-manager.md)
   - [Location Subsystem Error Codes](errorcode-geoLocationManager.md)
   - [Screen Hopping Error Codes](errorcode-devicestatus.md)
-  - [Screen Hopping Error Codes (to Be Deprecated)](errorcode-multimodalinput.md)
+  - [Screen Hopping Error Codes (To Be Deprecated Soon)](errorcode-multimodalinput.md)
   - [Sensor Error Codes](errorcode-sensor.md)
   - [Vibrator Error Codes](errorcode-vibrator.md)
   - [System Parameter Error Codes](errorcode-system-parameterV9.md)
@@ -94,7 +96,7 @@
   - [Update Error Codes](errorcode-update.md)
 - Customization
   - [Enterprise Device Management Error Codes](errorcode-enterpriseDeviceManager.md)
-- Common Library Library
+- Common Library
   - [Common Library Error Codes](errorcode-utils.md)
 - Test
   - [UiTest Error Codes](errorcode-uitest.md)

en/application-dev/reference/errorcodes/errorcode-ability.md

@@ -76,7 +76,7 @@ Visibility verification fails.
 
 **Solution**
 
-Check whether the application meets the visibility restriction of the started application.
+Check whether **exported** under the **Ability** field in the **module.json5** file of the application is set to **true**. If this parameter is set to **true**, the ability can be invoked by other applications. If this parameter is set to **false**, the ability cannot be invoked by other applications.
 
 ## 16000006 Cross-User Operation Is Not Allowed
 

en/application-dev/reference/errorcodes/errorcode-camera.md

+# Camera Error Codes
+
+> **NOTE**
+>
+> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](errorcode-universal.md).
+
+## 7400101 Invalid Parameter
+
+**Error Message**
+
+Parameter missing or parameter type incorrect.
+
+**Error Description**
+
+A parameter passed in the API is invalid.
+
+**Possible Cause**
+
+The parameter is invalid. For example, the parameter value is not within the range supported.
+
+**Solution**
+
+Pass the correct parameters in the API.
+
+## 7400102 Invalid Operation
+
+**Error Message**
+
+Operation not allowed.
+
+**Error Description**
+
+The operation is not performed in the specified mode.
+
+**Possible Cause**
+
+The API execution sequence is incorrect. For example, the **commitConfig** API is called in prior to **beginConfig**.
+
+**Solution**
+
+Perform operations according to the API reference and guide.
+
+## 7400103 Session Not Configured
+
+**Error Message**
+
+Session not config.
+
+**Error Description**
+
+An operation that requires session configuration is performed before the session is configured.
+
+**Possible Cause**
+
+For example, the **start()** API is called before the session is configured.
+
+**Solution**
+
+Configure the session first.
+
+## 7400104 Session Not Running
+
+**Error Message**
+
+Session not running.
+
+**Error Description**
+
+An operation that requires a running session is performed before the session runs.
+
+**Possible Cause**
+
+For example, the **capture()** API is called before the session runs.
+
+**Solution**
+
+Perform the operation to run the session first.
+
+## 7400105 Session Configuration Locked
+
+**Error Message**
+
+Session config locked.
+
+**Error Description**
+
+The session configuration is locked.
+
+**Possible Cause**
+
+Another thread has locked the session configuration.
+
+**Solution**
+
+Wait until the session configuration is unlocked.
+
+## 7400106 Device Configuration Locked
+
+**Error Message**
+
+Device setting locked.
+
+**Error Description**
+
+The device configuration is locked.
+
+**Possible Cause**
+
+Another thread has locked the device configuration.
+
+**Solution**
+
+Wait until the device configuration is unlocked.
+
+## 7400107 Camera Conflict
+
+**Error Message**
+
+Can not use camera cause of conflict.
+
+**Error Description**
+
+The camera cannot be used due to a conflict.
+
+**Possible Cause**
+
+The opened camera conflicts with the local camera to be used.
+
+**Solution**
+
+Wait until the conflicting camera is released.
+
+## 7400108 Camera Disabled Due to Security Reasons
+
+**Error Message**
+
+Camera disabled cause of security reason.
+
+**Error Description**
+
+The camera cannot be used due to security policies.
+
+**Possible Cause**
+
+The application running in the background attempts to open the camera.
+
+**Solution**
+
+Switch the application to the foreground first.
+
+## 7400109 Camera Preempted
+
+**Error Message**
+
+Can not use camera cause of preempted.
+
+**Error Description**
+
+The camera cannot be used because it is preempted.
+
+**Possible Cause**
+
+Two applications attempt to open the same camera simultaneously.
+
+**Solution**
+
+N/A
+
+## 7400201 Camera Service Error
+
+**Error Message**
+
+Camera service fatal error.
+
+**Error Description**
+
+The camera service is abnormal.
+
+**Possible Cause**
+
+For example, the camera service is restarted or cross-process invoking is abnormal.
+
+**Solution**
+
+Create the service again.

en/application-dev/reference/errorcodes/errorcode-universal.md

@@ -44,7 +44,7 @@ BusinessError 401: Parameter error. The type of "${parameterName}" must be ${val
 
 **Description**
 
-This error code is reported when a parameter error occurs.
+This error code is reported when a parameter error occurs. Regardless of whether the API is synchronous or asynchronous, this type of error is generally thrown in synchronous mode.
 
 **Possible Causes**
 

en/application-dev/reference/syscap.md

@@ -110,11 +110,11 @@ You can use either the ArtTS or native API to determine whether an API is availa
   - Method 2: Import a module using the **import** API. If the current device does not support the module, the import result is **undefined**. Before using an API, you must make sure the API is available.
 
 	```ts
-	import geolocation from '@ohos.geolocation';
+	import geolocationManager from '@ohos.geoLocationManager';
 
-	if (geolocation) {
-	geolocation.getCurrentLocation((location) => {
-		console.log(location.latitude, location.longitude);
+	if (geolocationManager) {
+	geolocationManager.getCurrentLocation((location) => {
+		console.log('current location: ' + JSON.stringify(location));
 	});
 	} else {
 	console.log('This device does not support location information.');

en/application-dev/task-management/background-task-overview.md

@@ -13,6 +13,10 @@ When you return to the home screen, lock the screen, or switch to another applic
 
 To ensure the normal use of features such as music playback and calendar reminders in the background, the system provides constrained background tasks to extend the running time of applications in the background.
 
+## Resource Usage Constraints
+
+The system provides resource quotas for running processes, including the memory usage and CPU usage in a continuous period of time, as well as disk write I/O volume in 24 hours. When the quota is reached, the system generates a warning-level log if the process is running in the foreground, and terminates the process if it is running in the background.
+
 ## Background Task Types
 
 For standard-system devices, OpenHarmony provides the following types of constrained background tasks: transient tasks, continuous tasks, deferred tasks, agent-powered reminders, and efficiency resources.
@@ -29,12 +33,13 @@ You can select a proper background task type to ensure that your application can
 
 For system applications that provide basic capabilities, the system provides an API for [requesting energy resources](efficiency-resource-request.md). After an application calls the API, the system exempts the application from management.
 
-  **Figure 1** Selecting a type of background task 
+**Figure 1** Selecting a type of background task
+
 ![bgtask_choice](figures/bgtask_choice.png)
 
 
 > **NOTE**
 >
-> 1. The system supports only constrained background tasks. If an application does not use a constrained background task or selects an inappropriate type of background task after switching to the background, its process will be suspended or terminated.
+> - The system supports only constrained background tasks. If an application does not use a constrained background task or selects an inappropriate type of background task after switching to the background, its process will be suspended or terminated.
 > 
-> 2. For an application that requests a constrained background task, only the priority of reclaiming the application process is increased. If system resources are severely insufficient, the application process may still be terminated.
+> - For an application that requests a constrained background task, only the priority of reclaiming the application process is increased. If system resources are severely insufficient, the application process may still be terminated.

en/application-dev/task-management/efficiency-resource-request.md

@@ -40,6 +40,7 @@ The table below lists the main APIs used for efficient resources. For details ab
 | reason | string | Yes| Reason for requesting the resource.|
 
 **Table 3** Efficiency resource types
+
 | Name| Value| Description|
 | -------- | -------- | -------- |
 | CPU | 1 | CPU resource. Such type of resource prevents an application from being suspended.|
@@ -49,7 +50,8 @@ The table below lists the main APIs used for efficient resources. For details ab
 | BLUETOOTH | 16 | Bluetooth resource. Such type of resource ensures that an application in the suspended state can be woken up by Bluetooth-related events.|
 | GPS | 32 | GPS resource. Such type of resource ensures that an application in the suspended state can be woken up by GPS-related events.|
 | AUDIO | 64 | Audio resource. Such type of resource prevents an application from being suspended when the application has an audio being played.|
-
+| RUNNING_LOCK<sup>10+</sup> | 128 | RUNNING_LOCK resource. Such type of resources prevents locks running in the background from being temporarily released when the application is suspended.|
+| SENSOR<sup>10+</sup> | 256 | Sensor resource. Such type of resources prevents sensor callbacks from being intercepted.|
 
 ## How to Develop
 

en/application-dev/website.md

@@ -144,9 +144,10 @@
         - [Component Startup Rules (Stage Model)](application-models/component-startup-rules.md)
         - Inter-Device Application Component Interaction (Continuation)
           - [Continuation Overview](application-models/inter-device-interaction-hop-overview.md)
-          - [Cross-Device Migration (for System Applications Only)](application-models/hop-cross-device-migration.md)
+          - [Cross-Device Migration](application-models/hop-cross-device-migration.md)
           - [Multi-device Collaboration (for System Applications Only)](application-models/hop-multi-device-collaboration.md)
         - [Subscribing to System Environment Variable Changes](application-models/subscribe-system-environment-variable-changes.md)
+        - [Setting Atomic Services to Support Sharing](application-models/atomic-services-support-sharing.md)
       - Process Model
         - [Process Model Overview](application-models/process-model-stage.md)
         - Common Events
@@ -478,6 +479,7 @@
         - [Developing Audio Call](media/audio-call-development.md)
       - [Video Playback](media/video-playback.md)
       - [Video Recording](media/video-recording.md)
+      - [Screen Capture](media/avscreen-capture.md)
       - Audio and Video Codecs
         - [Obtaining Supported Codecs](media/obtain-supported-codecs.md)
         - [Audio Encoding](media/audio-encoding.md)
@@ -544,9 +546,9 @@
       - [hapsigner Guide](security/hapsigntool-guidelines.md)
       - [HarmonyAppProvision Configuration File](security/app-provision-structure.md)
   - AI
-    - [AI Development](./ai/ai-overview.md)
-    - [Using MindSpore Lite JavaScript APIs to Develop AI Applications](./ai/mindspore-guidelines-based-js.md)
-    - [Using MindSpore Lite Native APIs to Develop AI Applications](./ai/mindspore-guidelines-based-native.md)
+    - [AI Development](ai/ai-overview.md)
+    - [Using MindSpore Lite JavaScript APIs to Develop AI Applications](ai/mindspore-guidelines-based-js.md)
+    - [Using MindSpore Lite Native APIs to Develop AI Applications](ai/mindspore-guidelines-based-native.md)
   - Connectivity
     - Network Management
       - [Network Management Overview](connectivity/net-mgmt-overview.md)
@@ -680,6 +682,7 @@
   - Native APIs
     - [Using Native APIs in Application Projects](napi/napi-guidelines.md)
     - Graphics
+      - [XComponent Development](napi/xcomponent-guidelines.md)
       - [Drawing Development](napi/drawing-guidelines.md)
       - [NativeBuffer Development](napi/native-buffer-guidelines.md)
       - [NativeImage Development](napi/native-image-guidelines.md)
@@ -730,6 +733,8 @@
         - [@ohos.app.ability.ServiceExtensionAbility (ServiceExtensionAbility)](reference/apis/js-apis-app-ability-serviceExtensionAbility.md)
         - [@ohos.app.ability.StartOptions (StartOptions)](reference/apis/js-apis-app-ability-startOptions.md)
         - [@ohos.app.ability.UIAbility (UIAbility)](reference/apis/js-apis-app-ability-uiAbility.md)
+        - [@ohos.app.ability.UIExtensionAbility (Base Class for ExtensionAbilities with UI)](reference/apis/js-apis-app-ability-uiExtensionAbility.md)
+        - [@ohos.app.ability.UIExtensionContentSession (UI Operation Class for ExtensionAbilities with UI)](reference/apis/js-apis-app-ability-uiExtensionContentSession.md)
         - [@ohos.app.form.FormExtensionAbility (FormExtensionAbility)](reference/apis/js-apis-app-form-formExtensionAbility.md)
         - [@ohos.application.DataShareExtensionAbility (DataShareExtensionAbility)](reference/apis/js-apis-application-dataShareExtensionAbility.md)
         - [@ohos.application.StaticSubscriberExtensionAbility (StaticSubscriberExtensionAbility)](reference/apis/js-apis-application-staticSubscriberExtensionAbility.md)
@@ -820,6 +825,7 @@
           - [ProcessInformation](reference/apis/js-apis-inner-application-processInformation.md)
           - [ServiceExtensionContext](reference/apis/js-apis-inner-application-serviceExtensionContext.md)
           - [UIAbilityContext](reference/apis/js-apis-inner-application-uiAbilityContext.md)
+          - [UIExtensionContext](reference/apis/js-apis-inner-application-uiExtensionContext.md)
           - [shellCmdResult](reference/apis/js-apis-inner-application-shellCmdResult.md)
           - [WindowExtensionContext](reference/apis/js-apis-inner-application-windowExtensionContext.md)
         - wantAgent
@@ -935,12 +941,15 @@
         - [WebGL](reference/apis/js-apis-webgl.md)
         - [WebGL2](reference/apis/js-apis-webgl2.md)
     - Multimedia
+      - [@ohos.app.ability.MediaControlExtensionAbility (ExtensionAbility for Media Playback Control)](reference/apis/js-apis-app-ability-MediaControlExtensionAbility.md)
       - [@ohos.multimedia.audio (Audio Management)](reference/apis/js-apis-audio.md)
       - [@ohos.multimedia.avsession (AVSession Management)](reference/apis/js-apis-avsession.md)
       - [@ohos.multimedia.camera (Camera Management)](reference/apis/js-apis-camera.md)
       - [@ohos.multimedia.image (Image Processing)](reference/apis/js-apis-image.md)
       - [@ohos.multimedia.media (Media)](reference/apis/js-apis-media.md)
       - [@ohos.multimedia.systemSoundManager (System Sound Management)](reference/apis/js-apis-systemSoundManager.md)
+      - application
+        - [MediaControlExtensionContext (ExtensionAbility Context for Media Playback Control)](reference/apis/js-apis-inner-application-MediaControlExtensionContext.md)
       - multimedia
         - [ringtonePlayer (Ringtone Player)](reference/apis/js-apis-inner-multimedia-ringtonePlayer.md)
     - Resource Management
@@ -1336,6 +1345,7 @@
       - [GridRow](reference/arkui-ts/ts-container-gridrow.md)
       - [Grid](reference/arkui-ts/ts-container-grid.md)
       - [GridItem](reference/arkui-ts/ts-container-griditem.md)
+      - [Hyperlink](reference/arkui-ts/ts-container-hyperlink.md)
       - [List](reference/arkui-ts/ts-container-list.md)
       - [ListItem](reference/arkui-ts/ts-container-listitem.md)
       - [ListItemGroup](reference/arkui-ts/ts-container-listitemgroup.md)
@@ -1351,6 +1361,7 @@
       - [Swiper](reference/arkui-ts/ts-container-swiper.md)
       - [Tabs](reference/arkui-ts/ts-container-tabs.md)
       - [TabContent](reference/arkui-ts/ts-container-tabcontent.md)
+      - [UIExtensionComponent](reference/arkui-ts/ts-container-ui-extension-component.md)
       - [WaterFlow](reference/arkui-ts/ts-container-waterflow.md)
     - Media Components
       - [Video](reference/arkui-ts/ts-media-components-video.md)
@@ -1603,6 +1614,7 @@
       - [Audio Error Codes](reference/errorcodes/errorcode-audio.md)
       - [Media Error Codes](reference/errorcodes/errorcode-media.md)
       - [AVSession Management Error Codes](reference/errorcodes/errorcode-avsession.md)
+      - [Camera Error Codes](reference/errorcodes/errorcode-camera.md)
     - Resource Management
       - [I18N Error Codes](reference/errorcodes/errorcode-i18n.md)
       - [Resource Manager Error Codes](reference/errorcodes/errorcode-resource-manager.md)
@@ -1622,7 +1634,7 @@
       - [DataShare Error Codes](reference/errorcodes/errorcode-datashare.md)
       - [Distributed Data Object Error Codes](reference/errorcodes/errorcode-distributed-dataObject.md)
       - [Distributed KV Store Error Codes](reference/errorcodes/errorcode-distributedKVStore.md)
-      - [Preferences Error Codes](reference/errorcodes/errorcode-preferences.md)
+      - [User Preference Error Codes](reference/errorcodes/errorcode-preferences.md)
     - File Management
       - [File Management Error Codes](reference/errorcodes/errorcode-filemanagement.md)
     - Telephony Service
@@ -1656,7 +1668,7 @@
       - [Time and Time Zone Service Error Codes](reference/errorcodes/errorcode-time.md)
       - [Webview Error Codes](reference/errorcodes/errorcode-webview.md)
     - Account Management
-      - [Account Error Codes](reference/errorcodes/errorcode-account.md)
+      - [Account Management Error Codes](reference/errorcodes/errorcode-account.md)
     - Device Management
       - [Power Consumption Statistics Error Codes](reference/errorcodes/errorcode-batteryStatistics.md)
       - [Brightness Error Codes](reference/errorcodes/errorcode-brightness.md)

en/contribute/template/js-template.md

@@ -9,13 +9,13 @@
 |      | Item                           | Writing Instruction                                                        |
 | ---- | --------------------------------- | ------------------------------------------------------------ |
 | 1    | Customer-oriented mindset               | **Stand in the shoes of developers and provide the use cases, parameter selection principles, recommendations/tips, sample code, and anything else that a developer will need to develop the API.**|
-| 2    | Upload path                         | Upload markdown files to **docs/en/application-dev/reference/apis**.<br>Upload images to **docs/en/application-dev/reference/apis/figures**. In addition, reference the image path in the markdown file as follows: **![](figures/exampleImage.jpg)**, **![](figures/exampleImage.png)**, or **![](figures/exampleImage.gif)**.|
+| 2    | Upload path                         | Upload markdown files to **docs/en/application-dev/reference/apis**.<br>Upload images to **docs/en/application-dev/reference/apis/figures**. In addition, reference the image path in the markdown file as follows: **\![]\(figures/exampleImage.jpg)**, **\![]\(figures/exampleImage.png)**, or **\![]\(figures/exampleImage.gif)**.|
 | 3    | File name                         | Provide one JS API reference document for each d.ts file. Name the file in the format of **js-apis-exampleModule.md**, where **exampleModule** is a variable and must be the same as the actual module name.<br>Examples:<br>For @ohos.multimedia.audio in the Multimedia subsystem, the JS API file name is **js-apis-audio.md**.<br>For @ohos.telephony.sms in the Telephony subsystem, the JS API file name is **js-apis-sms.md**.|
 | 4    | Directory update                         | After uploading an API reference document, update the **Readme-EN.md** file in **docs/en/application-dev/reference/apis**.<br>The directories are automatically arranged in alphabetical order.|
 | 5    | Document structure                         | - Module description<br>- Initial version description<br>- Modules to Import/Usage description<br>- API description (attributes, constants, methods, enums, and custom types)<br>  The order in which APIs are described in the document must be consistent with that in which they appear in the code. If some APIs have a logical sequence, pay attention to their sequence in the API reference document.|
 | 6    | Initial version description                     | 1. Use the greater-than sign (**>**) followed by a space to indent the description about the initial version of the module. Unless otherwise marked, all APIs in the module have the same initial version.<br>2. When introducing an API to an existing module, use the **<sup>** tag to mark its earliest version. The format is **<sup>versionNumber+</sup>**, for example, **<sup>7+</sup>**.<br>If an attribute is added to an existing module, suffix the **<sup>** tag to the new attribute name, for example, **newAttribute<sup>7+</sup>**.<br>If a method is added to an existing module, suffix the **<sup>** tag to the method name, for example, **sim.getSimIccId<sup>7+</sup>**. The same rule applies to new interfaces, classes, and enums.|
 | 7    | Deprecated API description                     | Do not delete the deprecated content from the document. Instead, suffix **deprecated** as a superscript to the content, and use the greater-than sign (**>**) to introduce the initial version and deprecated version.<br>Example: abandonmentMethod<sup>(deprecated)</sup><br>> This API is supported since API version 4 and deprecated since API version 7. You are advised to use [newMethod]\(#newmethod) instead.|
-| 8    | Permission description                         | Provide the same permission description as that defined in the code for each method, enum, and attribute.<br> 1. If only one permission is required for using the API, use the following format:<br>**Required permissions**: ohos.permission.examplePermission<br>2. If multiple permissions are required for using the API, provide the permissions with **and** or **or** in the following format:<br>**Required permissions**: ohos.permission.examplePermissionA and ohos.permission.examplePermissionB<br>    **Required permissions**: ohos.permission.examplePermissionA or ohos.permission.examplePermissionB |
+| 8    | Permission description                         | Provide the same permission description as that defined in the code for each method, enum, and attribute.<br> 1. If only one permission is required for using the API, use the following format:<br>**Required permissions**: ohos.permission.examplePermission<br>2. If multiple permissions are required for using the API, provide the permissions with **and** or **or** in the following format:<br>**Required permissions**: ohos.permission.examplePermissionA and ohos.permission.examplePermissionB<br>    **Required permissions**: ohos.permission.examplePermissionA or ohos.permission.examplePermissionB|
 | 9   | @syscap                           | 1. Provide a description for every API in the following format, wherein *A.B* indicates a specific system capability.<br>    **System capability**: SystemCapability.*A.B*<br>2. There are two cases for adding system capability information to a table (of attributes, enums, constants, or variables).<br>    1) If all the items in a table require the same system capability, add the following information to the front of the table:<br>          **System capability**: SystemCapability.*A.B*<br>    2) If the items in a table require different system capabilities, list the system capability for each item in the table.|
 | 10   | @system api                       | 1. If all APIs of the module are system APIs, add the following sentence to the next line of the initial version description:<br>The APIs provided by this module are system APIs.<br>2. If an API is a system API that can be used only by original equipment manufacturers (OEMs), add the following sentence to the API description:<br>**System API**: This is a system API.|
 | 11   | @FAModelOnly<br>@StageModelOnly  | 1. If a module is implemented only for a specific ability model, add the following sentence to the next line of the initial version description:<br>The APIs of this module can be used only in the FA model.<br>Or<br>The APIs of this module can be used only in the stage model.<br>2. If an API is implemented only for a specific ability model, add the following sentence to the API description:<br>**Model restriction**: This API can be used only in the FA model.<br/>Or<br/>**Model restriction**: This API can be used only in the stage model.|

en/contribute/template/ts-template.md

@@ -9,14 +9,14 @@
 |      | Item        | Writing Instruction                                      |
 | ---- | ----------- | ---------------------------------------- |
 | 1    | Customer-oriented mindset  | **Stand in the shoes of developers and provide the use cases, parameter selection principles, recommendations/tips, sample code, and anything else that a developer will need to develop the component.**|
-| 2   | Upload path       | Upload markdown files to `docs/en/application-dev/reference/arkui-ts`.<br>Upload images to `docs/en/application-dev/reference/arkui-ts/figures`. In addition, reference the image path in the markdown file as follows: `![](figures/exampleImage.jpg)`, `![](figures/exampleImage.png)`, or `![](figures/exampleImage.gif)`.|
-| 3    | File name       | Provide one TS component reference document for each .d.ts file. Name the file in the format of `ts-componentClassName-componentName.md`.<br>Examples:<br>For the basic component **\<text>**, the reference file name is `ts-basic-component-text.md`.<br>For the container component **\<list>**, the reference file name is `js-container-component-list.md`. |
-| 4    | Directory update       | After uploading a TS component reference document, update the `Readme-EN.md` file in `docs/en/application-dev/reference/arkui-ts`. |
-| 5    | Document structure       | - Component description<br>- Initial version description<br>- Modules to import/Usage description<br>- Permission description<br>- APIs, attributes, events, objects, enums, and custom types<br>The order in which APIs are described in the document must be consistent with that in which they appear in the code. If some APIs have a logical sequence, pay attention to their sequence in the document. |
-| 6    | Initial version description     | 1. Use the greater-than sign (`>`) followed by a space to indent the description about the initial version of the component. Unless otherwise marked, all APIs in the component have the same initial version.<br>2. When introducing an API to an existing component, use the `<sup>` tag to mark its initial version. The format is `<sup>versionNumber+</sup>`, for example, `<sup>7+</sup>`.<br>When introducing an attribute to an existing API, use the `<sup>` tag to mark its initial version. The format is `newAttribute<sup>versionNumber+</sup>`, for example, `newAttribute<sup>7+</sup>`. |
+| 2    | Upload path       | Upload markdown files to `docs/en/application-dev/reference/arkui-ts`.<br>Upload images to **docs/en/application-dev/reference/arkui-ts/figures**. In addition, reference the image path in the markdown file as follows: **\![]\(figures/exampleImage.jpg)**, **\![]\(figures/exampleImage.png)**, or **\![]\(figures/exampleImage.gif)**.|
+| 3    | File name       | Provide one TS component reference document for each .d.ts file. Name the file in the format of `ts-componentClassName-componentName.md`.<br>Examples:<br>For the basic component **\<text>**, the reference file name is `ts-basic-component-text.md`.<br>For the container component **\<list>**, the reference file name is `js-container-component-list.md`.|
+| 4    | Directory update       | After uploading a TS component reference document, update the `Readme-EN.md` file in `docs/en/application-dev/reference/arkui-ts`.|
+| 5    | Document structure       | - Component description<br>- Initial version description<br>- Modules to import/Usage description<br>- Permission description<br>- APIs, attributes, events, objects, enums, and custom types<br>The order in which APIs are described in the document must be consistent with that in which they appear in the code. If some APIs have a logical sequence, pay attention to their sequence in the document.|
+| 6    | Initial version description     | 1. Use the greater-than sign (`>`) followed by a space to indent the description about the initial version of the component. Unless otherwise marked, all APIs in the component have the same initial version.<br>2. When introducing an API to an existing component, use the `<sup>` tag to mark its initial version. The format is `<sup>versionNumber+</sup>`, for example, `<sup>7+</sup>`.<br>When introducing an attribute to an existing API, use the `<sup>` tag to mark its initial version. The format is `newAttribute<sup>versionNumber+</sup>`, for example, `newAttribute<sup>7+</sup>`.|
 | 7    | Deprecated API description     | Do not delete the deprecated content from the document. Instead, suffix `deprecated` as a superscript to the content, and use the greater-than sign (`>`) to introduce the substitute API plus a link to the API description.<br>Example: abandonmentMethod<sup>(deprecated)</sup><br>> This API is no longer maintained since API version 7. You are advised to use [newMethod]\(#newmethod) instead.|
-| 8    | Permission description       | Use "Required Permissions" as a level-2 heading.<br>1. If a specific permission required for using the component can be requested only by system applications, provide the description in the following format:<br>ohos.permission.examplePermission (available only to system applications)<br>2. If a specific permission required for using the component can be requested by all applications, provide the description in the following format:<br>ohos.permission.examplePermission<br>3. If multiple permissions are required for using the component, provide the permissions with `and` or `or` in the following format:<br>ohos.permission.examplePermissionA and ohos.permission.examplePermissionB<br>ohos.permission.examplePermissionA or ohos.permission.examplePermissionB |
-| 9   | @system api | 1. If all APIs of the component are system APIs, add the following sentence to the next line of the initial version description:<br>The APIs provided by this component are system APIs.<br>2. If an API is a system API that can be used only by original equipment manufacturers (OEMs), add the following sentence to the API description:<br>**System API**: This is a system API. |
+| 8    | Permission description       | Use "Required Permissions" as a level-2 heading.<br>1. If a specific permission required for using the component can be requested only by system applications, provide the description in the following format:<br>ohos.permission.examplePermission (available only to system applications)<br>2. If a specific permission required for using the component can be requested by all applications, provide the description in the following format:<br>ohos.permission.examplePermission<br>3. If multiple permissions are required for using the component, provide the permissions with `and` or `or` in the following format:<br>ohos.permission.examplePermissionA and ohos.permission.examplePermissionB<br>ohos.permission.examplePermissionA or ohos.permission.examplePermissionB|
+| 9   | @system api | 1. If all APIs of the component are system APIs, add the following sentence to the next line of the initial version description:<br>The APIs provided by this component are system APIs.<br>2. If an API is a system API that can be used only by original equipment manufacturers (OEMs), add the following sentence to the API description:<br>**System API**: This is a system API.|
 | 10   | Sample code programming language     | Use code blocks to provide sample code, and mark the programming language ts by adding `// xxx.ets` at the beginning of every sample code block.|
 | 11   | Link       | Link format: [Link text]\(Link content)<br>Cross-folder link format: [markdown file name]\(\.\./../xxx/xxx.md). One `./` indicates one upper-level folder.<br>Intra-topic link format: [Interface A<sup>7+</sup>]\(#xxxa7). The text in the intra-topic link must be the same as the title to be linked. In the link, all letters must be in lowercase, and no special character (except the hyphen) or tag is included.|
 

en/release-notes/api-diff/v4.0-beta2/Readme-EN.md

@@ -3,7 +3,7 @@
 - [Ability framework](js-apidiff-ability.md)
 - [Account subsystem](js-apidiff-account.md)
 - [AI subsystem](js-apidiff-ai.md)
-- [System Applications](js-apidiff-application.md)
+- [System applications](js-apidiff-application.md)
 - [ArkUI development framework](js-apidiff-arkui.md)
 - [Power management subsystem](js-apidiff-battery.md)
 - [Bundle management framework](js-apidiff-bundle.md)

en/release-notes/changelogs/v3.2-beta4/changelogs-enterprise_device_management.md

+# Customization Subsystem Changelog
+
+## cl.Customization.1 Change of the Enterprise Device Management Module Name
+
+Changed **@ohos.enterpriseDeviceManager.d.ts** to **@ohos.enterprise.adminManager.d.ts** in OpenHarmony 3.2.8.3. You need to adapt your applications according to the following information.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must be adapted so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Before Change                            | After Change                             |
+| ---------------------------------  | ---------------------------------- |
+| @ohos.enterpriseDeviceManager.d.ts  | @ohos.enterprise.adminManager.d.ts |
+
+**Adaptation Guide**
+
+Import the module with the new name.
+
+Before change:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterpriseDeviceManager';
+```
+
+After change:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterprise.adminManager';
+```
+
+## cl.Customization.2 enterpriseDeviceManager/DeviceSettingsManager.d.ts Module Change
+
+Changed **enterpriseDeviceManager/DeviceSettingsManager.d.ts** to **ohos.enterprise.dateTimeManager.d.ts** in OpenHarmony 3.2.8.3.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must be adapted so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Original API               | Original API Type            | New API             | New API Type               |
+| ---------------------------------  | --------- |  ---------------------------------- | ----- |
+| enterpriseDeviceManager/DeviceSettingsManager.d.ts | interface | @ohos.enterprise.dateTimeManager.d.ts | namespace |
+
+**Adaptation Guide**
+
+If **setDateTime()** of **enterpriseDeviceManager/DeviceSettingsManager.d.ts** is used:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterpriseDeviceManager'
+
+let wantTemp = {
+    bundleName: "bundleName",
+    abilityName: "abilityName",
+};
+enterpriseDeviceManager.getDeviceSettingsManager((error, mgr) => {
+    if (error) {
+        console.log("error code:" + error.code + " error message:" + error.message);
+        return;
+    }
+    mgr.setDateTime(wantTemp, 1526003846000, (error) => {
+        if (error) {
+            console.log("error code:" + error.code + " error message:" + error.message);
+        }
+    });
+});
+```
+
+You need to import the new namespace.
+
+```js
+import dateTimeManager from '@ohos.enterprise.dateTimeManager'
+
+let wantTemp = {
+    bundleName: "bundleName",
+    abilityName: "abilityName",
+};
+dateTimeManager.setDateTime(wantTemp, 1526003846000, (error) => {
+    if (error) {
+        console.log("error code:" + error.code + " error message:" + error.message);
+    }
+})
+```
+
+## cl.Customization.3 Change of APIs to System APIs
+
+Changed all enterprise device management APIs to system APIs in OpenHarmony 3.2.8.3.
+
+**Change Impact**
+
+All APIs can be called only by system applications.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId?: number): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId?: number): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, userId: number, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, userId?: number): Promise<**boolean**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** getEnterpriseInfo(admin: Want, callback: AsyncCallback<**EnterpriseInfo**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** getEnterpriseInfo(admin: Want): Promise<**EnterpriseInfo**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isSuperAdmin(bundleName: String, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isSuperAdmin(bundleName: String): Promise<**boolean**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **interface** EnterpriseInfo | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **enum** AdminType | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **enum** ManagedEvent | systemapi     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number): Promise<**void**>; | systemapi     |
+
+## cl.Customization.4 API Permission Change
+
+Added permission verification for some APIs in OpenHarmony 3.2.8.3.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must have the corresponding permission so that it can properly call these APIs.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | New Permission|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId: number, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId?: number): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId: number, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId?: number): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo, callback: AsyncCallback<**void**>): void; | ohos.permission.SET_ENTERPRISE_INFO     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo): Promise<**void**>; | ohos.permission.SET_ENTERPRISE_INFO     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SET_DATETIME     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number): Promise<**void**>; | ohos.permission.ENTERPRISE_SET_DATETIME     |
+
+**Adaptation Guide**
+
+Apply for the corresponding permissions for your application before these APIs are called.

en/release-notes/changelogs/v3.2-beta5/changelogs-arkui.md

@@ -39,7 +39,6 @@
     }
     ```
 
-    ![datePicker](../../../application-dev/reference/arkui-ts/figures/datePicker.gif)
 
 2. The data type declaration of the **@State**, **@Provide**, **@Link**, or **@Consume** decorated state variables can consist of only one of the primitive data types or reference data types.
 

en/release-notes/changelogs/v4.0-beta2/Readme-EN.md

 # Summary
 
 
-| Subsystem | Change Type | Description |
+| Subsystem| Change Type| Change Description|
 | -------- | -------- | -------- |
-| ArkUI |                                       |                                                              |
-| ArkUI |                                       |                                                              |
-| ArkUI |                                       |                                                              |
-| ArkUI |                                       |                                                              |
-| ArkUI |                                       |                                                              |
-| ArkUI |  |  |
-| ArkUI |  |  |
-| ArkUI |  |  |
-| ArkUI |  |                                                              |
-| ArkUI |  |                                                              |
-| ArkUI |  |                                                              |
-| ArkUI |  |  |
-| Bundle management |  |  |
-| Bundle management |  |                                                              |
-| Bundle management |  |  |
-| Bundle management |  |  |
-| Bundle management |                                       |  |
-| OS media |  |  |
-| OS media |  |                                                              |
-| OS media |  |  |
+| Bundle management subsystem| Bottom-layer implementation changed| [1. The bottom layer implementation of getAllBundleInfo in ohos.bundle.d.ts is changed.](changelogs-bundlemanager.md#clbundlemanager1-bottom-layer-implementation-of-getallbundleinfo-in-ohosbundledts-changed)<br>[2. The bottom layer implementation of getAllApplicationInfo in ohos.bundle.d.ts is changed.](changelogs-bundlemanager.md#clbundlemanager2-bottom-layer-implementation-of-getallapplicationinfo-in-ohosbundledts-changed) |
+| Bundle management subsystem| API permission changed| [1. The permission on getAllBundleInfo in ohos.bundle.bundleManager.d.ts is changed.](changelogs-bundlemanager.md#clbundlemanager3-permission-on-getallbundleinfo-in-ohosbundlebundlemanagerdts-changed)<br>[2. The permission on getAllApplicationInfo in ohos.bundle.bundleManager.d.ts is changed.](changelogs-bundlemanager.md#clbundlemanager4-permission-on-getallapplicationinfo-in-ohosbundlebundlemanagerdts-changed) |
+| Bundle management subsystem| API/Component changed| [1. The getSpecifiedDistributionType API is moved from ohos.bundle.installer.d.ts to ohos.bundle.bundleManager.d.ts.](changelogs-bundlemanager.md#clbundlemanager5-getspecifieddistributiontype-moved-from-ohosbundleinstallerdts-to-ohosbundlebundlemanagerdts)<br>[2. The getAdditionalInfo API is moved from ohos.bundle.installer.d.ts to ohos.bundle.bundleManager.d.ts.](changelogs-bundlemanager.md#clbundlemanager6-getadditionalinfo-moved-from-ohosbundleinstallerdts-to-ohosbundlebundlemanagerdts) |
+| Bundle management subsystem| API/Component changed| [proxyDatas is renamed proxyData.](changelogs-bundlemanager.md#clbundlemanager7-proxydatas-renamed-proxydata-in-the-modulejson5-file) |
+| Bundle management subsystem| Configuration file changed| [schema in the module.json file is changed.](https://gitee.com/openharmony/docs/blob/master/en/release-notes/changelogs/OpenHarmony_4.0.9.3/changelogs-bundlemanager.md) |
+| OS multimedia subsystem| Enumeration declaration changed| [The audio output stream type is changed from AUDIOSTREAM_TYPE_RERNDERER to AUDIOSTREAM_TYPE_RENDERER.](changelogs-multimedia.md#clmultimedia1-stream-type-enum-declaration-in-audio-c-apis-changed)|
+| OS multimedia subsystem| Enumerated value changed| [1. For the OH_AudioStream_Usage enum, the enumerated value AUDIOSTREAM_USAGE_MEDIA is deleted, and AUDIOSTREAM_USAGE_COMMUNICATION is changed to AUDIOSTREAM_USAGE_VOICE_COMMUNICATION and AUDIOSTREAM_USAGE_VOICE_ASSISTANT.](changelogs-multimedia.md#clmultimedia2-oh_audiostream_usage-changed)<br>[2. The enumerated value AUDIOSTREAM_SAMPLE_F32LE is deleted for the OH_AudioStream_SampleFormat enum.](changelogs-multimedia.md#clmultimedia3-audiostream_sample_f32le-deleted-for-oh_audiostream_sampleformat) |
+| OS multimedia subsystem| Input parameter changed| [The input parameter content is deleted from getAudioEffectInfoArray.](changelogs-multimedia.md#clmultimedia4-deleted-content-from-getaudioeffectinfoarray) |
 | Application access control | Permission changed | [Change of the Permission Requesting Modes of the Phone, Messaging, and Call Logs Permission Groups](changelogs-accessToken.md#claccesstoken2-change-of-the-permission-requesting-modes-of-the-phone-messaging-and-call-logs-permission-groups) |
 | Application access control | Permission group changed | [Change of the Media and Files Permission Group:<br/>Moved ohos.permission.MEDIA_LOCATION to the Images and Videos permission group.<br/>Moved ohos.permission.READ_MEDIA and ohos.permission.WRITE_MEDIA to the Documents permission group.](changelogs-accessToken.md#claccesstoken1-change-of-the-media-and-files-permission-group) |
-| Input method framework |  |  |
-| Theme framework |  |  |
 | Distributed data management | API/Component changed | [Change of ValuesBucket to a Public Interface](changelogs-distributeddatamgr.md#cldistributeddatamgr1-change-of-valuesbucket-to-a-public-interface) |
 | Distributed data management | API/Component changed | [Change of Some Predicate Interfaces in dataSharePredicates to Public Interfaces](changelogs-distributeddatamgr.md#cldistributeddatamgr2-change-of-some-predicate-interfaces-in-datasharepredicates-to-public-interfaces) |
 | Distributed data management | API/Component changed | [Change of the DataShareExtensionAbility Context](cldistributeddatamgr3-change-of-the-datashareextensionability-context) |
@@ -35,16 +21,14 @@
 | Distributed data management | Variable changed (Native) | [1. Change of int (*close)(OH_Cursor *cursor) in OH_Cursor Struct to int (*destroy)(OH_Cursor *cursor)](cldistributeddatamgr6-change-of-int-closeoh_cursor-cursor-in-oh_cursor-struct-to-int-destroyoh_cursor-cursor)<br/>[2. Change of int (*destroyPredicates)(OH_Predicates *predicates) in OH_Predicates Struct to int (*destroy) (OH_Predicates *predicates)](cldistributeddatamgr7-change-of-int-destroypredicatesoh_predicates-predicates-in-oh_predicates-struct-to-int-destroy-oh_predicates-predicates)<br/>[3. Change of int (*destroyValueObject)(OH_VObject *valueObject) in OH_VObject Struct to int (*destroy) (OH_VObject *valueObject)](cldistributeddatamgr8-change-of-int-destroyvalueobjectoh_vobject-valueobject-in-oh_vobject-struct-to-int-destroy-oh_vobject-valueobject)<br/>[4. Change of int (*destroyValuesBucket)(OH_VBucket *bucket) in OH_VBucket Struct to int (*destroy) (OH_VBucket *bucket)](cldistributeddatamgr9-change-of-int-destroyvaluesbucketoh_vbucket-bucket-in-oh_vbucket-struct-to-int-destroy-oh_vbucket-bucket) |
 | Distributed data management | Variable changed (Native) | [Change of OH_Rdb_Config Struct Member Variables:<br/>1. Changed the type of **securityLevel** from **enum OH_Rdb_SecurityLevel** to **in**.<br/>2. Deleted the member variable **path**.<br/>3. Added the member variables **selfSize**, **dataBaseDir**, **storeName**, **bundleName**, and **moduleName**.](cldistributeddatamgr10-change-of-oh_rdb_config-struct-member-variables) |
 | Distributed data management | API input parameter changed  (Native) | [Change of const char *path in OH_Rdb_DeleteStore() to const OH_Rdb_Config *config](changelogs-distributeddatamgr.md#cldistributeddatamgr11-change-of-const-char-path-in-oh_rdb_deletestore-to-const-oh_rdb_config-config) |
-| Distributed hardware |  |  |
-| Media |                                       |                                                              |
-| Media |                                       |                                                              |
-| Ability - widget framework |                                       |                                                              |
-| Ability - widget framework |  |  |
-| Pan-Sensor |  |  |
+| Multimedia subsystem| Input parameter changed| [The input parameter content is deleted from getAudioEffectInfoArray.](changelogs-multimedia.md#clmultimedia4-deleted-content-from-getaudioeffectinfoarray) |
+| Multimedia subsystem| API changed| [The APIs related to audio track switching are deleted.](changelogs-multimedia.md#clmultimedia5-playback-apis-changed) |
+| Ability - widget framework| API permission changed| [Some APIs are moved from ohos.app.form.formHost.d.ts and their permission is changed.](changelogs-formfwk.md#clformfwk1-some-apis-moved-from-ohosappformformhostdts-and-their-permission-changed) |
+| Ability - widget framework| API parameter changed| [The callback parameter is moved as the last parameter in the event subscription and unsubscription APIs (on/off).](changelogs-formfwk.md#clformfwk2-adjusted-the-parameter-sequence-of-event-subscription-and-unsubscription-apis-onoff) |
+| Pan-sensor subsystem| API/Component changed| [The attributes VibrateFromFile (custom vibration effect) and HapticFileDescriptor (file descriptor of the custom vibration configuration file) are added. The vibration effect supported by startVibration is extended from VibrateEffect = VibrateTime \| VibratePreset to VibrateEffect = VibrateTime \| VibratePreset \| VibrateFromFile.](changelogs-miscdevice.md) |
 | File management (media library) | API/Component changed | [Change of the mediaLibrary Interface Compatibility](changelogs-medialibrary.md#clfile1-change-of-the-mediabibrary-interface-compatibility) |
 | Communication | API/Component changed | [Change of the API Name](changelogs-wifiManager.md#clwifi1-change-of-the-name-of-the-api-for-obtaining-wi-fi-scan-result) |
 
-
 > **NOTE**
 > 
 > Unless otherwise specified, the changes described in this topic are ArkTS API changes.

en/release-notes/changelogs/v4.0-beta2/changelogs-bundlemanager.md

+# Bundle Management Subsystem Changelog
+
+
+## cl.bundlemanager.1 Bottom Layer Implementation of getAllBundleInfo in \@ohos.bundle.d.ts Changed
+
+The **getAllBundleInfo** API in the **\@ohos.bundle.d.ts** file is marked as deprecated. On the image with **targetAPILevel** set to API 9 or later, the returned data list is empty.
+
+**Change Impact**
+
+After an update to the new image version, the calling of **getAllBundleInfo** in **\@ohos.bundle.d.ts** is successful. However, the returned data list is empty. To obtain the bundle information, call **getAllBundleInfo** in the **\@ohos.bundle.bundleManager.d.ts** file.
+
+**Key API/Component Changes**
+
+The bottom-layer implementation is changed. The result value of **getAllBundleInfo** in **\@ohos.bundle.d.ts** is empty.
+
+**Adaptation Guide**
+
+If your application uses **getAllBundleInfo** in **\@ohos.bundle.d.ts**, replace it with **getAllBundleInfo** in **\@ohos.bundle.bundleManager.d.ts**. For details about how to use the new API, see the corresponding API Reference.
+```ets
+import bundleManager from '@ohos.bundle.bundleManager';
+```
+
+
+## cl.bundlemanager.2 Bottom Layer Implementation of getAllApplicationInfo in \@ohos.bundle.d.ts Changed
+
+The **getAllApplicationInfo** API in the **\@ohos.bundle.d.ts** file is marked as deprecated. On the image with **targetAPILevel** set to API 9 or later, the returned data list is empty.
+
+**Change Impact**
+
+After an update to the new image version, the calling of **getAllApplicationInfo** in **\@ohos.bundle.d.ts** is successful. However, the returned data list is empty. To obtain the application information, call **getAllApplicationInfo** in the **\@ohos.bundle.bundleManager.d.ts** file.
+
+**Key API/Component Changes**
+
+The bottom-layer implementation is changed. The result value of **getAllApplicationInfo** in **\@ohos.bundle.d.ts** is empty.
+
+**Adaptation Guide**
+
+If your application uses **getAllApplicationInfo** in **\@ohos.bundle.d.ts**, replace it with **getAllApplicationInfo** in **\@ohos.bundle.bundleManager.d.ts**. For details about how to use the new API, see the corresponding API Reference.
+```ets
+import bundleManager from '@ohos.bundle.bundleManager';
+```
+
+
+## cl.bundlemanager.3 Permission on getAllBundleInfo in \@ohos.bundle.bundleManager.d.ts Changed
+
+The APIs for obtaining the application list require authorization from the end user.
+
+Therefore, the permission on **getAllBundleInfo** in **\@ohos.bundle.bundleManager.d.ts** is changed to **ohos.permission.GET_INSTALLED_BUNDLE_LIST**.
+
+**Change Impact**
+
+After an update to the new image version, you must have the **ohos.permission.GET_INSTALLED_BUNDLE_LIST** permission when calling **getAllBundleInfo**. Otherwise, the call fails.
+
+**Key API/Component Changes**
+
+Therefore, the permission on **getAllBundleInfo** in **\@ohos.bundle.bundleManager.d.ts** is changed to **ohos.permission.GET_INSTALLED_BUNDLE_LIST**.
+
+**Adaptation Guide**
+
+1. Add the **ohos.permission.GET_INSTALLED_BUNDLE_LIST** permission to the configuration file of the application.
+
+2. This permission is of the **user_grant** type and is not authorized by default during application installation. You must display a dialog box to ask the permission from the user or use pre-authorization.
+
+3. For details about how to display a dialog box to ask for permission, see [Requesting User Authorization](../../../application-dev/security/accesstoken-guidelines.md#requesting-user-authorization).
+
+4. For details about how to use pre-authorization, see [Pre-authorizing user_grant Permissions](../../../application-dev/security/accesstoken-guidelines.md#pre-authorizing-user_grant-permissions).
+
+
+## cl.bundlemanager.4 Permission on getAllApplicationInfo in \@ohos.bundle.bundleManager.d.ts Changed
+
+The APIs for obtaining the application list require authorization from the end user.
+
+Therefore, the permission on **getAllApplicationInfo** in **\@ohos.bundle.bundleManager.d.ts** is changed to **ohos.permission.GET_INSTALLED_BUNDLE_LIST**.
+
+**Change Impact**
+
+After an update to the new image version, you must have the **ohos.permission.GET_INSTALLED_BUNDLE_LIST** permission when calling **getAllApplicationInfo**. Otherwise, the call fails.
+
+**Key API/Component Changes**
+
+Therefore, the permission on **getAllApplicationInfo** in **\@ohos.bundle.bundleManager.d.ts** is changed to **ohos.permission.GET_INSTALLED_BUNDLE_LIST**.
+
+**Adaptation Guide**
+
+1. Add the **ohos.permission.GET_INSTALLED_BUNDLE_LIST** permission to the configuration file of the application.
+
+2. This permission is of the **user_grant** type and is not authorized by default during application installation. You must display a dialog box to ask the permission from the user or use pre-authorization.
+
+3. For details about how to display a dialog box to ask for permission, see [Requesting User Authorization](../../../application-dev/security/accesstoken-guidelines.md#requesting-user-authorization).
+
+4. For details about how to use pre-authorization, see [Pre-authorizing user_grant Permissions](../../../application-dev/security/accesstoken-guidelines.md#pre-authorizing-user_grant-permissions).
+
+
+## cl.bundlemanager.5 getSpecifiedDistributionType Moved from \@ohos.bundle.installer.d.ts to \@ohos.bundle.bundleManager.d.ts
+
+The **getSpecifiedDistributionType** API is moved from **\@ohos.bundle.installer.d.ts** to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Change Impact**
+
+After an update to the new SDK version, the **getSpecifiedDistributionType** API in **\@ohos.bundle.installer.d.ts** is moved to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Key API/Component Changes**
+
+The **getSpecifiedDistributionType** API is moved from **\@ohos.bundle.installer.d.ts** to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Adaptation Guide**
+
+To use **getSpecifiedDistributionType**, import the **bundleManager** module.
+```ets
+import bundleManager form '@ohos.bundle.bundleManager'
+```
+
+
+## cl.bundlemanager.6 getAdditionalInfo Moved from \@ohos.bundle.installer.d.ts to \@ohos.bundle.bundleManager.d.ts
+
+The **getAdditionalInfo** API is moved from **\@ohos.bundle.installer.d.ts** to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Change Impact**
+
+After an update to the new SDK version, the **getAdditionalInfo** API in **\@ohos.bundle.installer.d.ts** is moved to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Key API/Component Changes**
+
+The **getAdditionalInfo** API is moved from **\@ohos.bundle.installer.d.ts** to **\@ohos.bundle.bundleManager.d.ts**.
+
+**Adaptation Guide**
+
+To use **getAdditionalInfo**, import the **bundleManager** module.
+```ets
+import bundleManager form '@ohos.bundle.bundleManager'
+```
+
+
+## cl.bundlemanager.7 proxyDatas Renamed proxyData in the module.json5 File
+
+**proxyDatas** is renamed **proxyData**.
+
+**Change Impact**
+
+After an update to the new SDK version, **proxyDatas** is **renamed proxyData**. If your application is not adapted, the build will fail.
+
+**Key API/Component Changes**
+
+**proxyDatas** is renamed **proxyData**.
+
+**Adaptation Guide**
+
+Replace **proxyDatas** with **proxyData**. The content of **proxyDatas** does not need to be changed.

en/release-notes/changelogs/v4.0-beta2/changelogs-device_manager.md

+# Device Management Changelog
+
+
+## cl.device_manager.1 API Permissions Changed
+
+Permission verification is added for some APIs of device management from OpenHarmony 4.0.8.2. 
+
+**Change Impact**
+
+The apps developed using OpenHarmony 4.0.8.2 or later must have the corresponding permissions. Otherwise, the related APIs cannot be called.
+
+**Key API/Component Changes**
+
+| Module| Class| Method/Attribute/Enum/Constant| Added Permission| 
+| -------- | -------- | -------- | -------- |
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** release(): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getTrustedDeviceListSync(): Array<DeviceInfo> | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getTrustedDeviceList(callback:AsyncCallback<Array<DeviceInfo>>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getTrustedDeviceList(): Promise<Array<DeviceInfo>> | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getLocalDeviceInfoSync(): DeviceInfo | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getLocalDeviceInfo(callback:AsyncCallback<DeviceInfo>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getLocalDeviceInfo(): Promise<DeviceInfo> | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getDeviceInfo(networkId: string, callback:AsyncCallback<DeviceInfo>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** getDeviceInfo(networkId: string): Promise<DeviceInfo> | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** startDeviceDiscovery(subscribeInfo: SubscribeInfo): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** startDeviceDiscovery(subscribeInfo: SubscribeInfo, filterOptions?: string): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** stopDeviceDiscovery(subscribeId: number): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** publishDeviceDiscovery(publishInfo: PublishInfo): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** unPublishDeviceDiscovery(publishId: number): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** authenticateDevice(deviceInfo: DeviceInfo, authParam: AuthParam, callback: AsyncCallback<{deviceId: string, pinToken ?: number}>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** unAuthenticateDevice(deviceInfo: DeviceInfo): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** verifyAuthInfo(authInfo: AuthInfo, callback: AsyncCallback<{deviceId: string, level: number}>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** setUserOperation(operateAction: number, params: string): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** requestCredentialRegisterInfo(requestInfo: string, callback: AsyncCallback<{registerInfo: string}>): void; | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** importCredential(credentialInfo: string, callback: AsyncCallback<{resultInfo: string}>): void; | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** deleteCredential(queryInfo: string, callback: AsyncCallback<{resultInfo: string}>): void; | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'uiStateChange', callback: Callback<{ param: string}>): void; | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'uiStateChange', callback?: Callback<{ param: string}>): void; | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'deviceStateChange', callback: Callback<{ action: DeviceStateChangeAction, device: DeviceInfo }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'deviceStateChange', callback?: Callback<{ action: DeviceStateChangeAction, device: DeviceInfo }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'deviceFound', callback: Callback<{ subscribeId: number, device: DeviceInfo }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'deviceFound', callback?: Callback<{ subscribeId: number, device: DeviceInfo }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'discoverFail', callback: Callback<{ subscribeId: number, reason: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'discoverFail', callback?: Callback<{ subscribeId: number, reason: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'publishSuccess', callback: Callback<{ publishId: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'publishSuccess', callback?: Callback<{ publishId: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'publishFail', callback: Callback<{ publishId: number, reason: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'publishFail', callback?: Callback<{ publishId: number, reason: number }>): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** on(type: 'serviceDie', callback: () => void): void | ohos.permission.ACCESS_SERVICE_DM | 
+| \@ohos.distributedHardware.deviceManager | deviceManager | **function** off(type: 'serviceDie', callback?: () => void): void | ohos.permission.ACCESS_SERVICE_DM | 
+
+**Adaptation Guide**
+
+Apply for the corresponding permissions for your application before these APIs are called.

en/release-notes/changelogs/v4.0-beta2/changelogs-formfwk.md

+# Ability - Widget Framework Changelog
+
+
+## cl.formfwk.1 Some APIs Moved from \@ohos.app.form.formHost.d.ts and Their Permission Changed
+
+1. APIs used for listening for and obtaining dynamic widget information are moved from **\@ohos.app.form.formHost.d.ts** to **\@ohos.app.form.formObserver.d.ts**.
+
+2. The permission for these APIs is changed from **ohos.permission.REQUIRE_FORM** to **ohos.permission.OBSERVE_FORM_RUNNING**.
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.
+
+**Key API/Component Changes**
+
+| API| Home .d.ts File Before Modification| Home .d.ts File After Modification| Permission Required Before Modification| Permission Required After Modification| 
+| -------- | -------- | -------- | -------- | -------- |
+| on('formAdd') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| off('formAdd') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| on('formRemove') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| off('formRemove') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| on('notifyVisible') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| off('notifyVisible') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| on('notifyInvisible') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| off('notifyInvisible') | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| getRunningFormInfos | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| getRunningFormInfosByFilter | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+| getRunningFormInfoById | \@ohos.app.form.formHost.d.ts | \@ohos.app.form.formObserver.d.ts | ohos.permission.REQUIRE_FORM | ohos.permission.OBSERVE_FORM_RUNNING | 
+
+**Adaptation Guide**
+
+Adapt your application code accordingly. To use these APIs in OpenHarmony 4.0.9.5 and later versions, import **\@ohos.app.form.formObserver.d.ts** and request the **ohos.permission.OBSERVE_FORM_RUNNING** permission.
+
+**Example**
+
+```js
+import formObserver from @ohos.app.form.formObserver.d.ts;
+
+try {
+  formObserver.getRunningFormInfos((error, data) => {
+    if (error) {
+      console.error(`error, code: ${error.code}, message: ${error.message}`);
+    } else {
+      console.log('formHost getRunningFormInfos, data: ${JSON.stringify(data)}');
+    }
+  }, 'com.example.ohos.formjsdemo');
+} catch(error) {
+  console.error(`catch error, code: ${error.code}, message: ${error.message}`);
+}
+```
+
+
+## cl.formfwk.2 Adjusted the Parameter Sequence of Event Subscription and Unsubscription APIs (on/off)
+
+The **callback** parameter is moved as the last parameter in the event subscription and unsubscription APIs (**on**/**off**).
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.
+
+**Key API/Component Changes**
+
+Before change:
+
+```js
+function on(type: 'formAdd', observerCallback: Callback<formInfo.RunningFormInfo>, bundleName?: string): void;
+function off(type: 'formAdd', observerCallback?: Callback<formInfo.RunningFormInfo>, bundleName?: string): void;
+
+function on(type: 'formRemove', observerCallback: Callback<formInfo.RunningFormInfo>, bundleName?: string): void;
+function off(type: 'formRemove', observerCallback?: Callback<formInfo.RunningFormInfo>, bundleName?: string): void;
+
+function on(
+    type: 'notifyVisible',
+    observerCallback: Callback<Array<formInfo.RunningFormInfo>>,
+    hostBundleName?: string
+  ): void;
+function off(
+    type: 'notifyVisible',
+    observerCallback?: Callback<Array<formInfo.RunningFormInfo>>,
+    hostBundleName?: string
+  ): void;
+
+function on(
+    type: 'notifyInvisible',
+    observerCallback: Callback<Array<formInfo.RunningFormInfo>>,
+    hostBundleName?: string
+  ): void;
+function off(
+    type: 'notifyInvisible',
+    observerCallback?: Callback<Array<formInfo.RunningFormInfo>>,
+    hostBundleName?: string
+  ): void;
+```
+
+After change:
+
+```js
+function on(type: 'formAdd', observerCallback: Callback<formInfo.RunningFormInfo>): void;
+function on(type: 'formAdd', hostBundleName: string, observerCallback: Callback<formInfo.RunningFormInfo>): void;
+function off(type: 'formAdd', hostBundleName?: string, observerCallback?: Callback<formInfo.RunningFormInfo>): void;
+
+function on(type: 'formRemove', observerCallback: Callback<formInfo.RunningFormInfo>): void;
+function on(type: 'formRemove', hostBundleName: string, observerCallback: Callback<formInfo.RunningFormInfo>): void;
+function off(type: 'formRemove', hostBundleName?: string, observerCallback?: Callback<formInfo.RunningFormInfo>): void;
+
+function on(type: 'notifyVisible', observerCallback: Callback<Array<formInfo.RunningFormInfo>>): void;
+function on(
+    type: 'notifyVisible',
+    hostBundleName: string,
+    observerCallback: Callback<Array<formInfo.RunningFormInfo>>
+  ): void;
+function off(
+    type: 'notifyVisible',
+    hostBundleName?: string,
+    observerCallback?: Callback<Array<formInfo.RunningFormInfo>>
+  ): void;
+
+function on(type: 'notifyInvisible', observerCallback: Callback<Array<formInfo.RunningFormInfo>>): void;
+function on(
+    type: 'notifyInvisible',
+    hostBundleName: string,
+    observerCallback: Callback<Array<formInfo.RunningFormInfo>>,
+  ): void;
+function off(
+    type: 'notifyInvisible',
+    hostBundleName?: string,
+    observerCallback?: Callback<Array<formInfo.RunningFormInfo>>
+  ): void;
+```
+
+**Adaptation Guide**
+
+Adapt your application code accordingly. In OpenHarmony 4.0.9.5 and later versions, pass in **callback** as the last parameter when calling these APIs.
+
+**Example**
+
+```js
+import formObserver from @ohos.app.form.formObserver.d.ts;
+
+let bundleName = 'ohos.samples.FormApplication';
+let callback = function(data) {
+  console.log('a new form added, data: ${JSON.stringify(data)');
+}
+
+formHost.on('formAdd', callback);
+formHost.on('formAdd', bundleName, callback);
+```

en/release-notes/changelogs/v4.0-beta2/changelogs-miscdevice.md

+# Pan-Sensor Subsystem Changelog
+
+
+## cl.vibrator.1 Added Attributes Related to Custom Vibration
+
+The attributes **VibrateFromFile** (custom vibration effect) and **HapticFileDescriptor** (file descriptor of the custom vibration configuration file) are added. The vibration effect supported by **startVibration** is extended from **VibrateEffect = VibrateTime | VibratePreset** to **VibrateEffect = VibrateTime | VibratePreset | VibrateFromFile**.
+
+**Change Impact**
+
+When developing applications based on OpenHarmony 4.0.8.2 and later SDK versions, you can use the **VibrateFromFile** attribute to enable devices that support custom vibration to trigger vibration according to the vibration sequence configured in the custom vibration configuration file.
+
+**Key API/Component Changes**
+
+Added the **VibrateFromFile** and **HapticFileDescriptor** attributes to **\@ohos.vibrator.d.ts**.
+
+| Module| Class| Method/Attribute/Enum/Constant| Change Type| 
+| -------- | -------- | -------- | -------- |
+| \@ohos.vibrator.d.ts | vibrator | HapticFileDescriptor | Added| 
+| \@ohos.vibrator.d.ts | vibrator | VibrateFromFile | Added| 
+
+**Adaptation Guide**
+
+Obtain the resources in the vibration configuration file through the resource management API, and start or stop custom vibration as required.
+
+```ts
+import vibrator from '@ohos.vibrator';
+import resourceManager from '@ohos.resourceManager';
+
+const FILE_NAME = "xxx.json";
+
+async function openResource(fileName) {
+    let fileDescriptor = undefined;
+    let mgr = await resourceManager.getResourceManager();
+    await mgr.getRawFd(fileName).then(value => {
+        fileDescriptor = {fd: value.fd, offset: value.offset, length: value.length};
+        console.log('openResource success fileName: ' + fileName);
+    }).catch(error => {
+        console.log('openResource err: ' + error);
+    });
+    return fileDescriptor;
+}
+
+async function closeResource(fileName) {
+    let mgr = await resourceManager.getResourceManager();
+    await mgr.closeRawFd(fileName).then(()=> {
+        console.log('closeResource success fileName: ' + fileName);
+    }).catch(error => {
+        console.log('closeResource err: ' + error);
+    });
+}
+
+// Obtain the file descriptor of the vibration configuration file.
+let rawFd = openResource(FILE_NAME);
+// To use startVibration and stopVibration, you must configure the ohos.permission.VIBRATE permission.
+try {
+    // Start custom vibration.
+    vibrator.startVibration({
+        type: "file",
+        hapticFd: { fd: rawFd.fd, offset: rawFd.offset, length: rawFd.length }
+    }, {
+        usage: "alarm"
+    }).then(() => {
+        console.info('startVibration success');
+    }, (error) => {
+        console.info('startVibration error');
+    });
+    // Stop vibration in all modes.
+    vibrator.stopVibration(function (error) {
+        if (error) {
+            console.log('error.code' + error.code + 'error.message' + error.message);
+            return;
+        }
+        console.log('Callback returned to indicate successful.');
+    })
+} catch (error) {
+    console.info('errCode: ' + error.code + ' ,msg: ' + error.message);
+}
+// Close the vibration file.
+closeResource(FILE_NAME);
+```

en/release-notes/changelogs/v4.0-beta2/changelogs-multimedia.md

+# Multimedia Subsystem Changelog
+
+
+## cl.multimedia.1 Stream Type Enum Declaration in Audio C APIs Changed
+
+For the audio APIs of API version 10 in C, the audio output stream type is changed from **AUDIOSTREAM_TYPE_RERNDERER** to **AUDIOSTREAM_TYPE_RENDERER**.
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.
+
+**Key API/Component Changes**
+
+Before change:
+
+```C
+enum OH_AudioStream_Type {
+   /**
+    * The type for audio stream is renderer.
+    */
+   AUDIOSTREAM_TYPE_RERNDERER = 1,
+
+   /**
+    * The type for audio stream is capturer.
+    */
+   AUDIOSTREAM_TYPE_CAPTURER = 2
+};
+```
+
+After change:
+
+```C
+enum OH_AudioStream_Type {
+   /**
+    * The type for audio stream is renderer.
+    */
+   AUDIOSTREAM_TYPE_RENDERER = 1,
+
+   /**
+    * The type for audio stream is capturer.
+    */
+   AUDIOSTREAM_TYPE_CAPTURER = 2
+};
+```
+
+**Adaptation Guide**
+
+Change **AUDIOSTREAM_TYPE_RERNDERER** to **AUDIOSTREAM_TYPE_RENDERER** in your code. Example:
+
+Before change:
+
+```C
+OH_AudioStreamBuilder* builder;
+OH_AudioStreamBuilder_Create(&builder, AUDIOSTREAM_TYPE_RERNDERER);
+```
+
+After change:
+
+```C
+OH_AudioStreamBuilder* builder;
+OH_AudioStreamBuilder_Create(&builder, AUDIOSTREAM_TYPE_RENDERER);
+```
+
+
+## cl.multimedia.2 OH_AudioStream_Usage Changed
+
+In the **native_audiostream_base.h** file of the audio APIs of API version 10 in C, for the **OH_AudioStream_Usage** enum, the enumerated value **AUDIOSTREAM_USAGE_MEDIA** is deleted, and **AUDIOSTREAM_USAGE_COMMUNICATION** is changed to **AUDIOSTREAM_USAGE_VOICE_COMMUNICATION** and **AUDIOSTREAM_USAGE_VOICE_ASSISTANT**.
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.  
+
+**Key API/Component Changes**
+
+Before change:
+
+```C
+typedef enum {
+    AUDIOSTREAM_USAGE_UNKNOWN = 0,
+    AUDIOSTREAM_USAGE_MEDIA = 1,
+    AUDIOSTREAM_USAGE_COMMUNICATION = 2,
+} OH_AudioStream_Usage;
+```
+
+After change:
+
+```C
+typedef enum {
+    /**
+     * Unknown usage.
+     */
+    AUDIOSTREAM_USAGE_UNKNOWN = 0,
+    /**
+     * Music usage.
+     */
+    AUDIOSTREAM_USAGE_MUSIC = 1,
+    /**
+     * Voice communication usage.
+     */
+    AUDIOSTREAM_USAGE_VOICE_COMMUNICATION = 2,
+    /**
+     * Voice assistant usage.
+     */
+    AUDIOSTREAM_USAGE_VOICE_ASSISTANT = 3,
+    /**
+     * Movie or video usage.
+     */
+    AUDIOSTREAM_USAGE_MOVIE = 10,
+
+} OH_AudioStream_Usage;
+```
+
+**Adaptation Guide**
+
+When using **OH_AudioStreamBuilder_SetRendererInfo**, set **OH_AudioStream_Usage** to **AUDIOSTREAM_USAGE_MUSIC** or **AUDIOSTREAM_USAGE_MOVIE**, rather than **AUDIOSTREAM_USAGE_MEDIA**.
+
+Before change:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_MEDIA);
+```
+
+After change:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_MUSIC); // Music scene
+```
+
+Or:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_MOVIE); // Video scene
+```
+
+When using **OH_AudioStreamBuilder_SetRendererInfo**, set **OH_AudioStream_Usage** to **AUDIOSTREAM_USAGE_VOICE_COMMUNICATION** or **AUDIOSTREAM_USAGE_VOICE_ASSISTANT**, rather than **AUDIOSTREAM_USAGE_COMMUNICATION**.
+
+Before change:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_COMMUNICATION);
+```
+
+After change:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_VOICE_COMMUNICATION); // Communication scene
+```
+
+Or:
+
+```C
+OH_AudioStreamBuilder_SetRendererInfo(builder, AUDIOSTREAM_USAGE_VOICE_ASSISTANT); // Voice assistant scene
+```
+
+
+## cl.multimedia.3 AUDIOSTREAM_SAMPLE_F32LE Deleted for OH_AudioStream_SampleFormat
+
+In the **native_audiostream_base.h** file of the audio APIs of API version 10 in C, the enumerated value **AUDIOSTREAM_SAMPLE_F32LE** is deleted for the **OH_AudioStream_SampleFormat** enum.
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.  
+
+**Key API/Component Changes**
+
+Before change:
+
+```C
+typedef enum {
+    AUDIOSTREAM_SAMPLE_U8 = 0,
+    AUDIOSTREAM_SAMPLE_S16LE = 1,
+    AUDIOSTREAM_SAMPLE_S24LE = 2,
+    AUDIOSTREAM_SAMPLE_S32LE = 3,
+    AUDIOSTREAM_SAMPLE_F32LE = 4,
+} OH_AudioStream_SampleFormat;
+```
+
+After change:
+
+```C
+typedef enum {
+    /**
+     * Unsigned 8 format.
+     */
+    AUDIOSTREAM_SAMPLE_U8 = 0,
+    /**
+     * Signed 16 bit integer, little endian.
+     */
+    AUDIOSTREAM_SAMPLE_S16LE = 1,
+    /**
+     * Signed 24 bit integer, little endian.
+     */
+    AUDIOSTREAM_SAMPLE_S24LE = 2,
+    /**
+     * Signed 32 bit integer, little endian.
+     */
+    AUDIOSTREAM_SAMPLE_S32LE = 3,
+} OH_AudioStream_SampleFormat;
+```
+
+**Adaptation Guide**
+
+Do not use **AUDIOSTREAM_SAMPLE_F32LE** for **OH_AudioStream_SampleFormat**.
+
+
+## cl.multimedia.4 Deleted content from getAudioEffectInfoArray
+
+The input parameter **content** is deleted from **getAudioEffectInfoArray**.
+
+**Change Impact**
+
+Applications that use the involved APIs may have compatibility issues.
+
+**Key API/Component Changes**
+
+Before change:
+
+```js
+getAudioEffectInfoArray(content: ContentType, usage: StreamUsage, callback: AsyncCallback<AudioEffectInfoArray>): void;
+getAudioEffectInfoArray(content: ContentType, usage: StreamUsage): Promise<AudioEffectInfoArray>;
+```
+
+After change:
+
+```js
+getAudioEffectInfoArray(usage: StreamUsage, callback: AsyncCallback<AudioEffectInfoArray>): void;
+getAudioEffectInfoArray(usage: StreamUsage): Promise<AudioEffectInfoArray>;
+```
+
+**Adaptation Guide**
+
+When calling this API, pass in only the input parameter **usage**. If **getAudioEffectInfoArray** is used in your application code, delete the **content** parameter.
+
+
+## cl.multimedia.5 Playback APIs Changed
+
+The APIs related to audio track switching are deleted.
+
+**Change Impact**
+
+These APIs are unavailable.
+
+**Key API/Component Changes**
+
+The deleted APIs are as follows:
+
+| Class| API|
+| -------- | -------- |
+| Media.Core | MD_KEY_LANGUAGE |
+| Media.AVPlayer | selectTrack(index:&nbsp;number):&nbsp;void |
+| Media.AVPlayer | deselectTrack(index:&nbsp;number):&nbsp;void |
+| Media.AVPlayer | getCurrentTrack(trackType:&nbsp;MediaType,&nbsp;callback:&nbsp;AsyncCallback&lt;number&gt;):&nbsp;void |
+| Media.AVPlayer | getCurrentTrack(trackType:&nbsp;MediaType):&nbsp;Promise&lt;number&gt; |
+| Media.AVPlayer | on(type:&nbsp;'trackChange',&nbsp;callback:&nbsp;(index:&nbsp;number,&nbsp;isSelect:&nbsp;boolean)&nbsp;=&gt;&nbsp;void):&nbsp;void; |
+| Media.AVPlayer | off(type:&nbsp;'trackChange'):&nbsp;void |

en/website.md

@@ -4,6 +4,7 @@
 - [Glossary](glossary.md)
 - Release Notes
   - OpenHarmony 4.x Releases
+    - [OpenHarmony v4.0 Beta2 (2023-08-02)](release-notes/OpenHarmony-v4.0-beta2.md)
     - [OpenHarmony v4.0 Beta1 (2023-06-03)](release-notes/OpenHarmony-v4.0-beta1.md)
   - OpenHarmony 3.x Releases
     - [OpenHarmony v3.2 Release (2023-04-09)](release-notes/OpenHarmony-v3.2-release.md)
@@ -37,6 +38,53 @@
       - [OpenHarmony v1.1.1 LTS (2021-06-22)](release-notes/OpenHarmony-1-1-1-LTS.md)
       - [OpenHarmony v1.1.0 LTS (2021-04-01)](release-notes/OpenHarmony-1-1-0-LTS.md)
   - API Differences
+    - OpenHarmony 4.0 Beta2
+      - ArkTS API Differences
+        - [Ability framework](release-notes/api-diff/v4.0-beta2/js-apidiff-ability.md)
+        - [Account subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-account.md)
+        - [AI subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-ai.md)
+        - [System Applications](release-notes/api-diff/v4.0-beta2/js-apidiff-application.md)
+        - [ArkUI development framework](release-notes/api-diff/v4.0-beta2/js-apidiff-arkui.md)
+        - [Power management subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-battery.md)
+        - [Bundle management framework](release-notes/api-diff/v4.0-beta2/js-apidiff-bundle.md)
+        - [Communication subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-communication.md)
+        - [Compiler and runtime subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-compiler-and-runtime.md)
+        - [Customization subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-customization.md)
+        - [DFX subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-dfx.md)
+        - [Distributed data management subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-distributed-data.md)
+        - [Distributed hardware subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-distributed-hardware.md)
+        - [Upload and download](release-notes/api-diff/v4.0-beta2/js-apidiff-download-upload.md)
+        - [Driver subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-driver.md)
+        - [File management subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-file-management.md)
+        - [Geolocation subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-geolocation.md)
+        - [Globalization subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-global.md)
+        - [Misc services subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-misc.md)
+        - [MSDP subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-msdp.md)
+        - [Multimodal input subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-multi-modal-input.md)
+        - [Multimedia subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-multimedia.md)
+        - [Common event and notification subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-notification.md)
+        - [Resource scheduler subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-resource-scheduler.md)
+        - [Security subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-security.md)
+        - [Pan-sensor subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-sensor.md)
+        - [Startup subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-start-up.md)
+        - [Telephony subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-telephony.md)
+        - [Test subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-unitest.md)
+        - [USB subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-usb.md)
+        - [Web subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-web.md)
+        - [Window manager subsystem](release-notes/api-diff/v4.0-beta2/js-apidiff-window.md)
+      - API Changelogs
+        - [Readme](release-notes/changelogs/v4.0-beta2/Readme-EN.md)
+        - [ArkUI Framework Changelog](release-notes/changelogs/v4.0-beta2/changelogs-arkui.md)
+        - [Bundle management subsystem Changelog](release-notes/changelogs/v4.0-beta2/changelogs-bundlemanager.md)
+        - [Ability Access Control Changelog](release-notes/changelogs/v4.0-beta2/changelogs-accesstoken.md)
+        - [Distributed Data Management Changelog](release-notes/changelogs/v4.0-beta2/changelogs-distributeddatamgr.md)
+        - [Ability - Widget Framework Changelog](release-notes/changelogs/v4.0-beta2/changelogs-formfwk.md)
+        - [Input Method Framework Changelog](release-notes/changelogs/v4.0-beta2/changelogs-imf.md)
+        - [Multimedia Subsystem Changelog](release-notes/changelogs/v4.0-beta2/changelogs-multimedia.md)
+        - [Theme Framework - Screen Lock Management Changelog](release-notes/changelogs/v4.0-beta2/changelogs-screenlock.md)
+        - [Device Management Subsystem Changelog](release-notes/changelogs/v4.0-beta2/changelogs-device_manager.md)
+        - [Pan-Sensor Subsystem Changelog](release-notes/changelogs/v4.0-beta2/changelogs-miscdevice.md)
+        - [File Management Subsystem (MediaLibrary) Changelog](release-notes/changelogs/v4.0-beta2/changelogs-medialibrary.md)
     - OpenHarmony 4.0 Beta1
       - JS API Differences
         - [Ability](release-notes/api-diff/v4.0-beta1/js-apidiff-ability.md)
@@ -72,6 +120,7 @@
         - [Compiler and Runtime](release-notes/changelogs/v4.0-beta1/changelogs-arkcompiler.md)
         - [ArkUI](release-notes/changelogs/v4.0-beta1/changelogs-arkui.md)
         - [Bundle Management](release-notes/changelogs/v4.0-beta1/changelogs-bundlemanager.md)
+        - [Common Capability Changelog](release-notes/changelogs/v4.0-beta1/changelogs-common.md)
         - [Globalization](release-notes/changelogs/v4.0-beta1/changelogs-global.md)
         - [Security - HUKS](release-notes/changelogs/v4.0-beta1/changelogs-huks.md)
         - [Resource Scheduler](release-notes/changelogs/v4.0-beta1/changelogs-resourceschedule.md)

zh-cn/application-dev/application-models/Readme-CN.md

@@ -64,7 +64,6 @@
       - [跨端迁移](hop-cross-device-migration.md)
       - [多端协同（仅对系统应用开放）](hop-multi-device-collaboration.md)
     - [订阅系统环境变量的变化](subscribe-system-environment-variable-changes.md)
-    - [原子化服务支持分享](atomic-services-support-sharing.md)
   - 了解进程模型
     - [进程模型概述](process-model-stage.md)
     - 公共事件

zh-cn/application-dev/application-models/common-event-subscription.md

@@ -12,7 +12,7 @@
 
 | 接口名 | 接口描述 |
 | -------- | -------- |
-| createSubscriber(subscribeInfo: [CommonEventSubscribeInfo](../reference/apis/js-apis-commonEventManager.md#commoneventsubscribeinfo), callback: AsyncCallback<[CommonEventData](../reference/apis/js-apis-commonEventManager.md#commoneventdata)>): void | 创建订阅者对象（callback） |
+| createSubscriber(subscribeInfo: [CommonEventSubscribeInfo](../reference/apis/js-apis-commonEventManager.md#commoneventsubscribeinfo), callback: AsyncCallback<[CommonEventSubscriber](../reference/apis/js-apis-inner-commonEvent-commonEventSubscriber.md#使用说明)>): void | 创建订阅者对象（callback） |
 | createSubscriber(subscribeInfo: CommonEventSubscribeInfo): Promise<CommonEventSubscriber> | 创建订阅者对象（promise） |
 | subscribe(subscriber: CommonEventSubscriber, callback: AsyncCallback): void | 订阅公共事件 |
 

zh-cn/application-dev/connectivity/net-mdns.md

@@ -28,9 +28,13 @@ MDNS管理的典型场景有：
 | ohos.net.mdns.DiscoveryService | startSearchingMDNS(): void | 开始搜索局域网内的mDNS服务。 |
 | ohos.net.mdns.DiscoveryService | stopSearchingMDNS(): void | 停止搜索局域网内的mDNS服务。 |
 | ohos.net.mdns.DiscoveryService | on(type: 'discoveryStart', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void | 订阅开启监听mDNS服务的通知。 |
+| ohos.net.mdns.DiscoveryService | off(type: 'discoveryStart', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void | 取消开启监听mDNS服务的通知。 |
 | ohos.net.mdns.DiscoveryService | on(type: 'discoveryStop', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void | 订阅停止监听mDNS服务的通知。 |
+| ohos.net.mdns.DiscoveryService | off(type: 'discoveryStop', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void | 取消停止监听mDNS服务的通知。 |
 | ohos.net.mdns.DiscoveryService | on(type: 'serviceFound', callback: Callback\<LocalServiceInfo>): void | 订阅发现mDNS服务的通知。 |
+| ohos.net.mdns.DiscoveryService | off(type: 'serviceFound', callback: Callback\<LocalServiceInfo>): void | 取消发现mDNS服务的通知。 |
 | ohos.net.mdns.DiscoveryService | on(type: 'serviceLost', callback: Callback\<LocalServiceInfo>): void | 订阅移除mDNS服务的通知。 |
+| ohos.net.mdns.DiscoveryService | off(type: 'serviceLost', callback: Callback\<LocalServiceInfo>): void | 取消移除mDNS服务的通知。 |
 
 ## 管理本地服务
 
@@ -98,6 +102,7 @@ mdns.removeLocalService(context, localServiceInfo, function (error, data) {
 4. 订阅mDNS服务发现相关状态变化。
 5. 启动搜索局域网内的mDNS服务。
 6. 停止搜索局域网内的mDNS服务。
+7. 取消订阅的mdns服务。
 
 ```js
 // 从@ohos.net.mdns中导入mdns命名空间
@@ -139,4 +144,18 @@ discoveryService.startSearchingMDNS();
 
 // 停止搜索局域网内的mDNS服务
 discoveryService.stopSearchingMDNS();
+
+// 取消订阅的mdns服务
+discoveryService.off('discoveryStart', (data) => {
+  console.log(JSON.stringify(data));
+});
+discoveryService.off('discoveryStop', (data) => {
+  console.log(JSON.stringify(data));
+});
+discoveryService.off('serviceFound', (data) => {
+  console.log(JSON.stringify(data));
+});
+discoveryService.off('serviceLost', (data) => {
+  console.log(JSON.stringify(data));
+});
 ```
\ No newline at end of file

zh-cn/application-dev/faqs/full-sdk-compile-guide.md

@@ -14,17 +14,13 @@
 **下载和编译命令**
 
 1. 初始化manifest：repo init -u https://gitee.com/openharmony/manifest.git -b $manifest_branch --no-repo-verify --repo-url=https://gitee.com/oschina/repo --no-clone-bundle 
-
 2. 根据上面下载的manifest仓进行下载代码：repo sync -c -d --force-sync
-
-3. 预编译：yes y | apt install libxinerama-dev libxcursor-dev libxrandr-dev libxi-dev && rm -rf prebuilts/clang/ohos/darwin-x86_64/clang-480513 && rm -rf prebuilts/clang/ohos/windows-x86_64/clang-480513 && rm -rf prebuilts/clang/ohos/linux-x86_64/clang-480513 && bash build/prebuilts_download.sh -ndk && apt-get update -qqy && apt-get install doxygen -y --force-yes
-
+3. 预编译：yes y | apt install libxinerama-dev libxcursor-dev libxrandr-dev libxi-dev && rm -rf prebuilts/clang/ohos/darwin-x86_64/clang-480513 && rm -rf prebuilts/clang/ohos/windows-x86_64/clang-480513 && rm -rf prebuilts/clang/ohos/linux-x86_64/clang-480513 && apt-get update -qqy && apt-get install doxygen -y --force-yes
 4. 编译windows：./build.sh --product-name ohos-sdk
-   编译mac：./build.sh --product-name ohos-sdk --gn-args full_mini_debug=false --keep-ninja-going --gn-args=is_use_check_deps=false
+5. 编译mac：./build.sh --product-name ohos-sdk --gn-args full_mini_debug=false --keep-ninja-going --gn-args=is_use_check_deps=false
 
 编译成功后导出out/sdk/packages/ohos-sdk/目录下的文件即可
 
 ## 替换SDK
 
 full-SDK编译完成后需要在DevEcoStudio替换使用，具体请参考[full-SDK替换指南](full-sdk-switch-guide.md)。
-

zh-cn/application-dev/quick-start/arkts-builder.md

@@ -66,7 +66,7 @@ MyGlobalBuilderFunction()
 
 - 参数的类型必须与参数声明的类型一致，不允许undefined、null和返回undefined、null的表达式。
 
-- 在自定义构建函数内部，不允许改变参数值。如果需要改变参数值，且同步回调用点，建议使用[@Link](arkts-link.md)。
+- 在@Builder修饰的函数内部，不允许改变参数值。
 
 - \@Builder内UI语法遵循[UI语法规则](arkts-create-custom-components.md#build函数)。
 

zh-cn/application-dev/quick-start/arkts-observed-and-objectlink.md

@@ -15,7 +15,7 @@
 
 - 被\@Observed装饰的类，可以被观察到属性的变化；
 
-- 子组件中\@ObjectLink装饰器装饰的状态变量用于接收\@Observed装饰的类的实例，和父组件中对应的状态变量建立双向数据绑定。这个实例可以是数组中的被\@Observed装饰的项，或者是class object中是属性，这个属性同样也需要被\@Observed装饰。
+- 子组件中\@ObjectLink装饰器装饰的状态变量用于接收\@Observed装饰的类的实例，和父组件中对应的状态变量建立双向数据绑定。这个实例可以是数组中的被\@Observed装饰的项，或者是class object中的属性，这个属性同样也需要被\@Observed装饰。
 
 - 单独使用\@Observed是没有任何作用的，需要搭配\@ObjectLink或者[\@Prop](arkts-prop.md)使用。
 

zh-cn/application-dev/quick-start/arkts-persiststorage.md

@@ -78,10 +78,10 @@ struct Index {
 ```
 
 - 新应用安装后首次启动运行：
-  1. 调用PersistProp初始化PersistentStorage，首先查询在PersistentStorage本地文件中是否存在“aProp”，查询结果为不存在，因为应用是第一次安装；
-  2. 接着查询属性“aProp”在AppStorage中是否存在，依旧不存在；
-  3. 在AppStorge中创建名为“aProp”的number类型属性，属性初始值是定义的默认值47；
-  4. PersistentStorage将属性“aProp”和值47写入磁盘，AppStorage中“aProp”对应的值和其后续的更改将被持久化；
+  1. 调用PersistProp初始化PersistentStorage，首先查询在PersistentStorage本地文件中是否存在“aProp”，查询结果为不存在，因为应用是第一次安装。
+  2. 接着查询属性“aProp”在AppStorage中是否存在，依旧不存在。
+  3. 在AppStorge中创建名为“aProp”的number类型属性，属性初始值是定义的默认值47。
+  4. PersistentStorage将属性“aProp”和值47写入磁盘，AppStorage中“aProp”对应的值和其后续的更改将被持久化。
   5. 在Index组件中创建状态变量\@StorageLink('aProp') aProp，和AppStorage中“aProp”双向绑定，在创建的过程中会在AppStorage中查找，成功找到“aProp”，所以使用其在AppStorage找到的值47。
 
   **图1** PersistProp初始化流程  
@@ -89,14 +89,14 @@ struct Index {
 ![zh-cn_image_0000001553348833](figures/zh-cn_image_0000001553348833.png)
 
 - 触发点击事件后：
-  1. 状态变量\@StorageLink('aProp') aProp改变，触发Text组件重新刷新；
-  2. \@StorageLink装饰的变量是和AppStorage中建立双向同步的，所以\@StorageLink('aProp') aProp的变化会被同步回AppStorage中；
-  3. AppStorage中“aProp”属性的改变会同步到所有绑定该“aProp”的单向或者双向变量，在本示例中没有其他的绑定“aProp”的变量；
+  1. 状态变量\@StorageLink('aProp') aProp改变，触发Text组件重新刷新。
+  2. \@StorageLink装饰的变量是和AppStorage中建立双向同步的，所以\@StorageLink('aProp') aProp的变化会被同步回AppStorage中。
+  3. AppStorage中“aProp”属性的改变会同步到所有绑定该“aProp”的单向或者双向变量，在本示例中没有其他的绑定“aProp”的变量。
   4. 因为“aProp”对应的属性已经被持久化，所以在AppStorage中“aProp”的改变会触发PersistentStorage，将新的改变写入本地磁盘。
 
 - 后续启动应用：
-  1. 执行PersistentStorage.PersistProp('aProp', 47)，在首先查询在PersistentStorage本地文件查询“aProp”属性，成功查询到；
-  2. 将在PersistentStorage查询到的值写入AppStorage中；
+  1. 执行PersistentStorage.PersistProp('aProp', 47)，在首先查询在PersistentStorage本地文件查询“aProp”属性，成功查询到。
+  2. 将在PersistentStorage查询到的值写入AppStorage中。
   3. 在Index组件里，\@StorageLink绑定的“aProp”为PersistentStorage写入AppStorage中的值，即为上一次退出引用存入的值。
 
 

zh-cn/application-dev/quick-start/arkts-rendering-control-foreach.md

@@ -22,7 +22,7 @@ ForEach(
 | 参数名           | 参数类型                                     | 必填   | 参数描述                                     |
 | ------------- | ---------------------------------------- | ---- | ---------------------------------------- |
 | arr           | Array                                    | 是    | 必须是数组，允许设置为空数组，空数组场景下将不会创建子组件。同时允许设置返回值为数组类型的函数，例如arr.slice(1, 3)，设置的函数不得改变包括数组本身在内的任何状态变量，如Array.splice、Array.sort或Array.reverse这些改变原数组的函数。 |
-| itemGenerator | (item:&nbsp;any,&nbsp;index?:&nbsp;number)&nbsp;=&gt;&nbsp;void | 是    | 生成子组件的lambda函数，为数组中的每一个数据项创建一个或多个子组件，单个子组件或子组件列表必须包括在大括号“{...}”中。<br/>**说明：**<br/>-&nbsp;子组件的类型必须是ForEach的父容器组件所允许的（例如，只有当ForEach父级为List组件时，才允许LitemItem子组件）。<br/>-&nbsp;允许子类构造函数返回if或另一个ForEach。ForEach可以在if内的任意位置。<br/>-&nbsp;可选index参数如在函数体中使用，则必须仅在函数签名中指定。 |
+| itemGenerator | (item:&nbsp;any,&nbsp;index?:&nbsp;number)&nbsp;=&gt;&nbsp;void | 是    | 生成子组件的lambda函数，为数组中的每一个数据项创建一个或多个子组件，单个子组件或子组件列表必须包括在大括号“{...}”中。<br/>**说明：**<br/>-&nbsp;子组件的类型必须是ForEach的父容器组件所允许的（例如，只有当ForEach父级为List组件时，才允许ListItem子组件）。<br/>-&nbsp;允许子类构造函数返回if或另一个ForEach。ForEach可以在if内的任意位置。<br/>-&nbsp;可选index参数如在函数体中使用，则必须仅在函数签名中指定。 |
 | keyGenerator  | (item:&nbsp;any,&nbsp;index?:&nbsp;number)&nbsp;=&gt;&nbsp;string | 否    | 匿名函数，用于给数组中的每一个数据项生成唯一且固定的键值。键值生成器的功能是可选的，但是，为了使开发框架能够更好地识别数组更改，提高性能，建议提供。如将数组反向时，如果没有提供键值生成器，则ForEach中的所有节点都将重建。<br/>**说明：**<br/>-&nbsp;同一数组中的不同项绝对不能计算出相同的ID。<br/>-&nbsp;如果未使用index参数，则项在数组中的位置变动不得改变项的键值。如果使用了index参数，则当项在数组中的位置有变动时，键值必须更改。<br/>-&nbsp;当某个项目被新项替换（值不同）时，被替换的项键值和新项的键值必须不同。<br/>-&nbsp;在构造函数中使用index参数时，键值生成函数也必须使用该参数。<br>-&nbsp;键值生成函数不允许改变任何组件状态。 |
 
 

zh-cn/application-dev/quick-start/introduction-to-arkts.md

@@ -766,7 +766,7 @@ class Point {
     x: number = 0
     y: number = 0
 }
-let p: Point = {42 ,42}
+let p: Point = {x: 42, y: 42}
 ```
 
 ### 字段
@@ -868,11 +868,11 @@ class Rectangle {
 }
 ```
 
-实例方法需要在类的实例上调用：
+必须通过类的实例调用实例方法：
 
 ```typescript
-let r = new Rectangle(10, 10)
-console.log(square.calculateArea()) // output: 100
+let square = new Rectangle(10, 10)
+console.log(square.calculateArea()) // 输出：100
 ```
 
 #### 静态方法
@@ -883,7 +883,7 @@ console.log(square.calculateArea()) // output: 100
 
 所有实例都可以访问静态方法。
 
-要调用静态方法，需要使用类名：
+必须通过类名调用静态方法：
 
 ```typescript
 class Cl {
@@ -1309,7 +1309,7 @@ class Stack<Element> {
     public pop(): Element {
         // ...
     }
-    public push(e: Element) {
+    public push(e: Element):void {
         // ...
     }
 }
@@ -1402,7 +1402,7 @@ foo<number>()
 
 ## 空安全
 
-默认情况下，ArkTS中的所有类型都是不可为空的，因此类型的值不能为空。这类似于TypeScript的严格空值检查模式（`strictNullChecks`），但规则更严格，而且ArkTS中没有`undefined`类型。
+默认情况下，ArkTS中的所有类型都是不可为空的，因此类型的值不能为空。这类似于TypeScript的严格空值检查模式（`strictNullChecks`），但规则更严格。
 
 在下面的示例中，所有行都会导致编译时错误：
 
@@ -1454,28 +1454,47 @@ class Person {
 
 ### 可选链
 
-可选链运算符`?.` 可以在编写代码时遇到求值为null的表达式就停止运行。
+在访问对象属性时，如果该属性是`undefined`或者`null`，可选链运算符会返回`undefined`。
 
 ```typescript
 class Person {
-    // ...
-    spouse: Person | null = null
-    nick: string | null = null
-    getSpouseNick(): string | null {
+    nick    : string | null = null
+    spouse ?: Person
+
+    setSpouse(spouse: Person) : void {
+        this.spouse = spouse
+    }
+
+    getSpouseNick(): string | null | undefined {
         return this.spouse?.nick
     }
+
+    constructor(nick: string) {
+        this.nick = nick
+        this.spouse = undefined
+    }
 }
 ```
 
-**说明**：`getSpouseNick`的返回类型必须为`string | null`，因为该方法可能返回null。
+**说明**：`getSpouseNick`的返回类型必须为`string | null | undefined`，因为该方法可能返回`null`或者`undefined`。
 
-可选链可以是任何长度的，可包含任意数量的 `?.` 运算符。
+可选链可以任意长，可以包含任意数量的`?.`运算符。
 
-在以下示例中，如果某人有配偶，且配偶有昵称，则输出是该人的配偶昵称。否则，输出为空：
+在以下示例中，如果一个`Person`的实例有不为空的`spouse`属性，且`spouse`有不为空的`nickname`属性，则输出`spouse.nick`。否则，输出`undefined`：
 
 ```typescript
-let p: Person = ...
-console.log(p?.spouse?.nick)
+class Person {
+    nick    : string | null = null
+    spouse ?: Person
+
+    constructor(nick: string) {
+        this.nick = nick
+        this.spouse = undefined
+    }
+}
+
+let p: Person = new Person("Alice")
+console.log(p.spouse?.nick) // 打印undefined
 ```
 
 ## 模块

zh-cn/application-dev/quick-start/typescript-to-arkts-migration-guide.md

@@ -3,7 +3,7 @@
 本文通过提供简洁的约束指导如何将标准的TypeScript代码重构为ArkTS代码。尽管ArkTS是基于TypeScript设计的，但出于性能考虑，一些TypeScript的特性被限制了。因此，在ArkTS中，所有的TypeScript特性被分成三类。 
 
 1. **完全支持的特性**：原始代码无需任何修改。根据测试，对于已遵循最佳TypeScript实践的项目，代码库中90%到97%的内容可以保持原封不动。
-2. **部分支持的特性**：需小规模的代码重构。例如，必须使用关键字`let`代替`var` 来声明变量。注意，根据本文提供的约束进行代码重构后，您的代码仍为有效的TypeScript代码。
+2. **部分支持的特性**：需小规模的代码重构。例如，必须使用关键字`let`代替`var`来声明变量。注意，根据本文提供的约束进行代码重构后，您的代码仍为有效的TypeScript代码。
 3. **不支持的特性**：需大规模的代码重构。例如，不支持`any`类型，所有使用`any`的代码都需要引入显式类型。
 
 本文将逐一介绍所有部分支持和所有不支持的特性，并提供代码重构的建议。对于没有提到的特性，则说明ArkTS完全支持。
@@ -80,7 +80,7 @@ if (!res.succeeded()) {
 }
 ```
 
-`any`类型在TypeScript中并不常见，只有大约1%的TypeScript代码库使用。一些代码检查工具（例如ESLint）也制定一系列规则来禁止使用`any`。因此，虽然禁止`any` 将导致代码重构，但重构量很小，有助于整体性能提升，因此这个约束是非常有价值的。
+`any`类型在TypeScript中并不常见，只有大约1%的TypeScript代码库使用。一些代码检查工具（例如ESLint）也制定一系列规则来禁止使用`any`。因此，虽然禁止`any`将导致代码重构，但重构量很小，有助于整体性能提升，因此这个约束是非常有价值的。
 
 ### 禁止在运行时变更对象布局
 
@@ -137,7 +137,7 @@ let p6 = new Point(6.0, 6.0)
 console.log("Distance between p5 and p6: " + distance(p5, p6))
 ```
 
-不可预测的对象布局修改会影响代码的可读性以及运行时性能。从开发者的角度来说，在某处定义类，然后又在其他地方修改实际的对象布局，很容易引起困惑乃至引入错误。此外，这点还需要额外的运行时支持，增加了执行开销。这一点与静态类型的约束也冲突：既然已决定使用显式类型，为什么还需要添加或删除属性呢？
+修改对象布局会影响代码的可读性以及运行时性能。从开发者的角度来说，在某处定义类，然后又在其他地方修改实际的对象布局，很容易引起困惑乃至引入错误。此外，这点还需要额外的运行时支持，增加了执行开销。这一点与静态类型的约束也冲突：既然已决定使用显式类型，为什么还需要添加或删除属性呢？
 
 当前，只有少数项目允许在运行时变更对象布局，一些常用的代码检查工具也增加了相应的限制规则。这个约束只会导致少量代码重构，但对性能提升会有积极的影响。
 
@@ -214,13 +214,13 @@ structural typing是否有助于生成清晰、易理解的代码，关于这一
 
 ## 约束说明
 
-### 仅支持属性名称为标识符的对象
+### 对象的属性名必须是合法的标识符
 
 **规则：**`arkts-identifiers-as-prop-names`
 
 **级别：错误**
 
-ArkTS不支持属性名称为数字或字符串的对象。通过属性名访问类的属性，通过数值索引访问数组元素。
+在ArkTS中，对象的属性名不能为数字或字符串。通过属性名访问类的属性，通过数值索引访问数组元素。
 
 **TypeScript**
 
@@ -235,9 +235,9 @@ console.log(x[2])
 
 ```typescript
 class X {
-    public name: number
+    public name: number = 0
 }
-let x = {name: 1}
+let x: X = {name: 1}
 console.log(x.name)
 
 let y = [1, 2, 3]
@@ -269,7 +269,7 @@ console.log(z.get(2))
 
 **级别：错误**
 
-TypeScript中的`Symbol()` API用于在运行时生成唯一的属性名称。由于该API的常见使用场景在静态类型语言中没有意义，因此，ArkTS不支持`Symbol()` API。在ArkTS中，对象布局在编译时就确定了，且不能在运行时被更改。
+TypeScript中的`Symbol()`API用于在运行时生成唯一的属性名称。由于该API的常见使用场景在静态类型语言中没有意义，因此，ArkTS不支持`Symbol()`API。在ArkTS中，对象布局在编译时就确定了，且不能在运行时被更改。
 
 **TypeScript**
 
@@ -284,7 +284,7 @@ let o = {
 
 ```typescript
 class SomeClass {
-    public someProperty : string
+    public someProperty : string = ""
 }
 let o = new SomeClass()
 ```
@@ -300,13 +300,13 @@ let o = new SomeClass()
 * 不支持声明动态属性
 * 限制使用标准库
 
-### 不支持带“#”符号的私有修饰符
+### 不支持以`#`开头的私有字段
 
 **规则：**`arkts-no-private-identifiers`
 
 **级别：错误**
 
-ArkTS不支持以`#`符号开头的私有修饰符。改用 `private`关键字。
+ArkTS不支持使用`#`符号开头声明的私有字段。改用`private`关键字。
 
 **TypeScript**
 
@@ -330,7 +330,7 @@ class C {
 
 **级别：错误**
 
-类型、命名空间等的命名必须唯一，且能够与变量名等其他名称区分开来。
+类型、命名空间等的命名必须唯一，且能够与其他名称（例如：变量名）区分开来。
 
 **TypeScript**
 
@@ -401,57 +401,39 @@ scoped_var = 5
 scoped_let = 5 //编译时错误
 ```
 
-### 使用具体的类型而非`any`、`undefined`或`unknown`
+### 使用具体的类型而非`any`或`unknown`
 
-**规则：**`arkts-no-any-undefined-unknown`
+**规则：**`arkts-no-any-unknown`
 
 **级别：错误**
 
-ArkTS不支持`any`、`undefined`和`unknown`类型。显式指定具体类型。
+ArkTS不支持`any`和`unknown`类型。显式指定具体类型。
 
 **TypeScript**
 
 ```typescript
-var x
-console.log(x) // undefined
+let value1 : any
+value1 = true
+value1 = 42
 
-var y: any
-console.log(y) // undefined
+let value2 : unknown
+value2 = true
+value2 = 42
 ```
 
 **ArkTS**
 
 ```typescript
-// 所有变量都应显式指定其具体类型：
-let x: Object = {}
-console.log(x) // {}
+let value_b: boolean = true // 或者 let value_b = true
+let value_n: number = 42 // 或者 let value_n = 42
+let value_o1: Object = true
+let value_o2: Object = 42
 ```
 
 **相关约束**
 
 * 使用Object[]而非tuple
 
-### `bigint`不是内置类型，不支持带后缀`n`的数字字面量
-
-**规则：**`arkts-no-n-suffix`
-
-**级别：错误**
-
-在ArkTS中，`bigint`是标准库的一部分，而非一种内置类型。不支持带后缀`n`的数字字面量。使用`BigInt`工厂函数生成`bigint`类型的值。
-
-**TypeScript**
-
-```typescript
-let a: bigint = 1n
-```
-
-**ArkTS**
-
-```typescript
-let a = BigInt(1)
-let b: bigint = BigInt(2)
-```
-
 ### 使用`Object[]`而非tuple
 
 **规则：**`arkts-no-tuples`
@@ -476,7 +458,7 @@ let n = t[0]
 let s = t[1]
 ```
 
-### 使用`class` 而非具有call signature的类型
+### 使用`class`而非具有call signature的类型
 
 **规则：**`arkts-no-call-signatures`
 
@@ -519,15 +501,15 @@ doSomething(new DescribableFunction())
 
 **相关约束**
 
-* 使用class而非具有构造函数签名的类型
+* 使用class而非具有构造签名的类型
 
-### 使用`class`而非具有构造函数签名的类型
+### 使用`class`而非具有构造签名的类型
 
 **规则：**`arkts-no-ctor-signatures-type`
 
 **级别：错误**
 
-ArkTS不支持对象类型中的构造函数签名。改用类。
+ArkTS不支持对象类型中的构造签名。改用类。
 
 **TypeScript**
 
@@ -626,7 +608,7 @@ const secondItem = myArray[1]
 
 ```typescript
 class X {
-    public f: string[]
+    public f: string[] = []
 }
 
 let myArray: X = new X()
@@ -673,13 +655,13 @@ interface Contact {
 interface Employee extends Identity,  Contact {}
 ```
 
-### 不支持返回`this`类型
+### 不支持`this`类型
 
-**规则：**`arkts-no-this-as-return-type`
+**规则：**`arkts-no-typing-with-this`
 
 **级别：错误**
 
-ArkTS不支持返回`this`类型。改用显式具体类型。
+ArkTS不支持`this`类型。改用显式具体类型。
 
 **TypeScript**
 
@@ -687,6 +669,14 @@ ArkTS不支持返回`this`类型。改用显式具体类型。
 interface ListItem {
     getHead(): this
 }
+
+class C {
+    n: number = 0
+
+    m(c: this) {
+        console.log(c)
+    }
+}
 ```
 
 **ArkTS**
@@ -695,6 +685,14 @@ interface ListItem {
 interface ListItem {
     getHead(): ListItem
 }
+
+class C {
+    n: number = 0
+
+    m(c: C) {
+        console.log(c)
+    }
+}
 ```
 
 ### 不支持条件类型
@@ -726,42 +724,6 @@ type X2<T> = Object
 type YI<Item, T extends Array<Item>> = Item
 ```
 
-### 可选参数不能使用primitive type
-
-**规则：**`arkts-no-opt-params`
-
-**级别：错误**
-
-ArkTS中，可选参数的类型不能为primitive type。可以使用默认参数或引用类型。对于引用类型，可选参数缺省值为`null`。
-
-**TypeScript**
-
-```typescript
-// x为可选参数：
-function f(x?: number) {
-    console.log(x) // 打印undefined或某个数字
-}
-
-// x为带默认值的必选参数：
-function g(x: number = 1) {
-    console.log(x)
-}
-```
-
-**ArkTS**
-
-```typescript
-// 使用引用类型（缺省值为null）：
-function f(x?: Number) {
-    console.log(x) // 打印null或某个数字
-}
-
-// 使用带默认值的必选参数：
-function g(x: number = 1) {
-    console.log(x)
-}
-```
-
 ### 不支持在`constructor`中声明字段
 
 **规则：**`arkts-no-ctor-prop-decls`
@@ -810,13 +772,13 @@ class Person {
 }
 ```
 
-### 接口中不支持构造函数签名
+### 接口中不支持构造签名
 
 **规则：**`arkts-no-ctor-signatures-iface`
 
 **级别：错误**
 
-ArkTS不支持接口中的构造函数签名。改用方法。
+ArkTS不支持在接口中使用构造签名。改用函数或者方法。
 
 **TypeScript**
 
@@ -844,7 +806,7 @@ function fn(i: I) {
 
 **相关约束**
 
-* 使用class而非具有构造函数签名的类型
+* 使用class而非具有构造签名的类型
 
 ### 不支持索引访问类型
 
@@ -874,7 +836,7 @@ type N = number
 
 **级别：错误**
 
-ArkTS不支持针对类字段的索引访问。改用点操作符。
+ArkTS不支持通过索引访问对象的字段。改用点操作符。
 
 **TypeScript**
 
@@ -1044,7 +1006,7 @@ interface Z {
    foo: number
 }
 
-// X实现了接口Z，显示化定义了X和Y之间的关系。
+// X实现了接口Z，显式化定义了X和Y之间的关系。
 class X implements Z {
     public foo: number
 
@@ -1053,7 +1015,7 @@ class X implements Z {
     }
 }
 
-// Y实现了接口Z，显示化定义了X和Y之间的关系。
+// Y实现了接口Z，显式化定义了X和Y之间的关系。
 class Y implements Z {
     public foo: number
 
@@ -1078,60 +1040,13 @@ x = y // ok，两者类型相同
 * 子类型/父类型不支持structural typing
 * 类型推断不支持structural typing
 
-### 可选属性的的类型不能为primitive type
-
-**规则：**`arkts-no-opt-props`
-
-**级别：错误**
-
-ArkTS中，可选属性的类型不能为primitive type。使用默认值或引用类型。对于引用类型，可选属性缺省值为`null`。该规则同样适用于类和接口。
-
-**TypeScript**
-
-```typescript
-class CompilerOptions {
-    strict?: boolean
-    sourcePath?: string
-    targetPath?: string
-}
-
-let options: CompilerOptions = {
-    strict: true,
-    sourcePath: "./src"
-}
-
-if (options.targetPath == undefined) {
-    // 一些代码
-}
-```
-
-**ArkTS**
-
-```typescript
-class CompilerOptions {
-    strict: boolean = false
-    sourcePath: string = ""
-    targetPath?: string
-}
-
-let options: CompilerOptions = {
-    strict: true,
-    sourcePath: "./src"
-    // targetPath的值为null
-}
-
-if (options.targetPath == null) {
-    // 一些代码
-}
-```
-
-### 显式标注泛型函数类型实参，除非可以推断出类型实参
+### 显式标注泛型函数类型实参，除非可以从参数中推断出类型实参
 
 **规则：**`arkts-no-inferred-generic-params`
 
 **级别：错误**
 
-如果可以从传递给泛型函数的参数中推断出具体类型，ArkTS允许省略泛型类型实参。否则，会发生编译时错误。禁止仅基于函数返回类型推断泛型类型参数。
+如果可以从传递给泛型函数的参数中推断出具体类型，ArkTS允许省略泛型类型实参。否则，省略泛型类型实参会发生编译时错误。禁止仅基于泛型函数返回类型推断泛型类型参数。
 
 **TypeScript**
 
@@ -1146,7 +1061,7 @@ let y = choose("10", 20) // 编译时错误
 function greet<T>(): T {
     return "Hello" as T
 }
-let z = greet() // x的类型被推断为“unknown”
+let z = greet() // T的类型被推断为“unknown”
 ```
 
 **ArkTS**
@@ -1277,17 +1192,17 @@ let regex: RegExp = /bc*d/
 let regex: RegExp = new RegExp("/bc*d/")
 ```
 
-### 对象字面量必须对应显式声明的类或接口
+### 显式标注对象字面量的类型
 
 **规则：**`arkts-no-untyped-obj-literals`
 
 **级别：错误**
 
-如果编译器可以推断对象字面量对应于哪些类或接口，则可以使用对象字面量。否则，将发生编译时错误。具体来说，在以下上下文中不支持使用字面量初始化类和接口：
+显式标注对象字面量的类型，除非编译器可以根据上下文推断出字面量的类型是某些类或者接口。否则，将发生编译时错误。具体来说，在以下上下文中不支持使用字面量初始化类和接口：
 
 * 初始化具有`any`、`Object`或`object`类型的任何对象
 * 初始化带有方法的类或接口
-* 初始化有自定义且有参数的构造函数的类
+* 初始化包含自定义含参数的构造函数的类
 * 初始化带`readonly`字段的类
 
 **TypeScript**
@@ -1334,7 +1249,7 @@ function id_x_y(o: Point): Point {
     return o
 }
 
-// structural typing用于推断p为Point
+// 因为TS支持structural typing，编译器可以推断p的类型为Point
 let p = {x: 5, y: 10}
 id_x_y(p)
 
@@ -1401,7 +1316,7 @@ function id_x_y(o: Point): Point {
 let p: Point = {x: 5, y: 10}
 id_x_y(p)
 
-// id_x_y预计接受Point类型，字面量初始化生成一个Point的新实例
+// id_x_y接受Point类型，字面量初始化生成一个Point的新实例
 id_x_y({x: 5, y: 10})
 ```
 
@@ -1416,7 +1331,7 @@ id_x_y({x: 5, y: 10})
 
 **级别：错误**
 
-ArkTS不支持使用对象字面量声明类型。需显式声明类和接口。
+ArkTS不支持使用对象字面量声明类型，可以使用类或者接口声明类型。
 
 **TypeScript**
 
@@ -1433,8 +1348,8 @@ type S = Set<{x: number, y: number}>
 
 ```typescript
 class O {
-    x: number
-    y: number
+    x: number = 0
+    y: number = 0
 }
 
 let o: O = {x: 2, y: 3}
@@ -1453,7 +1368,7 @@ type S = Set<O>
 
 **级别：错误**
 
-本质上，ArkTS将数组字面量的类型推断为数组内容的联合类型。如果其中任何一个元素的类型无法根据上下文推导出来（例如，未类型化的对象字面量），则会发生编译时错误。
+本质上，ArkTS将数组字面量的类型推断为数组所有元素的联合类型。如果其中任何一个元素的类型无法根据上下文推导出来（例如，无类型的对象字面量），则会发生编译时错误。
 
 **TypeScript**
 
@@ -1474,11 +1389,10 @@ let a2: C[] = [{n: 1, s: "1"}, {n: 2, s : "2"}]      // a2的类型为“C[]”
 ```
 
 **相关约束**
-
 * 对象字面量必须对应某些显式声明的类或接口
 * 对象字面量不能用于类型声明
 
-### Lambda函数的参数类型必须显式化
+### 显式标注Lambda函数的参数类型
 
 **规则：**`arkts-explicit-param-types-in-lambdas`
 
@@ -1489,7 +1403,8 @@ let a2: C[] = [{n: 1, s: "1"}, {n: 2, s : "2"}]      // a2的类型为“C[]”
 **TypeScript**
 
 ```typescript
-let f = (s) => { // 隐式定义类型为any
+// 只有在开启noImplicitAny选项时会产生编译时错误
+let f = (s /* type any is assumed */) => {
     console.log(s)
 }
 ```
@@ -1497,7 +1412,7 @@ let f = (s) => { // 隐式定义类型为any
 **ArkTS**
 
 ```typescript
-// lambda函数的参数类型必须显式化
+// 显式标注Lambda函数的参数类型
 let f = (s: string) => {
     console.log(s)
 }
@@ -1566,11 +1481,11 @@ ArkTS不支持使用类表达式。必须显式声明一个类。
 ```typescript
 const Rectangle = class {
     constructor(height: number, width: number) {
-        this.heigth = height
+        this.height = height
         this.width = width
     }
 
-    heigth
+    height
     width
 }
 
@@ -1582,11 +1497,11 @@ const rectangle = new Rectangle(0.0, 0.0)
 ```typescript
 class Rectangle {
     constructor(height: number, width: number) {
-        this.heigth = height
+        this.height = height
         this.width = width
     }
 
-    heigth: number
+    height: number
     width: number
 }
 
@@ -1617,7 +1532,7 @@ class C1 implements C {
 
 ```typescript
 interface C {
-  foo()
+  foo(): void
 }
 
 class C1 implements C {
@@ -1640,7 +1555,7 @@ let person = {name: "Bob", isEmployee: true}
 
 let n = person["name"]
 let e = person["isEmployee"]
-let s = person["office"] // undefined
+let s = person["office"] // 只有在开启noImplicitAny选项时会产生编译时错误
 ```
 
 **ArkTS**
@@ -1664,7 +1579,7 @@ let s = person.office // 编译时错误
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 不支持delete运算符
 * 仅允许在表达式中使用typeof运算符
@@ -1681,6 +1596,8 @@ let s = person.office // 编译时错误
 
 在ArkTS中，`as`关键字是类型转换的唯一语法。错误的类型转换会导致编译时错误或者运行时抛出`ClassCastException`异常。不支持使用`<type>`语法进行类型转换。
 
+当需要将`primitive`类型（如`number`或`boolean`）转换成引用类型时，请使用`new`表达式。
+
 **TypeScript**
 
 ```typescript
@@ -1699,6 +1616,12 @@ let c2 = createShape() as Circle
 // 如果转换错误，不会产生编译时或运行时报错
 let c3 = createShape() as Square
 console.log(c3.y) // undefined
+
+// 在TS中，由于`as`关键字不会在运行时生效，所以`instanceof`的左操作数不会在运行时被装箱成引用类型
+let e1 = (5.0 as Number) instanceof Number // false
+
+// 创建Number对象，获得预期结果：
+let e2 = (new Number(5.0)) instanceof Number // true
 ```
 
 **ArkTS**
@@ -1716,6 +1639,9 @@ let c2 = createShape() as Circle
 
 // 运行时抛出ClassCastException异常：
 let c3 = createShape() as Square
+
+// 创建Number对象，获得预期结果：
+let e2 = (new Number(5.0)) instanceof Number // true
 ```
 
 ### 不支持JSX表达式
@@ -1732,48 +1658,19 @@ let c3 = createShape() as Square
 
 **级别：错误**
 
-ArkTS仅允许一元运算符用于数值类型，否则会发生编译时错误。与TypeScript不同，ArkTS不支持隐式将字符串转换成数值，必须进行显示转换。
+ArkTS仅允许一元运算符用于数值类型，否则会发生编译时错误。与TypeScript不同，ArkTS不支持隐式将字符串转换成数值，必须进行显式转换。
 
 **TypeScript**
 
 ```typescript
-let a = +5   // 5为number
-let b = +"5" // 5为number
-let c = -5   // -5为number
-let d = -"5" // -5为number
-let e = ~5   // -6为number
-let f = ~"5" // -6为number
-let g = +"string" // NaN为number
-```
-
-**ArkTS**
-
-```typescript
-let a = +5   // 5为number
-let b = +"5" // 编译时错误
-let c = -5   // -5为number
-let d = -"5" // 编译时错误
-let e = ~5   // -6为number
-let f = ~"5" // 编译时错误
-let g = +"string" // 编译时错误
-```
-
-**相关约束**
+let a = +5        // 5（number类型）
+let b = +"5"      // 5（number类型）
+let c = -5        // -5（number类型）
+let d = -"5"      // -5（number类型）
+let e = ~5        // -6（number类型）
+let f = ~"5"      // -6（number类型）
+let g = +"string" // NaN（number类型）
 
-* 二元运算符\*、/、%、-、<<、>>、>>>、&、^ 和|仅适用于数值类型
-* 二元运算符+仅支持数字和字符串的隐式转换
-
-### 一元运算符`+`不能将任何类型转换为数值类型
-
-**规则：**`arkts-no-unary-plus-cast`
-
-**级别：错误**
-
-ArkTS不支持使用一元运算符`+`将任何类型转换为数值类型，该运算符只能用于数值类型。
-
-**TypeScript**
-
-```typescript
 function returnTen(): string {
     return "-10"
 }
@@ -1782,13 +1679,21 @@ function returnString(): string {
     return "string"
 }
 
-let a = +returnTen()    // -10为数值
-let b = +returnString() // NaN
+let x = +returnTen()    // -10（number类型）
+let y = +returnString() // NaN
 ```
 
 **ArkTS**
 
 ```typescript
+let a = +5        // 5（number类型）
+let b = +"5"      // 编译时错误
+let c = -5        // -5（number类型）
+let d = -"5"      // 编译时错误
+let e = ~5        // -6（number类型）
+let f = ~"5"      // 编译时错误
+let g = +"string" // 编译时错误
+
 function returnTen(): string {
     return "-10"
 }
@@ -1797,16 +1702,10 @@ function returnString(): string {
     return "string"
 }
 
-let a = +returnTen()    // 编译时错误
-let b = +returnString() // 编译时错误
+let x = +returnTen()    // 编译时错误
+let y = +returnString() // 编译时错误
 ```
 
-**相关约束**
-
-* 一元运算符+、-和~仅适用于数值类型
-* 二元运算符\*、/、%、-、<<、>>、>>>、&、^ 和|仅适用于数值类型
-* 二元运算符+仅支持数字和字符串的隐式转换
-
 ### 不支持`delete`运算符
 
 **规则：**`arkts-no-delete`
@@ -1832,8 +1731,8 @@ delete p.y
 ```typescript
 // 可以声明一个可空类型并使用null作为缺省值
 class Point {
-    x: number | null
-    y: number | null
+    x: number | null = 0
+    y: number | null = 0
 }
 
 let p = new Point()
@@ -1842,7 +1741,7 @@ p.y = null
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 仅允许在表达式中使用typeof运算符
@@ -1882,7 +1781,7 @@ let s2: string
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 不支持delete运算符
@@ -1891,73 +1790,14 @@ let s2: string
 * 不支持声明动态属性
 * 限制使用标准库
 
-### 二元运算符`*`、`/`、`%`、`-`、`<<`、`>>`、`>>>`、`&`、`^`和`|`仅适用于数值类型
-
-**规则：**`arkts-no-polymorphic-binops`
-
-**级别：错误**
-
-在ArkTS中，二元运算符`*`、`/`、`%`、`-`，`<<`、`>>`、`>>>`、`&`、`^`和`|`仅可用于数值类型。不支持将其他类型隐式转换为数值类型，否则会导致编译时错误。
-
-**TypeScript**
-
-```typescript
-let a = (5 & 5)     // 5
-let b = (5.5 & 5.5) // 5，非5.5
-let c = (5 | 5)     // 5
-let d = (5.5 | 5.5) // 5，非5.5
-
-enum Direction {
-    Up = -1,
-    Down
-}
-let e = Direction.Up >> 1 // -1
-let f = Direction.Up >>> 1 // 2147483647
-
-let g = ("10" as any) << 1  // 20
-let h = ("str" as any) << 1 // 0
-
-let i = 10 * 5
-let j = 10 / 5
-let k = 10 % 5
-let l = 10 - 5
-```
-
-**ArkTS**
-
-```typescript
-let a = (5 & 5)     // 5
-let b = (5.5 & 5.5) // 编译时错误
-let c = (5 | 5)     // 5
-let d = (5.5 | 5.5) // 编译时错误
-
-enum Direction {
-    Up,
-    Down
-}
-
-let e = Direction.Up >> 1  // 0
-let f = Direction.Up >>> 1 // 0
-
-let i = 10 * 5
-let j = 10 / 5
-let k = 10 % 5
-let l = 10 - 5
-```
-
-**相关约束**
-
-* 一元运算符+、-和~仅适用于数值类型
-* 一元运算符`+`不能将任何类型转换为数值类型
-* 二元运算符+仅支持数字和字符串的隐式转换
-
-### 二元运算符+仅支持数字和字符串的隐式转换
+### 二元运算符`+`仅支持数字和字符串的隐式转换
 
 **规则：**`arkts-no-polymorphic-plus`
 
 **级别：错误**
 
-ArkTS支持使用`+`对字符串和数字进行隐式转换。其他情形下，都需要显式转换为字符串。
+如果二元运算符`+`的一个操作数是`string`类型（包括enum中的`string`），那么另一个操作数可以是任意的类型，在运算时它的值被隐式转换成`string`。在其他情况下，ArkTS只支持`number`和enum中的`number`的隐式转换。
+正如TypeScript一样，ArkTS不支持两个`boolean`类型的值相加。其他情形下，都需要显式转换为字符串。
 
 **TypeScript**
 
@@ -1973,6 +1813,10 @@ let e = "Hello, " + "world!" // "Hello, world!"
 let f = "string" + true // "stringtrue"
 
 let g = (new Object()) + "string" // "[object Object]string"
+
+let i = true + true // JS: 2, TS: 编译时错误
+let j = true + 2 // JS: 3, TS: 编译时错误
+let k = E.E1 + true // JS: 1, TS: 编译时错误
 ```
 
 **ArkTS**
@@ -1989,13 +1833,15 @@ let e = "Hello, " + "world!" // "Hello, world!"
 let f = "string" + true // "stringtrue"
 
 let g = (new Object()).toString() + "string"
+
+let i = true + true // 编译时错误
+let j = true + 2 // 编译时错误
+let k = E.E1 + true // 编译时错误
 ```
 
 **相关约束**
 
 * 一元运算符+、-和~仅适用于数值类型
-* 一元运算符`+`不能将任何类型转换为数值类型
-* 二元运算符\*、/、%、-、<<、>>、>>>、&、^ 和|仅适用于数值类型
 
 ### 部分支持`instanceof`运算符
 
@@ -2008,31 +1854,27 @@ let g = (new Object()).toString() + "string"
 **TypeScript**
 
 ```typescript
-class X {}
+class X {
+    // ...
+}
 
 let a = (new X()) instanceof Object // true
 let b = (new X()) instanceof X      // true
-// 左操作数是类型
-let c = X instanceof Object // true
-let d = X instanceof X // false
-
-// 左操作数的类型不是any类型
-let e = (5.0 as Number) instanceof Number // false
+let c = X instanceof Object         // true, 左操作数是一个类型
+let d = X instanceof X              // false, 左操作数是一个类型
 ```
 
 **ArkTS**
 
 ```typescript
-class X {}
+class X {
+    // ...
+}
 
 let a = (new X()) instanceof Object // true
 let b = (new X()) instanceof X      // true
-// 左操作数是类型
-let c = X instanceof Object // 编译时错误
-let d = X instanceof X // 编译时错误
-
-// 左操作数可以为任何引用类型，如Number
-let e = (5.0 as Number) instanceof Number // true
+let c = X instanceof Object         // 编译时错误, 左操作数是一个类型
+let d = X instanceof X              // 编译时错误, 左操作数是一个类型
 ```
 
 ### 不支持`in`运算符
@@ -2067,7 +1909,7 @@ let b = p instanceof Person // true，且属性name一定存在
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 不支持delete运算符
@@ -2105,11 +1947,11 @@ let tmp = one
 one = two
 two = tmp
 
-let data: Number[] = [1,2,3,4]
+let data: Number[] = [1, 2, 3, 4]
 let head = data[0]
-let tail = new Array(data.length - 1)
+let tail: Number[] = []
 for (let i = 1; i < data.length; ++i) {
-    tail[i - 1] = data[i]
+    tail.push(data[i])
 }
 ```
 
@@ -2221,7 +2063,7 @@ let c1 = arr[2]
 
 **级别：错误**
 
-在TypeScript的catch语句中，只能标注类型为`any`或`unknown`。由于ArkTS不支持这些类型，应省略类型注释。
+在TypeScript的catch语句中，只能标注`any`或`unknown`类型。由于ArkTS不支持这些类型，应省略类型标注。
 
 **TypeScript**
 
@@ -2229,7 +2071,9 @@ let c1 = arr[2]
 try {
     // 一些代码
 }
-catch (a: unknown) {}
+catch (a: unknown) {
+    // 处理异常
+}
 ```
 
 **ArkTS**
@@ -2238,7 +2082,9 @@ catch (a: unknown) {}
 try {
     // 一些代码
 }
-catch (a) {}
+catch (a) {
+    // 处理异常
+}
 ```
 
 **相关约束**
@@ -2278,11 +2124,11 @@ for (let i = 0; i < a.length; ++i) {
 
 ### 不支持可迭代接口
 
-**规则：**`arkts-noiterable`
+**规则：**`arkts-no-iterable`
 
 **级别：错误**
 
-ArkTS不支持`Symbol` API、`Symbol.iterator`和最终可迭代的接口。请使用数组和标准库中的容器。
+ArkTS不支持`Symbol`API、`Symbol.iterator`和最终可迭代的接口。请使用数组和标准库中的容器。
 
 **相关约束**
 
@@ -2311,7 +2157,7 @@ for (let s of a) {
 
 ```typescript
 let a: Set<number> = new Set([1, 2, 3])
-let numbers = a.values()
+let numbers = Array.from(a.values())
 for (let n of numbers) {
     console.log(n)
 }
@@ -2364,6 +2210,22 @@ class CFlags {
 
 ArkTS不支持`with`语句。使用其他语法来表示相同的语义。
 
+**TypeScript**
+
+```typescript
+with (Math) { // 编译时错误, 但是仍能生成JavaScript代码
+    let r: number = 42
+    console.log("Area: ", PI * r * r)
+}
+```
+
+**ArkTS**
+
+```typescript
+let r: number = 42
+console.log("Area: ", Math.PI * r * r)
+```
+
 ### `case`语句仅支持编译期值
 
 **规则：**`arkts-no-computed-case`
@@ -2417,7 +2279,7 @@ switch (x) {
 
 **级别：错误**
 
-ArkTS支持`switch`语句中使用`number`, `Number`, `string`, `String` 或者`enum`类型的值。其他情况下请使用`if`语句。
+ArkTS支持`switch`语句中使用`number`, `Number`, `string`, `String`或者`enum`类型的值。其他情况下请使用`if`语句。
 
 **TypeScript**
 
@@ -2483,6 +2345,7 @@ ArkTS在部分场景中支持对函数返回类型进行推断。当`return`语
 **TypeScript**
 
 ```typescript
+// 只有在开启noImplicitAny选项时会产生编译时错误
 function f(x: number) {
     if (x <= 0) {
         return x
@@ -2490,6 +2353,7 @@ function f(x: number) {
     return g(x)
 }
 
+// 只有在开启noImplicitAny选项时会产生编译时错误
 function g(x: number) {
     return f(x - 1)
 }
@@ -2513,7 +2377,7 @@ function f(x: number) : number {
     return g(x)
 }
 
-// 需标注返回类型：
+// 可以省略返回类型，返回类型可以从f的类型标注推导得到
 function g(x: number) : number {
     return f(x - 1)
 }
@@ -2617,7 +2481,7 @@ ArkTS不支持在函数中使用`this`。只能在方法中使用`this`。
 
 ```typescript
 function foo(i: number) {
-    this.count = i
+    this.count = i // 只有在开启noImplicitThis选项时会产生编译时错误
 }
 
 class A {
@@ -2884,7 +2748,7 @@ console.log(p3d.x, p3d.y, p3d.z)
 
 ### 接口不能继承具有相同属性的两个接口
 
-**规则：**`arkts-no-extend-same-property`
+**规则：**`arkts-no-extend-same-prop`
 
 **级别：错误**
 
@@ -3051,7 +2915,7 @@ interface SelectableControl extends Control {
 
 **级别：错误**
 
-ArkTS中，对象布局在编译时就确定了，且不能在运行时被更改。禁止运行时检查对象属性。使用`as`运算符进行类型转换以读取相应的属性和方法。读取对象中不存在的属性将导致编译时错误。
+ArkTS中，对象布局在编译时就确定了，且不能在运行时被更改。禁止运行时检查对象属性。使用`as`运算符进行类型转换以访问相应的属性和方法。访问对象中不存在的属性将导致编译时错误。
 
 **TypeScript**
 
@@ -3096,7 +2960,7 @@ function main(): void {
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 不支持delete运算符
@@ -3203,7 +3067,7 @@ function main(): void {
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 不支持delete运算符
@@ -3323,25 +3187,6 @@ namespace MyNamespace {
 MyNamespace.x = 2
 ```
 
-### 脚本和模块
-
-**规则：**`arkts-no-scripts`
-
-**级别：错误**
-
-通常来说，ArkTS中的脚本和模块与TypeScript非常接近。它们的差异在另外的约束中描述。
-
-**相关约束**
-
-* 不支持import type
-* 不支持仅为副作用而导入一个模块
-* 不支持import default as ...
-* 不支持require
-* 不支持重命名导出
-* 不支持导出列表
-* 不支持重导出
-* 不支持通过export = ... 
-
 ### 不支持命名空间中的非声明语句
 
 **规则：**`arkts-no-ns-statements`
@@ -3386,23 +3231,23 @@ ArkTS不支持`import type`。改为`import`。
 
 ```typescript
 // 通用导入语法
-import { APIResponseType } from "./api"
+import { APIResponseType } from "api"
 
 // 导入类型
-import type { APIResponseType } from "./api"
+import type { APIResponseType } from "api"
 ```
 
 **ArkTS**
 
 ```typescript
-import { APIResponseType } from "./api"
+import { APIResponseType } from "api"
 ```
 
 **相关约束**
 
 * 不支持仅为副作用而导入一个模块
 * 不支持import default as ...
-* 不支持require
+* 不支持require和import赋值表达式
 
 ### 不支持仅为副作用而导入一个模块
 
@@ -3437,7 +3282,7 @@ import * from "path/to/module"
 
 **级别：错误**
 
-ArkTS不支持`import default as ...` 语法。使用显式的`import ... from ...` 语法。
+ArkTS不支持`import default as ...`语法。使用显式的`import ... from ...`语法。
 
 **TypeScript**
 
@@ -3451,13 +3296,13 @@ import { default as d } from "mod"
 import d from "mod"
 ```
 
-### 不支持`require` 
+### 不支持`require`和`import`赋值表达式
 
 **规则：**`arkts-no-require`
 
 **级别：错误**
 
-ArkTS不支持通过`require`导入。改用`import`。
+ArkTS不支持通过`require`导入，也不支持`import`赋值表达式。改用`import`。
 
 **TypeScript**
 
@@ -3471,110 +3316,34 @@ import m = require("mod")
 import * as m from "mod"
 ```
 
-### 不支持重命名导出
-
-**规则：**`arkts-no-export-renaming`
-
-**级别：错误**
-
-ArkTS不支持重命名导出。可以采用设置别名的方式。
-
-**TypeScript**
-
-```typescript
-// file1.ts
-class MyClass {
-    // ...
-}
-
-export { MyClass as RenamedClass }
-
-// file2.ts
-import { RenamedClass } from "./file1"
-
-function main(): void {
-    const myObject = new RenamedClass()
-    // ...
-}
-```
-
-**ArkTS**
-
-```typescript
-// module1
-class MyClass {
-    // ...
-}
-
-export type RenamedClass = MyClass
-
-// module2
-import { RenamedClass } from "./module1"
-
-function main(): void {
-    const myObject = new RenamedClass()
-    // ...
-}
-```
-
-**相关约束**
-
-* 不支持导出列表
-* 不支持重导出
-* 不支持通过export = ... 
-
-### 不支持导出列表
-
-**规则：**`arkts-no-export-list-decl`
-
-**级别：错误**
-
-ArkTS不支持导出列表的语法。使用`export`关键字显式导出每个值。
-
-**TypeScript**
-
-```typescript
-export { x }
-export { x } from "mod"
-export { x, y as b, z as c }
-```
-
-**ArkTS**
-
-```typescript
-let x = 1
-class MyClass {}
-export let y = x, z: number = 2
-export type RenamedClass = MyClass
-```
-
 **相关约束**
 
-* 不支持重命名导出
-* 不支持重导出
-* 不支持通过export = ... 
+* 不支持export = ...语法 
 
-### 不支持重导出
+### 部分支持重导出
 
-**规则：**`arkts-no-reexport`
+**规则：**`arkts-limited-reexport`
 
 **级别：错误**
 
-ArkTS不支持重导出。从导出模块显式导入。
+ArkTS支持大多数场景下的重导出，比如命名导出和重命名导出，重导出import的。不支持`export * as ...`。
 
 **TypeScript**
 
 ```typescript
 // module1
-export class MyClass {
+export class Class1 {
+    // ...
+}
+export class Class2 {
     // ...
 }
 
 // module2
-export { MyClass } from "module1"
+export * as utilities from "module1"
 
 // consumer模块
-import { MyClass } from "module2"
+import { utilities } from "module2"
 
 const myInstance = new MyClass()
 ```
@@ -3583,27 +3352,28 @@ const myInstance = new MyClass()
 
 ```typescript
 // module1
-export class MyClass {
+export class Class1 {
+    // ...
+}
+export class Class2 {
     // ...
 }
 
 // module2
-// some stuff
+export { Class1 } from "module1"
+export { C2 as Class2 } from "module1"
 
 // consumer模块
-import { MyClass } from "module1"
-import * from "module2"
+import { Class1, Class2 } from "module2"
 
 const myInstance = new MyClass()
 ```
 
 **相关约束**
 
-* 不支持重命名导出
-* 不支持导出列表
-* 不支持通过export = ... 
+* 不支持export = ...语法 
 
-### 不支持通过`export = ...`
+### 不支持`export = ...`语法
 
 **规则：**`arkts-no-export-assignment`
 
@@ -3645,9 +3415,8 @@ let p = Pt.origin
 
 **相关约束**
 
-* 不支持重命名导出
-* 不支持导出列表
-* 不支持重导出
+* 不支持require和import赋值表达式
+* 部分支持重导出
 
 ### 不支持`export type`
 **规则：**`arkts-no-special-exports`
@@ -3659,14 +3428,32 @@ ArkTS不支持`export type`。改用`export`。
 **TypeScript**
 
 ```typescript
-class C {}
-export type { C }
+// 显式导出class：
+export class Class1 {
+    // ...
+}
+
+// 声明一个类，之后通过`export type`导出
+class Class2 {
+    // ...
+}
+
+// 不支持
+export type { Class2 }
 ```
 
 **ArkTS**
 
 ```typescript
-export class C {}
+// 显式导出class：
+export class Class1 {
+    // ...
+}
+
+// 显式导出class：
+export class Class2 {
+    // ...
+}
 ```
 
 ### 不支持ambient module声明
@@ -3689,7 +3476,7 @@ declare module "someModule" {
 
 ```typescript
 // 从原始模块中导入需要的内容
-import { normalize } from "../someModule"
+import { normalize } from "someModule"
 ```
 
 **相关约束**
@@ -3708,10 +3495,25 @@ import { normalize } from "../someModule"
 **TypeScript**
 
 ```typescript
+// 声明
 declare module "*!text" {
     const content: string
     export default content
 }
+
+import fileContent from "some.txt!text"
+```
+
+**ArkTS**
+
+```typescript
+// 声明
+declare namespace N {
+    function foo(x: number): number
+}
+
+import * from "module"
+console.log("N.foo called: ", N.foo(42))
 ```
 
 **相关约束**
@@ -3748,7 +3550,7 @@ namespace mathLib {
 }
 
 // 程序中
-import { mathLib } from "./math-lib"
+import { mathLib } from "math-lib"
 mathLib.isPrime(2)
 ```
 
@@ -3767,13 +3569,13 @@ ArkTS不允许在模块标识符中使用`.js`扩展名，因为ArkTS本身有
 **TypeScript**
 
 ```typescript
-import { something } from "./module.js"
+import { something } from "module.js"
 ```
 
 **ArkTS**
 
 ```typescript
-import { something } from "./module"
+import { something } from "module"
 ```
 
 **相关约束**
@@ -3803,6 +3605,19 @@ class CustomError extends Error {
 }
 ```
 
+**ArkTS**
+
+```typescript
+class CustomError extends Error {
+    constructor(message?: string) {
+        // 调用父类构造函数，继承链是静态的，且不能在运行时被改变
+        super(message)
+        console.log(this instanceof Error) // true
+    }
+}
+let ce = new CustomError()
+```
+
 **相关约束**
 
 * 不支持在原型上赋值
@@ -3818,13 +3633,13 @@ class CustomError extends Error {
 **TypeScript**
 
 ```typescript
-const zipUtil = await import("./utils/create-zip-file")
+const zipUtil = await import("utils/create-zip-file")
 ```
 
 **ArkTS**
 
 ```typescript
-import { zipUtil } from "./utils/create-zip-file"
+import { zipUtil } from "utils/create-zip-file"
 ```
 
 **相关约束**
@@ -3867,7 +3682,7 @@ let x: number = initialize()
 console.log("x = " + x)
 ```
 
-### 不支持IIFE作为命名空间的声明
+### 不支持IIFE（立即调用函数表达式）作为命名空间的声明
 
 **规则：**`arkts-no-iife`
 
@@ -3879,9 +3694,10 @@ console.log("x = " + x)
 
 ```typescript
 var C = (function() {
-    function C(n) {
-        this.p = n
+    function C(n: number) {
+        this.p = n // 只有在开启noImplicitThis选项时会产生编译时错误
     }
+    C.staticProperty = 0
     return C
 })()
 C.staticProperty = 1
@@ -3907,7 +3723,7 @@ ArkTS没有原型的概念，因此不支持在原型上赋值。此特性不符
 
 ```typescript
 var C = function(p) {
-    this.p = p
+    this.p = p // 只有在开启noImplicitThis选项时会产生编译时错误
 }
 
 C.prototype = {
@@ -3916,8 +3732,22 @@ C.prototype = {
     }
 }
 
-C.prototype.q = function(r) {
-    return this.p === r
+C.prototype.q = function(r: number) {
+    return this.p == r
+}
+```
+
+**ArkTS**
+
+```typescript
+class C {
+    p: number = 0
+    m() {
+        console.log(this.p)
+    }
+    q(r: number) {
+        return this.p == r
+    }
 }
 ```
 
@@ -3939,7 +3769,7 @@ C.prototype.q = function(r) {
 // 全局文件中
 var abc = 100
 
-// 从上面引用'abc'。
+// 从上面引用'abc'
 globalThis.abc = 200
 ```
 
@@ -3950,7 +3780,7 @@ globalThis.abc = 200
 export let abc : number = 0
 
 // file2
-import * as M from "../file1"
+import * as M from "file1"
 
 M.abc = 200
 ```
@@ -3960,13 +3790,16 @@ M.abc = 200
 * 不支持声明函数的属性
 * 标准库使用限制
 
-### 不支持utility类型
+### 不支持一些utility类型
 
 **规则：**`arkts-no-utility-types`
 
 **级别：错误**
 
-当前ArkTS不支持从TypeScript扩展到标准库的utility类型（例如`Omit`、`Partial`、`Readonly`、`Record`、`Pick`等)。
+当前ArkTS不支持从TypeScript扩展到标准库的utility类型（例如`Omit`、`Pick`等）。支持`Partial`和`Record`。
+
+对于*Record<K, V>*类型，表达式*rec[index]*的类型是*V | undefined*。
+对于`Record`类型，键-值中的值的类型必须是可选类型或者包含`undefined`的联合类型。
 
 **TypeScript**
 
@@ -3978,20 +3811,55 @@ type Person = {
 }
 
 type QuantumPerson = Omit<Person, "location">
+
+let persons : Record<string, Person> = {
+    "Alice": {
+        name: "Alice",
+        age: 32,
+        location: "Shanghai"
+    },
+    "Bob": {
+        name: "Bob",
+        age: 48,
+        location: "New York"
+    }
+}
+console.log(persons["Bob"].age)
+console.log(persons["Rob"].age) // 运行时异常
 ```
 
 **ArkTS**
 
 ```typescript
 class Person {
-    name: string
-    age: number
-    location: string
+    name: string = ""
+    age: number = 0
+    location: string = ""
 }
 
 class QuantumPerson {
-    name: string
-    age: number
+    name: string = ""
+    age: number = 0
+}
+
+type OptionalPerson = Person | undefined
+let persons : Record<string, OptionalPerson> = {
+// 或者
+// let persons : Record<string, Person | undefined> = {
+    "Alice": {
+        name: "Alice",
+        age: 32,
+        location: "Shanghai"
+    },
+    "Bob": {
+        name: "Bob",
+        age: 48,
+        location: "New York"
+    }
+}
+console.log(persons["Bob"]!.age)
+if (persons["Rob"]) { // 值检查，不会运行时抛异常
+    console.log(persons["Rob"].age)
 }
 ```
 
@@ -4038,15 +3906,15 @@ class MyImage {
     // ...
 }
 
-function readImage(
+async function readImage(
     path: string, callback: (err: Error, image: MyImage) => void
 ) : Promise<MyImage>
 {
-    // 异步实现
+    return await new MyImage()
 }
 
 function readImageSync(path: string) : MyImage {
-    // 同步实现
+    return new MyImage()
 }
 ```
 
@@ -4165,7 +4033,7 @@ let x : string = "hello"
 let y : number[] = [10, 20]
 
 class Label {
-    text : string
+    text : string = ""
 }
 
 // 'Label'类型
@@ -4185,14 +4053,14 @@ let z : Label = {
 **TypeScript**
 
 ```typescript
-import { obj } from "./something.json" assert { type: "json" }
+import { obj } from "something.json" assert { type: "json" }
 ```
 
 **ArkTS**
 
 ```typescript
 // 编译时将检查导入T的正确性
-import { something } from "./module"
+import { something } from "module"
 ```
 
 **相关约束**
@@ -4241,7 +4109,7 @@ ArkTS不允许使用TypeScript或JavaScript标准库中的某些接口。大部
 
 **相关约束**
 
-* 仅支持属性名称为标识符的对象
+* 对象的属性名必须是合法的标识符
 * 不支持Symbol() API
 * 访问未定义的属性将导致编译时错误
 * 仅允许在表达式中使用typeof运算符
@@ -4249,3 +4117,153 @@ ArkTS不允许使用TypeScript或JavaScript标准库中的某些接口。大部
 * 禁止运行时检查对象属性
 * 不支持声明动态属性
 * 不支持globalThis
+
+### 强制开启严格类型检查
+
+**规则 `arkts-strict-typing`**
+
+**级别：错误**
+
+在ArkTS中，以下TypeScript的严格类型检查选项必须打开：`noImplicitReturns`,
+`strictFunctionTypes`, `strictNullChecks`, `strictPropertyInitialization`。
+
+**TypeScript**
+
+```typescript
+class C {
+    n: number // 只有在开启strictPropertyInitialization选项时会产生编译时错误
+    s: string // 只有在开启strictPropertyInitialization选项时会产生编译时错误
+}
+
+// 只有在开启noImplicitReturns选项时会产生编译时错误
+function foo(s: string): string {
+    if (s != "") {
+        console.log(s)
+        return s
+    } else {
+        console.log(s)
+    }
+}
+
+let n: number = null // 只有在开启strictNullChecks选项时会产生编译时错误
+```
+
+**ArkTS**
+
+```typescript
+class C {
+    n: number = 0
+    s: string = ""
+}
+
+function foo(s: string): string {
+    console.log(s)
+    return s
+}
+
+let n1: number | null = null
+let n2: number = 0
+```
+
+**相关约束**
+
+* 使用具体的类型而非any或unknown
+* 不允许通过注释关闭类型检查
+
+### 不允许通过注释关闭类型检查
+
+**规则 `arkts-strict-typing-required`**
+
+**级别：错误**
+
+在ArkTS中，类型检查不是可选项。不允许通过注释关闭类型检查，不支持使用`@ts-ignore`和`@ts-nocheck`。
+
+**TypeScript**
+
+```typescript
+// @ts-nocheck
+// ...
+// 关闭了类型检查后的代码
+// ...
+
+let s1: string = null // 没有报错
+
+// @ts-ignore
+let s2: string = null // 没有报错
+```
+
+**ArkTS**
+
+```typescript
+let s1: string | null = null // 没有报错，合适的类型
+let s2: string = null // 编译时报错
+```
+
+**相关约束**
+
+* 使用具体的类型而非any或unknown
+* 强制开启严格类型检查
+
+### 允许ArkTS代码导入TS代码, 不允许TS代码导入ArkTS代码
+
+**规则 `arkts-no-ts-deps`**
+
+**级别：错误**
+
+ArkTS中的代码可以导入来自标准TypeScript的代码，而标准TypeScript的代码不能导入来自ArkTS中的代码。
+
+**TypeScript**
+
+```typescript
+// app.ets
+export class C {
+    // ...
+}
+
+// lib.ts
+import { C } from "app"
+```
+
+**ArkTS**
+
+```typescript
+// lib1.ets
+export class C {
+    // ...
+}
+
+// lib2.ets
+import { C } from "lib1"
+```
+
+### 除了ArkUI中的装饰器，不允许使用其他装饰器
+
+**规则 `arkts-no-decorators-except-arkui`**
+
+**级别：错误**
+
+现在，ArkTS中只支持ArkUI中的装饰器。使用其他装饰器会造成编译时错误。
+
+**TypeScript**
+
+```typescript
+function classDecorator(x: number, y: number): void {
+    //
+}
+
+@classDecorator
+class BugReport {
+}
+```
+
+**ArkTS**
+
+```typescript
+function classDecorator(x: number, y: number): void {
+    //
+}
+
+@classDecorator // 编译时错误
+class BugReport {
+}
+```

zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityConstant.md

@@ -39,7 +39,7 @@ Ability初次启动原因，该类型为枚举，可配合[Ability](js-apis-app-
 | CALL | 2    | 通过[startAbilityByCall](js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartabilitybycall)接口启动ability。 |
 | CONTINUATION           | 3    | 跨端设备迁移启动ability。 |
 | APP_RECOVERY           | 4    | 设置应用恢复后，应用故障时自动恢复启动ability。 |
-| SHARE<sup>10+</sup>           | 5    | 通过[acquireShareData](js-apis-app-ability-abilityManager.md#acquiresharedata)接口启动ability。 |
+| SHARE<sup>10+</sup>           | 5    | 通过原子化服务分享启动ability。 |
 
 **示例：**
 

zh-cn/application-dev/reference/apis/js-apis-app-ability-uiAbility.md

@@ -332,9 +332,7 @@ import AbilityConstant from '@ohos.app.ability.AbilityConstant';
 class MyUIAbility extends UIAbility {
     onShare(wantParams) {
         console.log('onShare');
-        wantParams['ohos.extra.param.key.contentTitle'] = 'shareFeatureAbility';
-        wantParams['ohos.extra.param.key.shareAbstract'] = 'huawei employee';
-        wantParams['ohos.extra.param.key.shareUrl'] = 'w3.huawei.com';
+        wantParams['ohos.extra.param.key.shareUrl'] = 'example.com';
     }
 }
   ```

zh-cn/application-dev/reference/apis/js-apis-media.md

@@ -365,8 +365,8 @@ Audio/Video播放demo可参考：[音频播放开发指导](../../media/using-av
 | loop<sup>9+</sup>                                   | boolean                                                      | 是   | 是   | 视频循环播放属性，默认'false'，设置为'true'表示循环播放，动态属性。<br/>只允许在**prepared**/**playing**/**paused**/**completed**状态下设置。<br/>直播场景不支持loop设置。 |
 | videoScaleType<sup>9+</sup>                         | [VideoScaleType](#videoscaletype9)                           | 是   | 是   | 视频缩放模式，默认VIDEO_SCALE_TYPE_FIT_CROP，动态属性。<br/>只允许在**prepared**/**playing**/**paused**/**completed**状态下设置。 |
 | audioInterruptMode<sup>9+</sup>                     | [audio.InterruptMode](js-apis-audio.md#interruptmode9)       | 是   | 是   | 音频焦点模型，默认SHARE_MODE，动态属性。<br/>只允许在**prepared**/**playing**/**paused**/**completed**状态下设置。 |
-| audioRendererInfo<sup>10+</sup>                     | [audio.AudioRendererInfo](js-apis-audio.md#audiorendererinfo8) | 是   | 是   | 设置音频渲染信息，默认值contentType为CONTENT_TYPE_MUSIC，streamUsage为STREAM_USAGE_MEDIA。<br/>只允许在**initialized**状态下设置 |
-| audioEffectMode<sup>10+</sup>                       | [audio.AudioEffectMode](js-apis-audio.md#audioeffectmode10)  | 是   | 是   | 设置音频音效模式，默认值为EFFECT_DEFAULT，动态属性。audioRendererInfo的contentType和streamUsage变动时会恢复为默认值，只允许在**prepared**/**playing**/**paused**/**completed**状态下设置。 |
+| audioRendererInfo<sup>10+</sup>                     | [audio.AudioRendererInfo](js-apis-audio.md#audiorendererinfo8) | 是   | 是   | 设置音频渲染信息，默认值content为CONTENT_TYPE_MUSIC，usage为STREAM_USAGE_MEDIA，rendererFlags为0。<br/>只允许在**initialized**状态下设置 |
+| audioEffectMode<sup>10+</sup>                       | [audio.AudioEffectMode](js-apis-audio.md#audioeffectmode10)  | 是   | 是   | 设置音频音效模式，默认值为EFFECT_DEFAULT，动态属性。audioRendererInfo的content和usage变动时会恢复为默认值，只允许在**prepared**/**playing**/**paused**/**completed**状态下设置。 |
 | state<sup>9+</sup>                                  | [AVPlayerState](#avplayerstate9)                             | 是   | 否   | 音视频播放的状态，全状态有效，可查询参数。                   |
 | currentTime<sup>9+</sup>                            | number                                                       | 是   | 否   | 视频的当前播放位置，单位为毫秒（ms），可查询参数。<br/>返回为(-1)表示无效值，**prepared**/**playing**/**paused**/**completed**状态下有效。<br/>直播场景默认返回(-1)。 |
 | duration<sup>9+</sup><a name=avplayer_duration></a> | number                                                       | 是   | 否   | 视频时长，单位为毫秒（ms），可查询参数。<br/>返回为(-1)表示无效值，**prepared**/**playing**/**paused**/**completed**状态下有效。<br/>直播场景默认返回(-1)。 |

zh-cn/application-dev/reference/apis/js-apis-mindSporeLite.md

@@ -408,7 +408,7 @@ syscontext.resourceManager.getRawFileContent(inputName).then(async (buffer) => {
   let mindSporeLiteModel = await mindSporeLite.loadModelFromFile(model_file);
   const modelInputs = mindSporeLiteModel.getInputs();
   modelInputs[0].setData(inputBuffer.buffer);
-  result.predict(modelInputs, (result) => {
+  mindSporeLiteModel.predict(modelInputs, (result) => {
     let output = new Float32Array(result[0].getData());
     for (let i = 0; i < output.length; i++) {
       console.log(output[i].toString());
@@ -448,7 +448,7 @@ syscontext.resourceManager.getRawFileContent(inputName).then(async (buffer) => {
   let mindSporeLiteModel = await mindSporeLite.loadModelFromFile(model_file);
   const modelInputs = mindSporeLiteModel.getInputs();
   modelInputs[0].setData(inputBuffer.buffer);
-  result.predict(modelInputs).then((result) => {
+  mindSporeLiteModel.predict(modelInputs).then((result) => {
     let output = new Float32Array(result[0].getData());
     for (let i = 0; i < output.length; i++) {
       console.log(output[i].toString());
@@ -549,7 +549,7 @@ syscontext.resourceManager.getRawFileContent(inputName).then(async (buffer) => {
   let mindSporeLiteModel = await mindSporeLite.loadModelFromFile(model_file);
   const modelInputs = mindSporeLiteModel.getInputs();
   modelInputs[0].setData(inputBuffer.buffer);
-  result.predict(modelInputs).then((result) => {
+  mindSporeLiteModel.predict(modelInputs).then((result) => {
     let output = new Float32Array(result[0].getData());
     for (let i = 0; i < output.length; i++) {
       console.log(output[i].toString());
@@ -579,7 +579,7 @@ import resourceManager from '@ohos.resourceManager'
 let inputName = 'input_data.bin';
 let syscontext = globalThis.context;
 syscontext.resourceManager.getRawFileContent(inputName).then(async (buffer) => {
-  inputBuffer = buffer;
+  let inputBuffer = buffer;
   let model_file = '/path/to/xxx.ms';
   let mindSporeLiteModel = await mindSporeLite.loadModelFromFile(model_file);
   const modelInputs = mindSporeLiteModel.getInputs();

zh-cn/application-dev/reference/apis/js-apis-net-mdns.md

@@ -718,6 +718,41 @@ discoveryService.on('discoveryStart', (data) => {
 discoveryService.stopSearchingMDNS();
 ```
 
+### off('discoveryStart')<sup>10+</sup>
+
+off(type: 'discoveryStart', callback?: Callback<{ serviceInfo: LocalServiceInfo, errorCode?: MdnsError }>): void;
+
+取消开启监听mDNS服务的通知。
+
+**系统能力**：SystemCapability.Communication.NetManager.MDNS
+
+**参数：**
+
+| 参数名        | 类型                             | 必填 | 说明                                     |
+|-------------|--------------|-----------|-----------------------------------------------------|
+| type     | string                          | 是       |取消订阅的事件，固定为'discoveryStart'。<br>discoveryStart：开始搜索局域网内的mDNS服务事件。 |
+| callback | Callback<{serviceInfo: [LocalServiceInfo](#localserviceinfo), errorCode?: [MdnsError](#mdnserror)}>                  | 是        |   mDNS服务的信息和事件错误信息。      |
+
+**示例：**
+
+```js
+// 参考mdns.createDiscoveryService
+let context = globalThis.context;
+let serviceType = "_print._tcp";
+let discoveryService = mdns.createDiscoveryService(context, serviceType);
+discoveryService.startSearchingMDNS();
+
+discoveryService.on('discoveryStart', (data) => {
+  console.log(JSON.stringify(data));
+});
+
+discoveryService.stopSearchingMDNS();
+
+discoveryService.off('discoveryStart', (data) => {
+  console.log(JSON.stringify(data));
+});
+```
+
 ### on('discoveryStop')<sup>10+</sup>
 
 on(type: 'discoveryStop', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void
@@ -749,6 +784,41 @@ discoveryService.on('discoveryStop', (data) => {
 discoveryService.stopSearchingMDNS();
 ```
 
+### off('discoveryStop')<sup>10+</sup>
+
+off(type: 'discoveryStop', callback: Callback<{serviceInfo: LocalServiceInfo, errorCode?: MdnsError}>): void
+
+取消订阅停止监听mDNS服务的通知。
+
+**系统能力**：SystemCapability.Communication.NetManager.MDNS
+
+**参数：**
+
+| 参数名        | 类型                             | 必填 | 说明                                     |
+|-------------|--------------|-----------|-----------------------------------------------------|
+| type     | string                          | 是       |取消订阅的事件'discoveryStop'。<br>discoveryStop：停止搜索局域网内的mDNS服务事件。 |
+| callback | Callback<{serviceInfo: [LocalServiceInfo](#localserviceinfo), errorCode?: [MdnsError](#mdnserror)}>                 | 是        |   mDNS服务的信息和事件错误信息。      |
+
+**示例：**
+
+```js
+// 参考mdns.createDiscoveryService
+let context = globalThis.context;
+let serviceType = "_print._tcp";
+let discoveryService = mdns.createDiscoveryService(context, serviceType);
+discoveryService.startSearchingMDNS();
+
+discoveryService.on('discoveryStop', (data) => {
+  console.log(JSON.stringify(data));
+});
+
+discoveryService.stopSearchingMDNS();
+
+discoveryService.off('discoveryStop', (data) => {
+  console.log(JSON.stringify(data));
+});
+```
+
 ### on('serviceFound')<sup>10+</sup>
 
 on(type: 'serviceFound', callback: Callback\<LocalServiceInfo>): void
@@ -780,6 +850,41 @@ discoveryService.on('serviceFound', (data) => {
 discoveryService.stopSearchingMDNS();
 ```
 
+### off('serviceFound')<sup>10+</sup>
+
+off(type: 'serviceFound', callback: Callback\<LocalServiceInfo>): void
+
+取消订阅发现mDNS服务的通知。
+
+**系统能力**：SystemCapability.Communication.NetManager.MDNS
+
+**参数：**
+
+| 参数名        | 类型                             | 必填 | 说明                                     |
+|-------------|--------------|-----------|-----------------------------------------------------|
+| type     | string                          | 是       |取消订阅的事件，固定为'serviceFound'。<br>serviceFound：发现mDNS服务事件。 |
+| callback | Callback<[LocalServiceInfo](#localserviceinfo)>                 | 是        |   mDNS服务的信息。      |
+
+**示例：**
+
+```js
+// 参考mdns.createDiscoveryService
+let context = globalThis.context;
+let serviceType = "_print._tcp";
+let discoveryService = mdns.createDiscoveryService(context, serviceType);
+discoveryService.startSearchingMDNS();
+
+discoveryService.on('serviceFound', (data) => {
+  console.log(JSON.stringify(data));
+});
+
+discoveryService.stopSearchingMDNS();
+
+discoveryService.off('serviceFound', (data) => {
+  console.log(JSON.stringify(data));
+});
+```
+
 ### on('serviceLost')<sup>10+</sup>
 
 on(type: 'serviceLost', callback: Callback\<LocalServiceInfo>): void
@@ -811,6 +916,41 @@ discoveryService.on('serviceLost', (data) => {
 discoveryService.stopSearchingMDNS();
 ```
 
+### off('serviceLost')<sup>10+</sup>
+
+off(type: 'serviceLost', callback: Callback\<LocalServiceInfo>): void
+
+取消订阅移除mDNS服务的通知。
+
+**系统能力**：SystemCapability.Communication.NetManager.MDNS
+
+**参数：**
+
+| 参数名        | 类型                             | 必填 | 说明                                     |
+|-------------|--------------|-----------|-----------------------------------------------------|
+| type     | string                          | 是       |取消订阅的事件，固定为'serviceLost'。<br>serviceLost：移除mDNS服务事件。 |
+| callback | Callback<[LocalServiceInfo](#localserviceinfo)>   | 是        |   mDNS服务的信息。      |
+
+**示例：**
+
+```js
+// 参考mdns.createDiscoveryService
+let context = globalThis.context;
+let serviceType = "_print._tcp";
+let discoveryService = mdns.createDiscoveryService(context, serviceType);
+discoveryService.startSearchingMDNS();
+
+discoveryService.on('serviceLost', (data) => {
+  console.log(JSON.stringify(data));
+});
+
+discoveryService.stopSearchingMDNS();
+
+discoveryService.off('serviceLost', (data) => {
+  console.log(JSON.stringify(data));
+});
+```
+
 ## LocalServiceInfo<sup>10+</sup>
 
 mDNS服务信息

zh-cn/application-dev/reference/apis/js-apis-socket.md

@@ -2515,7 +2515,7 @@ tcpServer.on('connect', function(client) {
 
 ### off('close')<sup>10+</sup>
 
-on(type: 'close', callback: Callback\<void\>): void
+off(type: 'close', callback?: Callback<void>): void
 
 取消订阅TCPSocketConnection的关闭事件。使用callback方式作为异步方法。
 
@@ -5706,7 +5706,7 @@ tlsServer.on('connect', function(client) {
 
 ### off('close')<sup>10+</sup>
 
-on(type: 'close', callback: Callback\<void\>): void
+off(type: 'close', callback?: Callback<void>): void
 
 取消订阅TLSSocketConnection的关闭事件。使用callback方式作为异步方法。
 

zh-cn/application-dev/website.md

@@ -147,7 +147,6 @@
           - [跨端迁移](application-models/hop-cross-device-migration.md)
           - [多端协同（仅对系统应用开放）](application-models/hop-multi-device-collaboration.md)
         - [订阅系统环境变量的变化](application-models/subscribe-system-environment-variable-changes.md)
-        - [原子化服务支持分享](application-models/atomic-services-support-sharing.md)
       - 了解进程模型
         - [进程模型概述](application-models/process-model-stage.md)
         - 公共事件