diff --git a/en/application-dev/dfx/hitracemeter-guidelines.md b/en/application-dev/dfx/hitracemeter-guidelines.md
index a4152acb7303cd672b830d80a3ba48bc54ee8d9c..ed99e4e89d5b6fce3d5bd50ef8dedcfc32b04fb1 100644
--- a/en/application-dev/dfx/hitracemeter-guidelines.md
+++ b/en/application-dev/dfx/hitracemeter-guidelines.md
@@ -21,7 +21,7 @@ hiTraceMeter provides APIs for system performance tracing. You can call the APIs
 
 ## Available APIs
 
-The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference]( ../reference/apis/js-apis-hitracemeter.md).
+The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference](../reference/apis/js-apis-hitracemeter.md).
 
 **APIs for performance tracing**
 
@@ -80,15 +80,15 @@ In this example, distributed call chain tracing begins when the application star
    ```
 
 2. Create an ArkTs application project. In the displayed **Project** window, choose **entry** > **src** > **main** > **ets** > **pages** > **index**, and double-click **index.js**. Add the code to implement performance tracing upon page loading. For example, if the name of the trace task is **HITRACE\_TAG\_APP**, the sample code is as follows:
- 
+
    ```ts
    import hitrace from '@ohos.hiTraceMeter';
