diff --git a/en/application-dev/quick-start/arkts-state.md b/en/application-dev/quick-start/arkts-state.md
index be3260d6855bdb72a8e38fbaea31307117ec091b..325940b1640224b5bf47fbfe4fc898c6125fa1a3 100644
--- a/en/application-dev/quick-start/arkts-state.md
+++ b/en/application-dev/quick-start/arkts-state.md
@@ -30,14 +30,14 @@ An @State decorated variable, like all other decorated variables in the declarat
 | Decorator parameters       | None.                                       |
 | Synchronization type        | Does not synchronize with any type of variable in the parent component.                        |
 | Allowed variable types   | Object, class, string, number, Boolean, enum, and array of these types. For details about the scenarios of nested types, see [Observed Changes](#observed-changes).<br>The type must be specified.<br>**any** is not supported. A combination of simple and complex types is not supported. The **undefined** and **null** values are not allowed.<br>**NOTE**<br>Avoid using this decorator to decorate the Date type, as doing so may lead to unexpected behavior of the application.<br>The Length, ResourceStr, and ResourceColor types are a combination of simple and complex types and therefore not supported.|
-| Initial value for the decorated variable   | Mandatory.                                   |
+| Initial value for the decorated variable| Local initialization is required.                                              |
 
 
 ## Variable Transfer/Access Rules
 
 | Transfer/Access    | Description                                      |
 | --------- | ---------------------------------------- |
-| Initialization from the parent component  | Optional. Initialization from the parent component or local initialization can be used.<br>An \@State decorated variable can be initialized from a regular variable or an \@State, \@Link, \@Prop, \@Provide, \@Consume, \@ObjectLink, \@StorageLink, \@StorageProp, \@LocalStorageLink, or \@LocalStorageProp decorated variable in its parent component.|
+| Initialization from the parent component    | Optional. Initialization from the parent component or local initialization can be used. The initial value specified in the parent component will overwrite the one defined locally.<br>An \@State decorated variable can be initialized from a regular variable or an \@State, \@Link, \@Prop, \@Provide, \@Consume, \@ObjectLink, \@StorageLink, \@StorageProp, \@LocalStorageLink, or \@LocalStorageProp decorated variable in its parent component.|
 | Subnode initialization | Supported. An \@State decorated variable can be used to initialize a regular variable or \@State, \@Link, \@Prop, or \@Provide decorated variable in the child component.|
 | Access| Private, accessible only within the component.                           |
 
diff --git a/en/application-dev/reference/apis/js-apis-inputmethod-subtype.md b/en/application-dev/reference/apis/js-apis-inputmethod-subtype.md
index 3a044ea0a5a6558cc3b5f1dff3ff5918cd955fd1..68b5085ef1462efac95e2e44cfc2daa9d2e239fc 100644
--- a/en/application-dev/reference/apis/js-apis-inputmethod-subtype.md
+++ b/en/application-dev/reference/apis/js-apis-inputmethod-subtype.md
@@ -16,14 +16,14 @@ import InputMethodSubtype from '@ohos.InputMethodSubtype';
 
  **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
-| Name| Type| Readable| Writable| Mandatory| Description|
-| -------- | -------- | -------- | -------- | -------- | -------- |
-| label | string | Yes| No| No| Label of the input method subtype.|
-| name | string | Yes| No| Yes| Bundle name of the input method. |
-| id | string | Yes| No| Yes| ID of the input method subtype.|
-| mode | string | Yes| No| No| Mode of the input method subtype, including **upper** (uppercase) and **lower** (lowercase).|
-| locale | string | Yes| No| Yes| Locale of the input method subtype.|
-| language | string | Yes| No| Yes| Language of the input method subtype.|
-| icon | string | Yes| No| No| Icon of the input method subtype.|
-| iconId | number | Yes| No| No| Icon ID of the input method subtype.|
-| extra | object | Yes| Yes| Yes| Extra information of the input method subtype.|
+| Name| Type| Readable| Writable| Description|
+| -------- | -------- | -------- | -------- | -------- |
+| label | string | Yes| No| Optional. Label of the input method subtype.|
+| name | string | Yes| No| Mandatory. Bundle name of the input method.|
+| id | string | Yes| No| Mandatory. ID of the input method subtype.|
+| mode | string | Yes| No| Optional. Mode of the input method subtype, including **upper** (uppercase) and **lower** (lowercase).|
+| locale | string | Yes| No| Mandatory. Locale of the input method subtype.|
+| language | string | Yes| No| Mandatory. Language of the input method subtype.|
+| icon | string | Yes| No| Optional. Icon of the input method subtype.|
+| iconId | number | Yes| No| Optional. Icon ID of the input method subtype.|
+| extra | object | Yes| Yes| Mandatory. Extra information of the input method subtype.|
diff --git a/en/application-dev/reference/apis/js-apis-notificationManager.md b/en/application-dev/reference/apis/js-apis-notificationManager.md
index 0c136cad2373439709255dea4e829b5d3ec1eb7c..e42595bb358245fae6c627a2a10042c775f07ccd 100644
--- a/en/application-dev/reference/apis/js-apis-notificationManager.md
+++ b/en/application-dev/reference/apis/js-apis-notificationManager.md
@@ -100,7 +100,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 ```js
 // NotificationRequest object
 let notificationRequest = {
-    notificationId: 1,
+    id: 1,
     content: {
         contentType: Notification.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
         normal: {
diff --git a/en/application-dev/reference/apis/js-apis-webview.md b/en/application-dev/reference/apis/js-apis-webview.md
index d5a7c70f6d3f05b7ade664eb2cad3e45d9293091..aa09e7c8356b1cb99b0831f18de472e8c88cd5f9 100644
--- a/en/application-dev/reference/apis/js-apis-webview.md
+++ b/en/application-dev/reference/apis/js-apis-webview.md
@@ -694,7 +694,7 @@ struct WebComponent {
 
 onActive(): void
 
-Invoked to instruct the **\<Web>** component to enter the foreground, active state.
+Invoked to instruct the **\<Web>** component to enter the active foreground state.
 
 **System capability**: SystemCapability.Web.Webview.Core
 
@@ -1043,12 +1043,14 @@ HTML file to be loaded:
 <html>
     <meta charset="utf-8">
     <body>
-        Hello world!
+      <button type="button" onclick="htmlTest()">Click Me!</button>
+      <p id="demo"></p>
     </body>
     <script type="text/javascript">
     function htmlTest() {
-        str = objName.test("test function")
-        console.log('objName.test result:'+ str)
+      let str=objName.test();
+      document.getElementById("demo").innerHTML=str;
+      console.log('objName.test result:'+ str)
     }
 </script>
 </html>
diff --git a/en/application-dev/reference/arkui-ts/ts-basic-components-search.md b/en/application-dev/reference/arkui-ts/ts-basic-components-search.md
index e79244d086eba8de02a138bff039dd05245f19b3..21c1d227fa8f87a6d7ed078be9d22375bec2ebc7 100644
--- a/en/application-dev/reference/arkui-ts/ts-basic-components-search.md
+++ b/en/application-dev/reference/arkui-ts/ts-basic-components-search.md
@@ -12,7 +12,7 @@ Not supported
 
 ## APIs
 
-Search(options?: { value?: string; placeholder?: string; icon?: string; controller?: SearchController })
+Search(options?: { value?: string, placeholder?: string, icon?: string, controller?: SearchController })
 
 **Parameters**
 
diff --git a/en/application-dev/web/web-in-page-app-function-invoking.md b/en/application-dev/web/web-in-page-app-function-invoking.md
index a06af719f81d23cb8bb9a961ed520a0413f5ed02..21d30949a5b85fbfbc72869c216a3f394e63636d 100644
--- a/en/application-dev/web/web-in-page-app-function-invoking.md
+++ b/en/application-dev/web/web-in-page-app-function-invoking.md
@@ -89,7 +89,7 @@ The following example registers the **test()** function with the frontend page.
 
   > **NOTE**
   >
-  > If you use [registerJavaScriptProxy()](../reference/apis/js-apis-webview.md#registerjavascriptproxy) to register a function, call **[refresh()]**(../reference/apis/js-apis-webview.md#refresh) for the function to take effect.
+  > If you use [registerJavaScriptProxy()](../reference/apis/js-apis-webview.md#registerjavascriptproxy) to register a function, call [refresh()](../reference/apis/js-apis-webview.md#refresh) for the function to take effect.
 
 
 - Sample code for invoking application functions on the **index.htm** page:
@@ -103,7 +103,7 @@ The following example registers the **test()** function with the frontend page.
   <p id="demo"></p>
   <script>
       function callArkTS() {
-          let str = testObjName.test();
+          let str = objName.test();
           document.getElementById("demo").innerHTML = str;
           console.info('ArkTS Hello World! :' + str);
       }
diff --git a/en/device-dev/device-test/Readme-EN.md b/en/device-dev/device-test/Readme-EN.md
index 4ca9e2c13290f008cf73f231874cf598cb1edc0b..fdc39eacf45c3bf7f5af22ecc5a7db4e24612908 100644
--- a/en/device-dev/device-test/Readme-EN.md
+++ b/en/device-dev/device-test/Readme-EN.md
@@ -2,5 +2,5 @@
 
 - [Development Self-Test Framework User Guide](developer_test.md)
 - [xDevice User Guide](xdevice.md)
-- [XTS Test Case Development Guide](xts.md)
-
+- [Smartperf-Host User Guide](smartperf-host.md)
+- [XTS](xts.md)
diff --git a/en/device-dev/device-test/smartperf-host.md b/en/device-dev/device-test/smartperf-host.md
index ec92a1ba4c2c5ca57957702de1e9fe9c8cb54c9c..6f8451539b9e7bde43dbe79029138508f520d809 100644
--- a/en/device-dev/device-test/smartperf-host.md
+++ b/en/device-dev/device-test/smartperf-host.md
@@ -1,4 +1,4 @@
-# Smartperf-Host
+# Smartperf-Host User Guide
 ## Overview
 Smartperf-Host is an intuitive performance and power optimization tool that offers in-depth data mining and fine-grained data visualization. In this tool, you can gain visibility into a multitude of metrics in terms of CPU scheduling, frequency, process and thread time slices, heap memory, frame rate, and more, in swimlanes. Better yet, you can analyze the collected data intuitively on the GUI.
 ## Architecture
diff --git a/en/device-dev/kernel/kernel-mini-memory-perf.md b/en/device-dev/kernel/kernel-mini-memory-perf.md
deleted file mode 100644
index 95d097792307376342a55eefcfde96f7f921952b..0000000000000000000000000000000000000000
--- a/en/device-dev/kernel/kernel-mini-memory-perf.md
+++ /dev/null
@@ -1,449 +0,0 @@
-# perf
-
-
-## Basic Concepts
-
-perf is a performance analysis tool. It uses the performance monitoring unit (PMU) to count sampling events and collect context information and provides hot spot distribution and hot paths.
-
-
-## Working Principles
-
-When a performance event occurs, the corresponding event counter overflows and triggers an interrupt. The interrupt handler records the event information, including the current PC, task ID, and call stack.
-
-perf provides two working modes: counting mode and sampling mode.
-
-In counting mode, perf collects only the number of event occurrences and duration. In sampling mode, perf also collects context data and stores the data in a circular buffer. The IDE then analyzes the data and provides information about hotspot functions and paths.
-
-
-## Available APIs
-
-
-### Kernel Mode
-
-The Perf module of the OpenHarmony LiteOS-A kernel provides the following functions. For details about the interfaces, see the [API reference](https://gitee.com/openharmony/kernel_liteos_a/blob/master/kernel/include/los_perf.h).
-
-  **Table 1** APIs of the perf module
-
-| API| Description|
-| -------- | -------- |
-| LOS_PerfStart| Starts sampling.|
-| LOS_PerfStop| Stops sampling.|
-| LOS_PerfConfig| Sets the event type and sampling interval.|
-| LOS_PerfDataRead| Reads the sampling data.|
-| LOS_PerfNotifyHookReg| Registers the hook to be called when the buffer waterline is reached.|
-| LOS_PerfFlushHookReg| Registers the hook for flushing the cache in the buffer.|
-
-- The structure of the perf sampling event is **PerfConfigAttr**. For details, see **kernel\include\los_perf.h**.
-
-- The sampling data buffer is a circular buffer, and only the region that has been read in the buffer can be overwritten.
-
-- The buffer has limited space. You can register a hook to provide a buffer overflow notification or perform buffer read operation when the buffer waterline is reached. The default buffer waterline is 1/2 of the buffer size. 
-
-   Example:
-
-   ```
-   VOID Example_PerfNotifyHook(VOID)
-   {
-       CHAR buf[LOSCFG_PERF_BUFFER_SIZE] = {0};
-       UINT32 len;
-       PRINT_DEBUG("perf buffer reach the waterline!\n");
-       len = LOS_PerfDataRead(buf, LOSCFG_PERF_BUFFER_SIZE);
-       OsPrintBuff(buf, len); /* print data */
-   }
-   LOS_PerfNotifyHookReg(Example_PerfNotifyHook);
-   ```
-
-- If the buffer sampled by perf involves caches across CPUs, you can register a hook for flushing the cache to ensure cache consistency. 
-
-   Example:
-
-   ```
-   VOID Example_PerfFlushHook(VOID *addr, UINT32 size)
-   {
-       OsCacheFlush(addr, size); /* platform interface */
-   }
-   LOS_PerfNotifyHookReg(Example_PerfFlushHook);
-   ```
-
-   The API for flushing the cache is configured based on the platform.
-
-
-### User Mode
-
-
-The perf character device is located in **/dev/perf**. You can read, write, and control the user-mode perf by running the following commands on the device node:
-
-
-- **read**: reads perf data in user mode.
-
-- **write**: writes user-mode sampling events.
-
-- **ioctl**: controls the user-mode perf, which includes the following:
-  
-  ```
-  #define PERF_IOC_MAGIC     'T'
-  #define PERF_START         _IO(PERF_IOC_MAGIC, 1)
-  #define PERF_STOP          _IO(PERF_IOC_MAGIC, 2)
-  ```
-
-  The operations correspond to **LOS_PerfStart** and **LOS_PerfStop**.
-
-
-For details, see [User-Mode Development Example](#user-mode-development-example).
-
-
-## How to Develop
-
-
-### Kernel-Mode Development Process
-
-The typical process of enabling perf is as follows:
-
-1. Configure the macros related to the perf module.
-   
-   Configure the perf control macro **LOSCFG_KERNEL_PERF**, which is disabled by default. In the **kernel/liteos_a** directory, run the **make update_config** command, choose **Kernel**, and select **Enable Perf Feature**.
-
-  | Item| menuconfig Option| Description| Value|
-  | -------- | -------- | -------- | -------- |
-  | LOSCFG_KERNEL_PERF | Enable Perf Feature | Whether to enable perf.| YES/NO |
-  | LOSCFG_PERF_CALC_TIME_BY_TICK | Time-consuming Calc Methods-&gt;By Tick | Whether to use tick as the perf timing unit.| YES/NO |
-  | LOSCFG_PERF_CALC_TIME_BY_CYCLE | Time-consuming Calc Methods-&gt;By Cpu Cycle | Whether to use cycle as the perf timing unit.| YES/NO |
-  | LOSCFG_PERF_BUFFER_SIZE | Perf Sampling Buffer Size | Size of the buffer used for perf sampling.| INT |
-  | LOSCFG_PERF_HW_PMU | Enable Hardware Pmu Events for Sampling | Whether to enable hardware PMU events. The target platform must support the hardware PMU.| YES/NO |
-  | LOSCFG_PERF_TIMED_PMU | Enable Hrtimer Period Events for Sampling | Whether to enable high-precision periodical events. The target platform must support the high precision event timer (HPET).| YES/NO |
-  | LOSCFG_PERF_SW_PMU | Enable Software Events for Sampling | Whether to enable software events. **LOSCFG_KERNEL_HOOK** must also be enabled.| YES/NO |
-
-2. Call **LOS_PerfConfig** to configure the events to be sampled.
-
-   perf provides two working modes and three types of events.
-
-   Working modes: counting mode (counts only the number of event occurrences) and sampling mode (collects context information such as task IDs, PC, and backtrace)
-
-   Events: CPU hardware events (such as cycle, branch, icache, and dcache), high-precision periodical events (such as CPU clock), and OS software events (such as task switch, mux pend, and IRQ)
-
-3. Call **LOS_PerfStart(UINT32 sectionId)** at the start of the code to be sampled. The input parameter **sectionId** specifies different sampling session IDs.
-
-4. Call **LOS_PerfStop** at the end of the code to be sampled.
-
-5. Call **LOS_PerfDataRead** to read the sampling data and use IDE to analyze the collected data.
-
-
-####  Kernel-Mode Development Example
-
-This example implements the following:
-
-1. Create a perf task.
-
-2. Configure sampling events.
-
-3. Start perf.
-
-4. Execute algorithms for statistics.
-
-5. Stop perf.
-
-6. Export the result. 
-
-
-####  Kernel-Mode Sample Code
-
-Prerequisites: The perf module configuration is complete in **menuconfig**.
-
-The sample code is as follows:
-
-```
-#include "los_perf.h"
-STATIC VOID OsPrintBuff(const CHAR *buf, UINT32 num)
-{
-    UINT32 i = 0;
-    PRINTK("num: ");
-    for (i = 0; i < num; i++) {
-        PRINTK(" %02d", i);
-    }
-    PRINTK("\n");
-    PRINTK("hex: ");
-    for (i = 0; i < num; i++) {
-        PRINTK(" %02x", buf[i]);
-    }
-    PRINTK("\n");
-}
-STATIC VOID perfTestHwEvent(VOID)
-{
-    UINT32 ret;
-    CHAR *buf = NULL;
-    UINT32 len;
-    PerfConfigAttr attr = {
-        .eventsCfg = {
-            .type        = PERF_EVENT_TYPE_HW,
-            .events = {
-                [0]      = {PERF_COUNT_HW_CPU_CYCLES, 0xFFFF},
-                [1]      = {PERF_COUNT_HW_BRANCH_INSTRUCTIONS, 0xFFFFFF00},
-            },
-            .eventsNr    = 2,
-            .predivided  = 1,             /* cycle counter increase every 64 cycles */
-        },
-        .taskIds         = {0},
-        .taskIdsNr       = 0,            
-        .needSample      = 0,
-        .sampleType      = PERF_RECORD_IP | PERF_RECORD_CALLCHAIN,
-    };
-    ret = LOS_PerfConfig(&attr);
-    if (ret != LOS_OK) {
-        PRINT_ERR("perf config error %u\n", ret);
-        return;
-    }
-    PRINTK("------count mode------\n");
-    LOS_PerfStart(0);
-    test(); /* this is any test function*/
-    LOS_PerfStop();
-    PRINTK("--------sample mode------ \n");
-    attr.needSample = 1;
-    LOS_PerfConfig(&attr);
-    LOS_PerfStart(2);
-    test(); /* this is any test function*/
-    LOS_PerfStop();
-    buf = LOS_MemAlloc(m_aucSysMem1, LOSCFG_PERF_BUFFER_SIZE);
-    if (buf == NULL) {
-        PRINT_ERR("buffer alloc failed\n");
-        return;
-    }
-    /* get sample data */
-    len = LOS_PerfDataRead(buf, LOSCFG_PERF_BUFFER_SIZE); 
-    OsPrintBuff(buf, len); /* print data */
-    (VOID)LOS_MemFree(m_aucSysMem1, buf);
-}
-UINT32 Example_Perf_test(VOID){
-    UINT32 ret;    
-    TSK_INIT_PARAM_S perfTestTask;    
-    /* Create a perf task. */   
-    memset(&perfTestTask, 0, sizeof(TSK_INIT_PARAM_S));    
-    perfTestTask.pfnTaskEntry = (TSK_ENTRY_FUNC)perfTestHwEvent;    
-    perfTestTask.pcName = "TestPerfTsk";    /* Test task name. */   				     
-    perfTestTask.uwStackSize  = 0x800;    
-    perfTestTask.usTaskPrio   = 5;    
-    perfTestTask.uwResved   = LOS_TASK_STATUS_DETACHED;    
-    ret = LOS_TaskCreate(&g_perfTestTaskId, &perfTestTask);    
-    if(ret != LOS_OK){        
-        PRINT_ERR("PerfTestTask create failed.\n");        
-        return LOS_NOK;    
-    }
-    return LOS_OK;
-}
-LOS_MODULE_INIT(perfTestHwEvent, LOS_INIT_LEVEL_KMOD_EXTENDED);
-```
-
-
-#### Kernel-Mode Verification
-
-  The output is as follows:
-
-```
---------count mode----------
-[EMG] [cycles] eventType: 0xff: 5466989440
-[EMG] [branches] eventType: 0xc: 602166445
-------- sample mode----------
-[EMG] dump section data, addr: 0x8000000 length: 0x800000
-num:  00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 ...
-hex:  00 ef ef ef 00 00 00 00 14 00 00 00 60 00 00 00 00 00 00 00 70 88 36 40 08 00 00 00 6b 65 72 6e 65 6c 00 00 01 00 00 00 cc 55 30 40 08 00 00 00 6b 65 72 6e 65 6c 00 00
-```
-
-- For the counting mode, the following information is displayed after perf is stopped:
-  Event name (cycles), event type (0xff), and number of event occurrences (5466989440)
-
-  For hardware PMU events, the displayed event type is the hardware event ID, not the abstract type defined in **enum PmuHWId**.
-
-- For the sampling mode, the address and length of the sampled data will be displayed after perf is stopped:
-  dump section data, addr: (0x8000000) length: (0x5000)
-
-  You can export the data using the JTAG interface and then use the IDE offline tool to analyze the data.
-
-  You can also call **LOS_PerfDataRead** to read data to a specified address for further analysis. In the example, **OsPrintBuff** is a test API, which prints the sampled data by byte. **num** indicates the sequence number of the byte, and **hex** indicates the value in the byte.
-
-
-### User-Mode Development Process
-
-Choose **Driver** > **Enable PERF DRIVER** in **menuconfig** to enable the perf driver. This option is available in **Driver** only after **Enable Perf Feature** is selected in the kernel.
-
-1. Open the **/dev/perf** file and perform read, write, and ioctl operations.
-
-2. Run the **perf** commands in user mode in the **/bin** directory. 
-   
-   After running **cd bin**, you can use the following commands:
-   
-   - **./perf start [*id*]**: starts perf sampling. *id* is optional and is **0** by default.
-   - **./perf stop**: stops perf sampling.
-   - **./perf read <*nBytes*>**: reads n-byte data from the sampling buffer and displays the data.
-   - **./perf list**: lists the events supported by **-e**.
-   - **./perf stat/record [*option*] <*command*>**: sets counting or sampling parameters.
-      - The [*option*] can be any of the following:
-         - -**-e**: sets sampling events. Events of the same type listed in **./perf list** can be used.
-         - -**-p**: sets the event sampling interval.
-         - -**-o**: specifies the path of the file for saving the perf sampling data.
-         - -**-t**: specifies the task IDs for data collection. Only the contexts of the specified tasks are collected. If this parameter is not specified, all tasks are collected by default.
-         - -**-s**: specifies the context type for sampling. For details, see **PerfSampleType** defined in **los_perf.h**.
-         - -**-P**: specifies the process IDs for data collection. Only the contexts of the specified processes are collected. If this parameter is not specified, all processes are collected by default.
-         - -**-d**: specifies whether to divide the frequency (the value is incremented by 1 each time an event occurs 64 times). This option is valid only for hardware cycle events.
-      - *command* specifies the program to be checked by perf.
-
-Examples:
-
-Run the **./perf list** command to display available events. 
-
-The output is as follows:
-
-
-```
-cycles                                 [Hardware event]
-instruction                            [Hardware event]
-dcache                                 [Hardware event]
-dcache-miss                            [Hardware event]
-icache                                 [Hardware event]
-icache-miss                            [Hardware event]
-branch                                 [Hardware event]
-branch-miss                            [Hardware event]
-clock                                     [Timed event]
-task-switch                            [Software event]
-irq-in                                 [Software event]
-mem-alloc                              [Software event]
-mux-pend                               [Software event]
-```
-
-Run **./perf stat -e cycles os_dump**. 
-
-The output is as follows:
-
-
-```
-type: 0
-events[0]: 255, 0xffff
-predivided: 0
-sampleType: 0x0
-needSample: 0
-usage os_dump [--help | -l | SERVICE]
-         --help: shows this help
-         -l: only list services, do not dump them
-         SERVICE: dumps only service SERVICE
-time used: 0.058000(s)
-[cycles] eventType: 0xff [core 0]: 21720647
-[cycles] eventType: 0xff [core 1]: 13583830
-```
-
-Run **./perf record -e cycles os_dump**. 
-
-The output is as follows:
-
-
-```
-type: 0
-events[0]: 255, 0xffff
-predivided: 0
-sampleType: 0x60
-needSample: 1
-usage os_dump [--help | -l | SERVICE]
-         --help: shows this help
-         -l: only list services, do not dump them
-         SERVICE: dumps only service SERVICE
-dump perf data, addr: 0x408643d8 length: 0x5000
-time used: 0.059000(s)
-save perf data success at /storage/data/perf.data
-```
-
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
-> After running the **./perf stat/record** command, you can run the **./perf start** and **./perf stop** commands multiple times. The sampling event configuration is as per the parameters set in the latest **./perfstat/record** command.
-
-
-#### User-Mode Development Example
-
-This example implements the following:
-
-1. Open the perf character device.
-
-2. Write the perf events.
-
-3. Start perf.
-
-4. Stop perf.
-
-5. Read the perf sampling data.
-
-
-#### User-Mode Sample Code
-
-  The code is as follows:
-
-```
-#include "fcntl.h"
-#include "user_copy.h"
-#include "sys/ioctl.h"
-#include "fs/driver.h"
-#include "los_dev_perf.h"
-#include "los_perf.h"
-#include "los_init.h"
-/* perf ioctl */
-#define PERF_IOC_MAGIC     'T'
-#define PERF_START         _IO(PERF_IOC_MAGIC, 1)
-#define PERF_STOP          _IO(PERF_IOC_MAGIC, 2)
-int main(int argc, char **argv)
-{
-    char *buf = NULL;
-    ssize_t len;
-    int fd = open("/dev/perf", O_RDWR);
-    if (fd == -1) {
-        printf("Perf open failed.\n");
-        exit(EXIT_FAILURE);
-    }
-    PerfConfigAttr attr = {
-        .eventsCfg = {
-#ifdef LOSCFG_PERF_HW_PMU
-            .type = PERF_EVENT_TYPE_HW,
-            .events = {
-                [0] = {PERF_COUNT_HW_CPU_CYCLES, 0xFFFF},
-            },
-#elif defined LOSCFG_PERF_TIMED_PMU
-            .type = PERF_EVENT_TYPE_TIMED,
-            .events = {
-                [0] = {PERF_COUNT_CPU_CLOCK, 100},
-            },
-#elif defined LOSCFG_PERF_SW_PMU
-            .type = PERF_EVENT_TYPE_SW,
-            .events = {
-                [0] = {PERF_COUNT_SW_TASK_SWITCH, 1},
-            },
-#endif
-            .eventsNr = 1, /* 1 event */
-            .predivided = 0,
-        },
-        .taskIds = {0},
-        .taskIdsNr = 0,
-        .processIds = {0},
-        .processIdsNr = 0,
-        .needSample = 1,
-        .sampleType = PERF_RECORD_IP | PERF_RECORD_CALLCHAIN,
-    };
-    (void)write(fd, &attr, sizeof(PerfConfigAttr)); /* perf config */
-    ioctl(fd, PERF_START, NULL); /* perf start */
-    test();
-    ioctl(fd, PERF_STOP, NULL); /* perf stop */
-    buf = (char *)malloc(LOSCFG_PERF_BUFFER_SIZE);
-    if (buf == NULL) {
-        printf("no memory for read perf 0x%x\n", LOSCFG_PERF_BUFFER_SIZE);
-        return -1;
-    }
-    len = read(fd, buf, LOSCFG_PERF_BUFFER_SIZE);
-    OsPrintBuff(buf, len); /* print data */
-    free(buf);
-    close(fd);
-    return 0;
-}
-```
-
-
-#### User-Mode Verification
-
-  The output is as follows:
-
-```
-[EMG] dump section data, addr: 0x8000000 length: 0x800000
-num:  00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 ...
-hex:  00 ef ef ef 00 00 00 00 14 00 00 00 60 00 00 00 00 00 00 00 70 88 36 40 08 00 00 00 6b 65 72 6e 65 6c 00 00 01 00 00 00 cc 55 30 40 08 00 00 00 6b 65 72 6e 65 6c 00 00
-```
diff --git a/en/device-dev/subsystems/Readme-EN.md b/en/device-dev/subsystems/Readme-EN.md
index 18af05d1d892d901c5e83f853d58c6925af1578a..bc5a5722ed27c1cbc91a56af050ca3bfa79f4457 100644
--- a/en/device-dev/subsystems/Readme-EN.md
+++ b/en/device-dev/subsystems/Readme-EN.md
@@ -20,7 +20,6 @@
       - [HAP Build Guide](subsys-build-gn-hap-compilation-guide.md)
       - [FAQs](subsys-build-FAQ.md)
 - [ArkCompiler Development](subsys-arkcompiler-guide.md)
-- [Distributed Remote Startup](subsys-remote-start.md)
 - Graphics
   - [Graphics Overview](subsys-graphics-overview.md)
   - [Container Component Development](subsys-graphics-container-guide.md)
diff --git a/en/device-dev/website.md b/en/device-dev/website.md
index b0a4b5f6c9a94cec2aa8ae2158da36ef73218d7b..c84b95dd2887b136be7ec793efb3e430bafe64a9 100644
--- a/en/device-dev/website.md
+++ b/en/device-dev/website.md
@@ -58,100 +58,54 @@
     - [Build Form Factors](quick-start/quickstart-appendix-compiledform.md)
     - [Getting Started with the Standard System with Hi3516 (IDE Mode)](quick-start/quickstart-appendix-hi3516-ide.md)
     - [Getting Started with the Standard System with Hi3516 (CLI Mode)](quick-start/quickstart-appendix-hi3516-pkg.md)
-  
   - [Obtaining Source Code](get-code/sourcecode-acquire.md)
 - Privacy and Security
   - [Privacy Protection](security/security-privacy-protection.md)
   - [Security Guidelines](security/security-guidelines-overall.md)
-
 - Porting
-
   - Mini System SoC Porting Guide
-
     - [Overview](porting/porting-minichip-overview.md)
-
     - [Porting Preparation](porting/porting-minichip-prepare.md)
-
     - [Kernel Porting](porting/porting-minichip-kernel.md)
-
     - Subsystem Porting
-
       - [Subsystem Porting Overview](porting/porting-minichip-subsys-overview.md)
-
       - [Porting the Startup Subsystem](porting/porting-minichip-subsys-startup.md)
-
       - [Porting the File Subsystem](porting/porting-minichip-subsys-filesystem.md)
-
       - [Porting the Security Subsystem](porting/porting-minichip-subsys-security.md)
-
       - [Porting the Communication Subsystem](porting/porting-minichip-subsys-communication.md)
-
       - [Porting the Driver Subsystem](porting/porting-minichip-subsys-driver.md)
-
       - [Configuring Other Subsystems](porting/porting-minichip-subsys-others.md)
-
     - [Porting Verification](porting/porting-minichip-verification.md)
-
     - [FAQs](porting/porting-chip-faqs.md)
-
   - Small System SoC Porting Guide
-
     - Porting Preparation
-
       - [Before You Start](porting/porting-smallchip-prepare-needs.md)
-
       - [Compilation and Building](porting/porting-smallchip-prepare-building.md)
-
     - Kernel Porting
-
       - [LiteOS Cortex-A](porting/porting-smallchip-kernel-a.md)
-
       - [Linux Kernel](porting/porting-smallchip-kernel-linux.md)
-
     - Driver Porting
-
       - [Porting Overview](porting/porting-smallchip-driver-overview.md)
-
       - [Platform Driver Porting](porting/porting-smallchip-driver-plat.md)
-
       - [Device Driver Porting](porting/porting-smallchip-driver-oom.md)
-
   - Standard System SoC Porting Guide
-
     - [Standard System Porting Guide](porting/standard-system-porting-guide.md)
-
     - [A Method for Rapidly Porting the OpenHarmony Linux Kernel](porting/porting-linux-kernel.md)
-
   - Third-Party Library Porting Guide for Mini and Small Systems
-
     - [Overview](porting/porting-thirdparty-overview.md)
-
     - [Porting a Library Built Using CMake](porting/porting-thirdparty-cmake.md)
-
     - [Porting a Library Built Using Makefile](porting/porting-thirdparty-makefile.md)
-
   - Mini System SoC Porting Cases
-
       - [Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting/porting-bes2600w-on-minisystem-display-demo.md)
-
       - [Combo Solution – ASR Chip Porting Case](porting/porting-asr582x-combo-demo.md)
-
-      - [IoT Solution - Chipsea CST85 Chip Porting Case](porting/porting-cst85f01-combo-demo.md)
-
+      -[IoT Solution - Chipsea CST85 Chip Porting Case](porting/porting-cst85f01-combo-demo.md)
       - [Mini System STM32F407 SoC Porting Case](porting/porting-stm32f407-on-minisystem-eth.md)
-
       - [Combo Solution – W800 Chip Porting Case](porting/porting-w800-combo-demo.md)
-
   - Small System SoC Porting Cases
-
       - [Mini-System Devices – STM32MP1 SoC Porting Case](porting/porting-stm32mp15xx-on-smallsystem.md)
-
   - Standard System SoC Porting Cases
-
       - [Standard System Solution – Rockchip RK3568 Porting Case](porting/porting-dayu200-on_standard-demo.md)
-
 - Subsystem Development
-
   -  Kernel
      - [Kernel Overview](kernel/kernel-overview.md)
      - Mini-System Kernel (LiteOS-M)
@@ -218,6 +172,7 @@
            - [Virtual File System](kernel/kernel-small-bundles-fs-virtual.md)
            - [Supported File Systems](kernel/kernel-small-bundles-fs-support.md)
            - [File System Adaptation](kernel/kernel-small-bundles-fs-new.md)
+           - [plimits](kernel/kernel-small-plimits.md)
        - Debugging and Tools
          - Shell
            - [Introduction to the Shell](kernel/kernel-small-debug-shell-overview.md)
@@ -287,7 +242,7 @@
            - [Magic Key](kernel/kernel-small-debug-shell-magickey.md)
            - [User-Mode Exception Information](kernel/kernel-small-debug-shell-error.md)
          - [Trace](kernel/kernel-small-debug-trace.md)
-         - [perf](kernel/kernel-mini-memory-perf.md)
+         - [perf](kernel/kernel-small-debug-perf.md)
          - [LMS](kernel/kernel-small-memory-lms.md)
          - [Process Debugging](kernel/kernel-small-debug-process-cpu.md)
          - Kernel-Mode Memory Debugging
@@ -394,7 +349,6 @@
        - [Viewing Ninja Build Information](subsystems/subsys-build-reference.md)
        - [HAP Build Guide](subsystems/subsys-build-gn-hap-compilation-guide.md)
        - [FAQs](subsystems/subsys-build-FAQ.md)
-  -  [Distributed Remote Startup](subsystems/subsys-remote-start.md)
   -  Graphics
      - [Graphics Overview](subsystems/subsys-graphics-overview.md)
      - [Container Component Development](subsystems/subsys-graphics-container-guide.md)
@@ -416,15 +370,8 @@
      - [Utils Development](subsystems/subsys-utils-guide.md)
      - [Utils FAQ](subsystems/subsys-utils-faqs.md)
   - AI
-     - [AI Framework Development](subsys-ai-aiframework-devguide.md)
-     - [NNRt Development](subsys-ai-nnrt-guide.md)
-  -  Data Management
-     - RDB
-       - [RDB Overview](subsystems/subsys-data-relational-database-overview.md)
-       - [RDB Development](subsystems/subsys-data-relational-database-guide.md)
-     - Lightweight Data Store
-       - [Lightweight Data Store Overview](subsystems/subsys-data-storage-overview.md)
-       - [Lightweight Data Store Development](subsystems/subsys-data-storage-guide.md)
+     - [AI Framework Development](subsystems/subsys-ai-aiframework-devguide.md)
+     - [NNRt Development](subsystems/subsys-ai-nnrt-guide.md)
   -  Sensor
      - [Sensor Overview](subsystems/subsys-sensor-overview.md)
      - [Sensor Usage Guidelines](subsystems/subsys-sensor-guide.md)
@@ -478,17 +425,13 @@
      - [HiChecker Development](subsystems/subsys-dfx-hichecker.md)
      - [FaultLogger Development](subsystems/subsys-dfx-faultlogger.md)
      - [Hiview Development](subsystems/subsys-dfx-hiview.md)
-  
+
 - Featured Topics
   - HPM Part
     - [HPM Part Overview](hpm-part/hpm-part-about.md)
-
     - [HPM Part Development](hpm-part/hpm-part-development.md)
-
     - [HPM Part Reference](hpm-part/hpm-part-reference.md)
-
 - Device Development Examples
-
   - Mini- and Small-System Devices
     - WLAN-connected Products
       - [LED Peripheral Control](guide/device-wlan-led-control.md)
@@ -514,17 +457,16 @@
     - [Development Guidelines on Clock Apps](guide/device-clock-guide.md)
     - [Development Example for Platform Drivers](guide/device-driver-demo.md)
     - [Development Example for Peripheral Drivers](guide/device-outerdriver-demo.md)
-
-
 - Debugging
   - [Development Self-Test Framework User Guide](device-test/developer_test.md)
   - [xDevice User Guide](device-test/xdevice.md)
+  - [Smartperf-Host User Guide](device-test/smartperf-host.md)
   - R&D Tools
     - [bytrace](subsystems/subsys-toolchain-bytrace-guide.md)
     - [hdc](subsystems/subsys-toolchain-hdc-guide.md)
     - [hiperf](subsystems/subsys-toolchain-hiperf.md)
+- [XTS](device-test/xts.md)
 - Tools
-
   - [Tool Overview](get-code/gettools-overview.md)
   - [Docker Environment](get-code/gettools-acquire.md)
   - [IDE](get-code/gettools-ide.md)