-  
+    
    @Entry
    @Component
    struct Index {
      @State message: string = 'Hello World';
- 
+    
      build() {
        Row() {
          Column() {
@@ -97,7 +97,7 @@ In this example, distributed call chain tracing begins when the application star
              .fontWeight(FontWeight.Bold)
              .onClick(() => {
                this.message = 'Hello ArkUI';
-
+   
                // Start trace tasks with the same name concurrently.
                hitrace.startTrace("HITRACE_TAG_APP", 1001);
                // Keep the service process running.
@@ -107,7 +107,7 @@ In this example, distributed call chain tracing begins when the application star
                hitrace.startTrace("HITRACE_TAG_APP", 1002);
                // Keep the service process running.
                console.log(`HITRACE_TAG_APP running`);
-  
+    
                hitrace.finishTrace("HITRACE_TAG_APP", 1001);
                hitrace.finishTrace("HITRACE_TAG_APP", 1002);
    
@@ -143,7 +143,7 @@ In this example, distributed call chain tracing begins when the application star
    ```
    
 3. Click the run button on the application page. Then, run the following commands in sequence in shell:
- 
+
    ```shell
    hdc shell
    hitrace --trace_begin app
diff --git a/en/application-dev/faqs/faqs-ability.md b/en/application-dev/faqs/faqs-ability.md
index fef66125771888f9dfe3dce2ae4297ce858d56b8..e42fc81eca4b256ec1dc2e242c9f777f5cda0923 100644
--- a/en/application-dev/faqs/faqs-ability.md
+++ b/en/application-dev/faqs/faqs-ability.md
@@ -217,7 +217,7 @@ Use **Context.cacheDir** to obtain the cache directory of the application.
 
 **Reference**
 
-[Obtaining the Application Development Path](../application-models/application-context-stage.md#obtaining-the-application-development-path)
+[Obtaining Application File Paths](../application-models/application-context-stage.md#obtaining-application-file-paths)
 
 ## In which JS file is the service widget lifecycle callback invoked?
 
@@ -262,7 +262,7 @@ Obtain them from the application context. Specifically, use **this.context.getAp
 
 **Reference**
 
-[Obtaining the Application Development Path](../application-models/application-context-stage.md#obtaining-the-application-development-path)
+[Obtaining Application File Paths](../application-models/application-context-stage.md#obtaining-application-file-paths)
 
 ## Why the application is not deleted from the background mission list after it calls terminateSelf?
 
@@ -472,7 +472,7 @@ To start a continuous task in the background, you must configure the permission
 
 [Continuous Task Permission](../security/permission-list.md#ohospermissionkeep_background_running)
 
-[Continuous Task Development](../task-management/continuous-task-dev-guide.md#development-in-the-stage-model)
+[Continuous Task Development](../task-management/continuous-task.md#stage-model)
 
 ## How do FA widgets exchange data?
 
diff --git a/en/application-dev/faqs/faqs-arkui-animation-interactive-event.md b/en/application-dev/faqs/faqs-arkui-animation-interactive-event.md
index fbe2594e6591bb774aa116095e721ca889490cc8..56c1f44dfd74cec442e94b6116a0bab8965cbc66 100644
--- a/en/application-dev/faqs/faqs-arkui-animation-interactive-event.md
+++ b/en/application-dev/faqs/faqs-arkui-animation-interactive-event.md
@@ -191,7 +191,7 @@ struct PageTransition2 {
 
 **Reference**
 
-[Page Transition Animation](../ui/arkts-page-transition-animation.md)
+[Page Transition](../reference/arkui-ts/ts-page-transition-animation.md)
 
 ## How do I configure custom components to slide in and out from the bottom?
 
@@ -266,4 +266,4 @@ struct ComponentChild2 {
 
 **Reference**
 
-[Transition Animation Within the Component](../ui/arkts-transition-animation-within-component.md)
+[Transition Animation Within the Component](../ui/arkts-enter-exit-transition.md)
diff --git a/en/application-dev/faqs/faqs-multimedia.md b/en/application-dev/faqs/faqs-multimedia.md
index 6d15bc704000f19b61d2f753b46a38592b052f06..5ebfdb20da6c3b7e53b15bdd1b09ec9107f72d52 100644
--- a/en/application-dev/faqs/faqs-multimedia.md
+++ b/en/application-dev/faqs/faqs-multimedia.md
@@ -98,7 +98,7 @@ Music cannot be played in the background.
 
 **Reference**
 
-[Continuous Task Development](../task-management/continuous-task-dev-guide.md)
+[Continuous Task Development](../task-management/continuous-task.md)
 
 [AVSession Development](../media/using-avsession-developer.md)
 
diff --git a/en/application-dev/media/audio-playback-overview.md b/en/application-dev/media/audio-playback-overview.md
index 5ef7a6f9c4d08719a71c9e07f34fa1104802fcc6..767f3dd775546f58844885406bc4816dc82a2eb6 100644
--- a/en/application-dev/media/audio-playback-overview.md
+++ b/en/application-dev/media/audio-playback-overview.md
@@ -20,6 +20,6 @@ To enable your application to play a video in the background or when the screen
 
 1. The application is registered with the system for unified management through the **AVSession** APIs. Otherwise, the playback will be forcibly stopped when the application switches to the background. For details, see [AVSession Development](avsession-overview.md).
 
-2. The application must request a continuous task to prevent from being suspended. For details, see [Continuous Task Development](../task-management/continuous-task-dev-guide.md).
+2. The application must request a continuous task to prevent from being suspended. For details, see [Continuous Task](../task-management/continuous-task.md).
 
 If the playback is interrupted when the application switches to the background, you can view the log to see whether the application has requested a continuous task. If the application has requested a continuous task, there is no log recording **pause id**; otherwise, there is a log recording **pause id**.
diff --git a/en/application-dev/media/avsession-overview.md b/en/application-dev/media/avsession-overview.md
index 766e642eebc2ba861bf6aceca5f9ea702f99d74f..619c37bdc97999dd35ffbc3cec6426cd00713906 100644
--- a/en/application-dev/media/avsession-overview.md
+++ b/en/application-dev/media/avsession-overview.md
@@ -4,7 +4,7 @@ The Audio and Video Session (AVSession) service is used to manage the playback b
 
 Audio and video applications access the AVSession service and send application data (for example, a song that is being played and playback state) to it. Through a controller, the user can choose another application or device to continue the playback. If an application does not access the AVSession service, its playback will be forcibly interrupted when it switches to the background.
 
-To implement background playback, you must request a continuous task to prevent the task from being suspended. For details, see [Continuous Task Development](../task-management/continuous-task-dev-guide.md).
+To implement background playback, you must request a continuous task to prevent the task from being suspended. For details, see [Continuous Task](../task-management/continuous-task.md).
 
 ## Basic Concepts
 
diff --git a/en/application-dev/media/using-avplayer-for-playback.md b/en/application-dev/media/using-avplayer-for-playback.md
index 9af55fb71b489f7b3ece342969c72d18ed90eaab..e5cd19b6c1077d9c73660087d751b48a47601e12 100644
--- a/en/application-dev/media/using-avplayer-for-playback.md
+++ b/en/application-dev/media/using-avplayer-for-playback.md
@@ -2,7 +2,7 @@
 
 The AVPlayer is used to play raw media assets in an end-to-end manner. In this topic, you will learn how to use the AVPlayer to play a complete piece of music.
 
-If you want the application to continue playing the music in the background or when the screen is off, you must use the [AVSession](avsession-overview.md) and [continuous task](../task-management/continuous-task-dev-guide.md) to prevent the playback from being forcibly interrupted by the system.
+If you want the application to continue playing the music in the background or when the screen is off, you must use the [AVSession](avsession-overview.md) and [continuous task](../task-management/continuous-task.md) to prevent the playback from being forcibly interrupted by the system.
 
 
 The full playback process includes creating an **AVPlayer** instance, setting the media asset to play, setting playback parameters (volume, speed, and focus mode), controlling playback (play, pause, seek, and stop), resetting the playback configuration, and releasing the instance.
@@ -40,7 +40,7 @@ Read [AVPlayer](../reference/apis/js-apis-media.md#avplayer9) for the API refere
    >
    > The URL in the code snippet below is for reference only. You need to check the media asset validity and set the URL based on service requirements.
    > 
-   > - If local files are used for playback, ensure that the files are available and the application sandbox path is used for access. For details about how to obtain the application sandbox path, see [Obtaining the Application Development Path](../application-models/application-context-stage.md#obtaining-the-application-development-path). For details about the application sandbox and how to push files to the application sandbox, see [File Management](../file-management/app-sandbox-directory.md).
+   > - If local files are used for playback, ensure that the files are available and the application sandbox path is used for access. For details about how to obtain the application sandbox path, see [Obtaining Application File Paths](../application-models/application-context-stage.md#obtaining-application-file-paths). For details about the application sandbox and how to push files to the application sandbox, see [File Management](../file-management/app-sandbox-directory.md).
    > 
    > - If a network playback path is used, you must request the ohos.permission.INTERNET [permission](../security/accesstoken-guidelines.md).
    > 
diff --git a/en/application-dev/media/video-playback.md b/en/application-dev/media/video-playback.md
index f745f2f25120f7068de6634af56aa1f443c5b5d9..30e3a98f9858baf7d3a6cbaf5c826792322417b4 100644
--- a/en/application-dev/media/video-playback.md
+++ b/en/application-dev/media/video-playback.md
@@ -6,7 +6,7 @@ OpenHarmony provides two solutions for video playback development:
 
 - <Video\> component: encapsulates basic video playback capabilities. It can be used to play video files after the data source and basic information are set. However, its scalability is poor. This component is provided by ArkUI. For details about how to use this component for video playback development, see [Video Component](../ui/arkts-common-components-video-player.md).
 
-In this topic, you will learn how to use the AVPlayer to develop a video playback service that plays a complete video file. If you want the application to continue playing the video in the background or when the screen is off, you must use the [AVSession](avsession-overview.md) and [continuous task](../task-management/continuous-task-dev-guide.md) to prevent the playback from being forcibly interrupted by the system.
+In this topic, you will learn how to use the AVPlayer to develop a video playback service that plays a complete video file. If you want the application to continue playing the video in the background or when the screen is off, you must use the [AVSession](avsession-overview.md) and [continuous task](../task-management/continuous-task.md) to prevent the playback from being forcibly interrupted by the system.
 
 ## Development Guidelines
 
diff --git a/en/application-dev/quick-start/Readme-EN.md b/en/application-dev/quick-start/Readme-EN.md
index 518ace9f58af6fc85388ab6e21f1eea36753a5b9..1d079b36d7af3cf7682659edc9362e6e802e258b 100644
--- a/en/application-dev/quick-start/Readme-EN.md
+++ b/en/application-dev/quick-start/Readme-EN.md
@@ -41,8 +41,8 @@
   - [Resource Categories and Access](resource-categories-and-access.md)
 - Learning ArkTS
   - [Getting Started with ArkTS](arkts-get-started.md)
-  - [Introduction to ArkTS](arkts/introduction-to-arkts.md)
-  - [TypeScript to ArkTS Migration Guide](arkts/typescript-to-arkts-migration-guide.md)
+  - [Introduction to ArkTS](introduction-to-arkts.md)
+  - [TypeScript to ArkTS Migration Guide](typescript-to-arkts-migration-guide.md)
   - UI paradigms
     - Basic Syntax
       - [Basic Syntax Overview](arkts-basic-syntax-overview.md)
diff --git a/en/application-dev/reference/apis/js-apis-arkui-UIContext.md b/en/application-dev/reference/apis/js-apis-arkui-UIContext.md
index 16a22c9cee6bd544845e748e039c64c2880bae7d..3862eeefb3dbb77c6171512c424af27e4f623eb8 100644
--- a/en/application-dev/reference/apis/js-apis-arkui-UIContext.md
+++ b/en/application-dev/reference/apis/js-apis-arkui-UIContext.md
@@ -548,9 +548,9 @@ Obtains the size, position, translation, scaling, rotation, and affine matrix in
 
 **Return value**
 
-| Type                                                    | Description                                            |
-| -------------------------------------------------------- | ------------------------------------------------ |
-| [ComponentInfo](js-apis-componentUtils.md#componentinfo) | Size, position, translation, scaling, rotation, and affine matrix information of the component.|
+| Type          | Description                                                  |
+| ------------- | ------------------------------------------------------------ |
+| ComponentInfo | Size, position, translation, scaling, rotation, and affine matrix information of the component. |
 
 **Example**
 
diff --git a/en/application-dev/reference/apis/js-apis-bundleManager.md b/en/application-dev/reference/apis/js-apis-bundleManager.md
index a25ad1642f255ee57a70f497a12a308ff49510c2..99e99255972ca0ae8a91b4fb55f4ae2387816b8d 100644
--- a/en/application-dev/reference/apis/js-apis-bundleManager.md
+++ b/en/application-dev/reference/apis/js-apis-bundleManager.md
@@ -100,7 +100,7 @@ Enumerates the types of Extension abilities.
 | Name| Value| Description|
 |:----------------:|:---:|-----|
 | FORM             | 0   | [FormExtensionAbility](../../application-models/service-widget-overview.md): provides APIs for widget development.|
-| WORK_SCHEDULER   | 1   | [WorkSchedulerExtensionAbility](../../task-management/work-scheduler-dev-guide.md): enables applications to execute non-real-time tasks when the system is idle.|
+| WORK_SCHEDULER   | 1   | [WorkSchedulerExtensionAbility](../../task-management/work-scheduler.md): enables applications to execute non-real-time tasks when the system is idle. |
 | INPUT_METHOD     | 2   | [InputMethodExtensionAbility](js-apis-inputmethod-extension-ability.md): provides APIs for developing input method applications.|
 | SERVICE          | 3   | [ServiceExtensionAbility](../../application-models/serviceextensionability.md): enables applications to run in the background and provide services.|
 | ACCESSIBILITY    | 4   | [AccessibilityExtensionAbility](js-apis-application-accessibilityExtensionAbility.md): provides accessibility for access to and operations on the UI.|
diff --git a/en/application-dev/reference/apis/js-apis-inner-application-applicationContext.md b/en/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
index 171527dd0ed70aef5499158e01be0409d0fa1550..1b5f208ade4e573769ad9a1d9263d605285d5c02 100644
--- a/en/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
+++ b/en/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
@@ -292,7 +292,7 @@ Registers a listener for application foreground/background state changes. This A
 | Name  | Type                                                        | Mandatory| Description            |
 | -------- | ------------------------------------------------------------ | ---- | ---------------- |
 | type     | string                                     | Yes  | Event type. The value is fixed at **'applicationStateChange'**, indicating that the application switches from the foreground to the background or vice versa.|
-| callback | [ApplicationStateChangeCallback](#js-apis-app-ability-applicationStateChangeCallback.md) | Yes  | Callback used to return the result.      |
+| callback | [ApplicationStateChangeCallback](js-apis-app-ability-applicationStateChangeCallback.md) | Yes  | Callback used to return the result.      |
 
 **Example**
 
@@ -370,7 +370,7 @@ Deregisters all the listeners for application foreground/background state change
 | Name| Type         | Mandatory| Description                |
 | ------ | ------------- | ---- | -------------------- |
 | type   | string | Yes  | Event type. The value is fixed at **'applicationStateChange'**, indicating that the application switches from the foreground to the background or vice versa.|
-| callback | [ApplicationStateChangeCallback](#js-apis-app-ability-applicationStateChangeCallback.md) | No  | Callback used to return the result.      |
+| callback | [ApplicationStateChangeCallback](js-apis-app-ability-applicationStateChangeCallback.md) | No  | Callback used to return the result.      |
 
 **Example**
 
diff --git a/en/application-dev/website.md b/en/application-dev/website.md
index 9605cdbe5ca3c083d5ac8887d45fa469943ee861..655a4dc5efdcc6c35a32876e7a4d9268c2cd208c 100644
--- a/en/application-dev/website.md
+++ b/en/application-dev/website.md
@@ -1397,7 +1397,7 @@
     - Components No Longer Maintained 
       - [GridContainer](reference/arkui-ts/ts-container-gridcontainer.md)
     - APIs No Longer Maintained
-    - [Click Control](reference/arkui-ts/ts-universal-attributes-click.md)
+      - [Click Control](reference/arkui-ts/ts-universal-attributes-click.md)
   - Component Reference (JavaScript-compatible Web-like Development Paradigm - ArkUI.Full)
     - Universal Component Information
       - [Universal Attributes](reference/arkui-js/js-components-common-attributes.md)
diff --git a/en/device-dev/device-dev-guide.md b/en/device-dev/device-dev-guide.md
index de69f8c8f17529c12ec54d30c2dca2a4b44567d5..caddaf65e31768d38dd9424a833f3ace66f1cd4f 100644
--- a/en/device-dev/device-dev-guide.md
+++ b/en/device-dev/device-dev-guide.md
@@ -34,7 +34,7 @@ In addition, OpenHarmony provides a wide array of system components that can be
 | About OpenHarmony| Getting familiar with OpenHarmony                                         | - [About OpenHarmony](https://gitee.com/openharmony)<br>- [Glossary](../glossary.md)|
 | Development resources   | Preparing for your development                                          | - [Obtaining Source Code](get-code/sourcecode-acquire.md)<br>- [Obtaining Tools](get-code/gettools-acquire.md) |
 | Getting started       | Getting started with setup, build, burning, debugging, and running of OpenHarmony         | - [Getting Started](quick-start/Readme-EN.md) |
-| Basic capabilities   | Using basic capabilities of OpenHarmony                               | - [Kernel for Mini System](kernel/kernel-mini-overview.md)<br>- [Kernel for Small System](kernel/kernel-small-overview.md)<br>- [HDF](driver/driver-hdf-overview.md)<br>- [Compilation and Building Guide](subsystems/subsys-build-all.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md)|
+| Basic capabilities   | Using basic capabilities of OpenHarmony                               | - [Kernel for Mini System](kernel/kernel-mini-overview.md)<br>- [Kernel for Small System](kernel/kernel-small-overview.md)<br>- [HDF](driver/driver-overview-foundation.md)<br>- [Compilation and Building Guide](subsystems/subsys-build-all.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md) |
 | Advanced development       | Developing smart devices based on system capabilities                                    | - [WLAN-connected Products](guide/device-wlan-led-control.md)<br>- [Cameras with a Screen](guide/device-camera-control-overview.md) |
 | Porting and adaptation       | - Porting and adapting OpenHarmony to an SoC<br>- Porting and adapting OpenHarmony to a third-party library<br>- Third-party vendor porting cases<br>| - [Small System SoC Porting Guide](porting/porting-smallchip-prepare-needs.md)<br>- [Third-Party Library Porting Guide for Mini and Small Systems](porting/porting-thirdparty-overview.md) <br>   - [Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting/porting-bes2600w-on-minisystem-display-demo.md) |
 | Contributing components       | Contributing components to OpenHarmony                                   | - [HPM Part Overview](hpm-part/hpm-part-about.md)<br>- [HPM Part Development](hpm-part/hpm-part-development.md)<br>- [HPM Part Reference](hpm-part/hpm-part-reference.md) |
@@ -47,7 +47,7 @@ In addition, OpenHarmony provides a wide array of system components that can be
 | About OpenHarmony| Getting familiar with OpenHarmony| - [About OpenHarmony](https://gitee.com/openharmony)<br>- [Glossary](../glossary.md)|
 | Development resources| Preparing for your development| - [Obtaining Source Code](get-code/sourcecode-acquire.md)<br>- [Obtaining Tools](get-code/gettools-acquire.md) |
 | Getting started| Getting started with setup, build, burning, debugging, and running of OpenHarmony| - [Getting Started](quick-start/Readme-EN.md) |
-| Basic capabilities| Using basic capabilities of OpenHarmony| - [Kernel Development](kernel/kernel-standard-overview.md)<br>- [HDF](driver/driver-hdf-overview.md)<br>- [Compilation and Building Guide](subsystems/subsys-build-all.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md) |
+| Basic capabilities| Using basic capabilities of OpenHarmony| - [Kernel Development](kernel/kernel-standard-overview.md)<br>- [HDF](driver/driver-overview-foundation.md)<br>- [Compilation and Building Guide](subsystems/subsys-build-all.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md) |
 | Advanced development| Developing smart devices based on system capabilities| - [Development Guidelines on Clock Apps](guide/device-clock-guide.md)<br>- [Development Example for Platform Drivers](guide/device-driver-demo.md)<br>- [Development Example for Peripheral Drivers](guide/device-outerdriver-demo.md) |
 | Porting and adaptation| - Porting and adapting OpenHarmony to an SoC<br>- Rapidly porting the OpenHarmony Linux kernel| - [Standard System Porting Guide](porting/standard-system-porting-guide.md)<br>- [A Method for Rapidly Porting the OpenHarmony Linux Kernel](porting/porting-linux-kernel.md) |
 | Contributing components| Contributing components to OpenHarmony| - [HPM Part Overview](hpm-part/hpm-part-about.md)<br>- [HPM Part Development](hpm-part/hpm-part-development.md)<br>- [HPM Part Reference](hpm-part/hpm-part-reference.md) |
diff --git a/en/device-dev/driver/driver-overview-foundation.md b/en/device-dev/driver/driver-overview-foundation.md
index d1bb233bf1ac1e8fe6920f5e06014772d62d020d..202934ce474afb649ce9de3f578eb1a0f746da4e 100644
--- a/en/device-dev/driver/driver-overview-foundation.md
+++ b/en/device-dev/driver/driver-overview-foundation.md
@@ -9,16 +9,19 @@ The OpenHarmony driver subsystem provides the following features and capabilitie
 
 - Elastic framework capabilities
   
+
 Based on the traditional driver framework, the OpenHarmony driver subsystem builds elastic framework capabilities to enable deployment on terminal products with memory of hundreds KB to hundreds MB.
-  
+
 - Standardized driver interfaces
   
+
 The OpenHarmony driver subsystem provides stable driver APIs compatible with the APIs of future-proof smartphones, tablets, smart TVs.
-  
+
 - Component-based driver model
   
+
 The OpenHarmony driver subsystem provides the component-based driver model to implement more refined driver management. You can add or reduce components as required and focus on the interaction between the hardware and driver. The subsystem also presets some template-based driver model components, such as the network device model.
-  
+
 - Normalized configuration UI
   
   The OpenHarmony driver subsystem provides a unified configuration tool that supports cross-platform configuration conversion and generation, enabling seamless switchover across platforms.
diff --git a/en/device-dev/guide/device-driver-demo.md b/en/device-dev/guide/device-driver-demo.md
index 777a8dba8e8c044fc2f83e7dd44303f68e8c64c2..b51f5b75ea8e451d8e232351e37fa98e5adefe4d 100644
--- a/en/device-dev/guide/device-driver-demo.md
+++ b/en/device-dev/guide/device-driver-demo.md
@@ -143,7 +143,7 @@ Configure the  **device\_info.hcs**  file and obtain and parse device configurat
 
 2.  \(Optional\) Add configuration parameters.
 
-    The driver may require private configuration information to ensure that the register configuration meets the requirements of different products. If private configuration data is required, you can add a driver configuration file to store some default configuration information about the driver. When loading the driver, the HDF obtains the specified configuration information, saves it in the  **property**  attribute of  **HdfDeviceObject**, and passes it to the driver via  **Bind**  and  **Init**. For details about how to use  **Bind**  and  **Init**, see  [Driver Development](../driver/driver-hdf-development.md). You can create a configuration file and reference it in the  **hdf.hcs**  file of the board-level driver. In this example, configuration parameters are directly added to the existing configuration file  **i2c\_config.hcs**.
+    The driver may require private configuration information to ensure that the register configuration meets the requirements of different products. If private configuration data is required, you can add a driver configuration file to store some default configuration information about the driver. When loading the driver, the HDF obtains the specified configuration information, saves it in the  **property**  attribute of  **HdfDeviceObject**, and passes it to the driver via  **Bind**  and  **Init**. For details about how to use  **Bind**  and  **Init**, see  [Driver Development](../driver/driver-overview-foundation.md). You can create a configuration file and reference it in the  **hdf.hcs**  file of the board-level driver. In this example, configuration parameters are directly added to the existing configuration file  **i2c\_config.hcs**.
 
     The following configuration parameters are added to the  **i2c\_config.hcs**  file:
 
@@ -434,4 +434,3 @@ Initialize the controller hardware, call core-layer APIs to add or delete device
     
     - For details about the operations in IDE mode, see [Building Source Code](../quick-start/quickstart-appendix-hi3516-ide.md#building-source-code) and [Burning an Image](../quick-start/quickstart-appendix-hi3516-ide.md#burning-an-image).
 
-
diff --git a/en/device-dev/guide/device-outerdriver-demo.md b/en/device-dev/guide/device-outerdriver-demo.md
index 5ff943c22f1a91a94fea476159087766e72c4d59..744ab37184dc8ac1daeb74ce7569249340faeb5a 100644
--- a/en/device-dev/guide/device-outerdriver-demo.md
+++ b/en/device-dev/guide/device-outerdriver-demo.md
@@ -41,7 +41,7 @@ You can configure the device driver description in the configuration file at **.
 
 The **device\_info.hcs**  file contains all necessary information for registering drivers in the input driver model with the HDF. You do not need to make any modification for the information unless otherwise required in special scenarios. The private configuration data of each driver uses the **deviceMatchAttr**  field to match the **match\_attr**  field in the **input\_config.hcs**  file.
 
-The input-related fields in the configuration file are as follows. For details about these fields, see  [Driver Development](../driver/driver-hdf-development.md).
+The input-related fields in the configuration file are as follows. For details about these fields, see  [Driver Development](../driver/driver-overview-foundation.md).
 
 ```
 input :: host {
diff --git a/en/device-dev/porting/porting-smallchip-driver-overview.md b/en/device-dev/porting/porting-smallchip-driver-overview.md
index 3a4fd33171a66dcb44d3266daf8ce41206742330..61d07597361d2e459b465cae59d3109af8471664 100644
--- a/en/device-dev/porting/porting-smallchip-driver-overview.md
+++ b/en/device-dev/porting/porting-smallchip-driver-overview.md
@@ -5,5 +5,5 @@ Drivers can be classified as platform drivers or device drivers. The platform dr
 **Figure  1**  OpenHarmony driver classification<a name="fig08631434121"></a>  
 ![](figures/openharmony-driver-classification.png "openharmony-driver-classification")
 
-The Hardware Driver Foundation \(HDF\) is designed to work across OSs. The HDF driver framework provides strong support for drivers to achieve this goal. During HDF driver development, you are advised to use only the APIs provided by the HDF driver framework. Otherwise, the driver cannot be used across OSs. Before driver development, familiarize yourself with the  [HDF](../driver/driver-hdf-overview.md).
+The Hardware Driver Foundation \(HDF\) is designed to work across OSs. The HDF driver framework provides strong support for drivers to achieve this goal. During HDF driver development, you are advised to use only the APIs provided by the HDF driver framework. Otherwise, the driver cannot be used across OSs. Before driver development, familiarize yourself with the [HDF](../driver/driver-overview-foundation.md).
 
diff --git a/en/release-notes/OpenHarmony-v4.0-beta1.md b/en/release-notes/OpenHarmony-v4.0-beta1.md
index 1d3c9d16e9142232790a2a81add7ff960b279c86..45830e1083607c4f84feadb45a9c11fd5d1b66f0 100644
--- a/en/release-notes/OpenHarmony-v4.0-beta1.md
+++ b/en/release-notes/OpenHarmony-v4.0-beta1.md
@@ -382,7 +382,7 @@ This version has the following updates to OpenHarmony 3.2 Release.
 
 ### APIs
 
-For details about the API changes over OpenHarmony 3.2 Release, see [API Differences](/api-diff/v4.0-beta1/Readme-EN.md). A few API changes may affect applications developed using API version 9 or earlier. For details about the change impact and adaptation guide, see [Changelogs](changelogs/v4.0-beta1/Readme-EN.md).
+For details about the API changes over OpenHarmony 3.2 Release, see [API Differences](api-diff/v4.0-beta1/Readme-EN.md). A few API changes may affect applications developed using API version 9 or earlier. For details about the change impact and adaptation guide, see [Changelogs](changelogs/v4.0-beta1/Readme-EN.md).
 
 
 ### Feature Updates
diff --git a/en/website.md b/en/website.md
index 6fd76f7e1bb045c9c35a78556d50343d5e122f24..151e31c6a23d31b4ed9db5058a7552a7defcf8ab 100644
--- a/en/website.md
+++ b/en/website.md
@@ -51,7 +51,6 @@
         - [Distributed Data Management](release-notes/api-diff/v4.0-beta1/js-apidiff-distributed-data.md)
         - [Distributed Hardware](release-notes/api-diff/v4.0-beta1/js-apidiff-distributed-hardware.md)
         - [File Management](release-notes/api-diff/v4.0-beta1/js-apidiff-file-management.md)
-        - [Location](release-notes/api-diff/v4.0-beta1/js-apidiff-geolocation.md)
         - [Globalization](release-notes/api-diff/v4.0-beta1/js-apidiff-global.md)
         - [Graphics](release-notes/api-diff/v4.0-beta1/js-apidiff-graphic.md)
         - [Misc Software](release-notes/api-diff/v4.0-beta1/js-apidiff-misc.md)
@@ -70,36 +69,13 @@
         - [Window Manager](release-notes/api-diff/v4.0-beta1/js-apidiff-window.md)
       - API Changelogs
         - [Ability](release-notes/changelogs/v4.0-beta1/changelogs-ability.md)
-        - [Ability Access Control](release-notes/changelogs/v4.0-beta1/changelogs-accesstoken.md)
-        - [Account](release-notes/changelogs/v4.0-beta1/changelogs-account_os_account.md)
-        - [Notification](release-notes/changelogs/v4.0-beta1/changelogs-ans.md)
         - [Compiler and Runtime](release-notes/changelogs/v4.0-beta1/changelogs-arkcompiler.md)
         - [ArkUI](release-notes/changelogs/v4.0-beta1/changelogs-arkui.md)
-        - [Bluetooth](release-notes/changelogs/v4.0-beta1/changelogs-bluetooth.md)
         - [Bundle Management](release-notes/changelogs/v4.0-beta1/changelogs-bundlemanager.md)
-        - [Common Event](release-notes/changelogs/v4.0-beta1/changelogs-ces.md)
-        - [Distributed Data Management](release-notes/changelogs/v4.0-beta1/changelogs-distributeddatamgr.md)
-        - [File Management](release-notes/changelogs/v4.0-beta1/changelogs-filemanagement.md)
-        - [Location](release-notes/changelogs/v4.0-beta1/changelogs-geoLocationManager.md)
         - [Globalization](release-notes/changelogs/v4.0-beta1/changelogs-global.md)
         - [Security - HUKS](release-notes/changelogs/v4.0-beta1/changelogs-huks.md)
-        - [Input Method Framework](release-notes/changelogs/v4.0-beta1/changelogs-imf.md)
-        - [Multimedia](release-notes/changelogs/v4.0-beta1/changelogs-media.md)
-        - [MISC Software](release-notes/changelogs/v4.0-beta1/changelogs-miscdevice.md)
-        - [Pasteboard](release-notes/changelogs/v4.0-beta1/changelogs-pasteboard.md)
-        - [Power Management](release-notes/changelogs/v4.0-beta1/changelogs-power.md)
         - [Resource Scheduler](release-notes/changelogs/v4.0-beta1/changelogs-resourceschedule.md)
-        - [Theme Framework - Lock Screen](release-notes/changelogs/v4.0-beta1/changelogs-screenlock.md)
-        - [Basic Security Service](release-notes/changelogs/v4.0-beta1/changelogs-security.md)
-        - [Pan-sensor](release-notes/changelogs/v4.0-beta1/changelogs-sensor.md)
-        - [DSoftBus](release-notes/changelogs/v4.0-beta1/changelogs-softbus.md)
-        - [Startup Service](release-notes/changelogs/v4.0-beta1/changelogs-startup.md)
-        - [Telephony](release-notes/changelogs/v4.0-beta1/changelogs-telephony.md)
-        - [Test](release-notes/changelogs/v4.0-beta1/changelogs-testfwk_arkxtest.md)
-        - [USB](release-notes/changelogs/v4.0-beta1/changelogs-usb.md)
-        - [Theme Framework - Wallpaper](release-notes/changelogs/v4.0-beta1/changelogs-wallpaper.md)
         - [Web](release-notes/changelogs/v4.0-beta1/changelogs-web.md)
-        - [WIFI](release-notes/changelogs/v4.0-beta1/changelogs-wifiManager.md)
     - OpenHarmony 3.2 Release (Compared with OpenHarmony 3.1 Release)
       - JS API Differences
         - [Ability](release-notes/api-diff/v3.2-Release/js-apidiff-ability.md)
@@ -332,11 +308,9 @@
     - OpenHarmony v2.2 Beta2
       - [JS API Differences](release-notes/api-diff/v2.2-beta2/js-apidiff-v2.2-beta2.md)
       - [Native API Differences](release-notes/api-diff/v2.2-beta2/native-apidiff-v2.2-beta2.md)
-  
 - OpenHarmony Third-Party Components
   - [Introduction to OpenHarmony Third-Party Components](third-party-components/third-party-components-introduction.md) 
   - [Using OpenHarmony JS and TS Third-Party Components](third-party-components/ohpm-third-party-guide.md)
-
 - Contribution
   - [How to Contribute](contribute/how-to-contribute.md)
   - [Code of Conduct](contribute/code-of-conduct.md)