diff --git a/documentation/source/index.rst b/documentation/source/index.rst
index e15529552a011309052caeadff101d94cf0352e9..eabbad43f2acf4edb0e5f3584cfc4303105eb936 100644
--- a/documentation/source/index.rst
+++ b/documentation/source/index.rst
@@ -3,7 +3,8 @@
 Welcome to |main_project_name| documentation!
 #############################################
 
-|main_project_name| is an open-source project launched by Open Source Technology Center (OSTC). |main_project_name| is a distributed operating system (OS) that is intended to address all conceivable usage scenarios. |main_project_name| is an open-source version of HarmonyOS. HarmonyOS is a future-proof distributed operating system open to you as part of the initiatives for the all-scenario strategy, adaptable to a mobile office, fitness and health, social communication, and media entertainment, and so on. Unlike a legacy operating system that runs on a standalone device, HarmonyOS is built on a distributed architecture designed based on a set of system capabilities. It runs on a wide range of device forms, including smartphones, wearables, tablets, PCs, smart TVs, AI speakers, head units, earphones, and AR/VR glasses.
+|main_project_name| is an open-source project launched by Huawei. |main_project_name| is a future-proof distributed operating system open to you as part of the initiatives for the all-scenario strategy, adaptable to a mobile office, fitness and health, social communication, and media entertainment, and so on. Unlike a legacy Operating system that runs on a standalone device, |main_project_name| is built on a distributed architecture design based on a set of system capabilities. It will run on a wide range of device forms, including smartphones, wearables, tablets, PCs, smart TVs, AI speakers, head units, earphones, and AR/VR glasses.
+
 
 .. toctree::
    :maxdepth: 1
diff --git a/documentation/source/overview/Readme.rst b/documentation/source/overview/Readme.rst
index 6aea449baccf2d3f69631f76219774d3bdfc0bea..0209925d7822918304b40030e5e66d205db9b244 100644
--- a/documentation/source/overview/Readme.rst
+++ b/documentation/source/overview/Readme.rst
@@ -7,7 +7,7 @@
    :maxdepth: 2
    
    
-   about-harmonyOS
+   about-openharmony
    technical-features
    system-security
    
diff --git a/documentation/source/overview/about-harmonyOS.rst b/documentation/source/overview/about-harmonyOS.rst
deleted file mode 100644
index 65768a8ec97c4fa42ceefd57bde9447f0d9010b0..0000000000000000000000000000000000000000
--- a/documentation/source/overview/about-harmonyOS.rst
+++ /dev/null
@@ -1,65 +0,0 @@
-About HarmonyOS
-===============
-
-System Positioning
-------------------
-
-HarmonyOS is a future-proof distributed operating system open to you as part of the initiatives for the all-scenario strategy, adaptable to mobile office, fitness and health, social communication, and media entertainment, to name a few. Unlike a legacy operating system that runs on a standalone device, HarmonyOS is built on a distributed architecture designed based on a set of system capabilities. It is able to run on a wide range of device forms.
-
-Play Video
-
-- If you are an end user, HarmonyOS integrates your various smart devices to implement fast connection, capability collaboration, and resource sharing 
-  between them. This way, your services can be seamlessly transferred to a suitable device that delivers smooth all-scenario experience.
-- If you are an application developer, HarmonyOS adopts distributed technologies to make your application development possible on different device 
-  forms. With HarmonyOS, you will have the choice to focus on upper-layer service logic and develop applications in a much easier and more efficient 
-  way.
-- If you are a device developer, HarmonyOS uses a component-based software design to tailor itself to your particular device forms based on their 
-  respective resource capabilities and service characteristics.
-
-HarmonyOS provides multi-programming-language APIs for you to develop applications. You can choose from Java, Extensible Markup Language (XML), C/C++, JavaScript (JS), Cascading Style Sheets (CSS), and HarmonyOS Markup Language (HML).
-
-Technical Architecture
-----------------------
-
-HarmonyOS is designed with a layered architecture, which from bottom to top consists of the kernel layer, system service layer, framework layer, and application layer. System functions are expanded by levels, from system to subsystem, and further to function/module. In multi-device deployment scenario, unnecessary subsystems, functions, or modules can be excluded from the system as required. The following shows the technical architecture of HarmonyOS.
-
-.. figure:: figures/architecture.png
-   
-   :scale: 50
-   width: 100 px
-   :align: center
-   
-   Figure 1 Technical Architecture
-
-Kernel Layer
-------------
-
-- Kernel subsystem: HarmonyOS uses a multi-kernel design (Linux kernel, HarmonyOS microkernel, or LiteOS) so that appropriate OS kernels can be selected for devices with different resource limitations. The kernel abstraction layer (KAL) shields differences in kernel implementations and provides the upper layer with basic kernel capabilities, including process and thread management, memory management, file system, network management, and peripheral management.
-- Driver subsystem: Hardware Driver Foundation (HDF) lays the foundation for an open HarmonyOS hardware ecosystem. It allows unified access from peripheral devices and provides foundation for driver development and management.
-
-System Service Layer
---------------------
-
-This layer provides a complete set of capabilities essential for HarmonyOS to offer services for applications through the framework layer. The system service layer consists of the following parts:
-
-- Basic system capability subsystem set: Implements distributed application running, scheduling, and migration across HarmonyOS devices. This 
-  subsystem set provides the following basic capabilities: distributed virtual bus, distributed data management, distributed scheduler, utils,  
-  multimode input, graphics, security, and AI.
-- Basic software service subsystem set: Provides HarmonyOS with common and universal software services, including common event and notification, 
-  telephony, multimedia, Design For X (DFX), as well as Mobile Sensing Development Platform (MSDP) & Device Virtualization (DV).
-- Enhanced software service subsystem set: Provides HarmonyOS with differentiated and enhanced software services, including those dedicated to smart 
-  TVs, wearables, IoT devices, and more.
-- Hardware service subsystem set: Provides HarmonyOS with hardware services, including location, biometric recognition, as well as those dedicated to 
-  wearables and IoT devices.
-
-The basic software service, enhanced software service, and hardware service subsystem sets can be tailored by subsystems, and each subsystem can be tailored by functions, depending on the deployment scenario for a particular device form.
-
-Framework Layer
----------------
-
-This layer provides what you need to develop HarmonyOS applications: application framework and ability framework, specific to multiple languages (like Java, C, C++, and JS), Java and JS UI frameworks, as well as multi-language APIs for hardware and software services. The APIs designed for different HarmonyOS devices vary according to component-based tailoring.
-
-Application Layer
------------------
-
-This layer consists of system applications and third-party applications. Each HarmonyOS application is powered by one or more Feature Abilities (FAs) or Particle Abilities (PAs). An FA provides a UI for user interaction. A PA has no UI and provides background task processing as well as data access. Applications developed based on FAs and PAs implement specific business characteristics and achieve cross-device scheduling and distribution, delighting users with consistent and efficient experience.
diff --git a/documentation/source/overview/about-openharmony.rst b/documentation/source/overview/about-openharmony.rst
new file mode 100644
index 0000000000000000000000000000000000000000..943854ca5752743c6957d9f1be10b9a6af46b67c
--- /dev/null
+++ b/documentation/source/overview/about-openharmony.rst
@@ -0,0 +1,68 @@
+
+.. include:: ../definitions.rst
+
+About |main_project_name|
+=====================
+
+System Positioning
+---------------------------
+
+|main_project_name| is a future-proof distributed operating system open to you as part of the initiatives for the all-scenario strategy, adaptable to mobile office, fitness and health, social communication, and media entertainment, to name a few. Unlike a legacy operating system that runs on a standalone device, |main_project_name| is built on a distributed architecture designed based on a set of system capabilities. It is able to run on a wide range of device forms.
+
+Play Video
+
+- If you are an end user, |main_project_name| integrates your various smart devices to implement fast connection, capability collaboration, and resource sharing 
+  between them. This way, your services can be seamlessly transferred to a suitable device that delivers smooth all-scenario experience.
+- If you are an application developer, |main_project_name| adopts distributed technologies to make your application development possible on different device 
+  forms. With |main_project_name|, you will have the choice to focus on upper-layer service logic and develop applications in a much easier and more efficient 
+  way.
+- If you are a device developer, |main_project_name| uses a component-based software design to tailor itself to your particular device forms based on their 
+  respective resource capabilities and service characteristics.
+
+|main_project_name| provides multi-programming-language APIs for you to develop applications. You can choose from Java, Extensible Markup Language (XML), C/C++, JavaScript (JS), Cascading Style Sheets (CSS), and |main_project_name| Markup Language (HML).
+
+Technical Architecture
+----------------------
+
+|main_project_name| is designed with a layered architecture, which from bottom to top consists of the kernel layer, system service layer, framework layer, and application layer. System functions are expanded by levels, from system to subsystem, and further to function/module. In multi-device deployment scenario, unnecessary subsystems, functions, or modules can be excluded from the system as required. The following shows the technical architecture of |main_project_name|.
+
+.. figure:: figures/architecture.png
+   
+   :scale: 50
+   width: 100 px
+   :align: center
+   
+   Figure 1 Technical Architecture
+
+Kernel Layer
+------------------
+
+- Kernel subsystem: |main_project_name| uses a multi-kernel design (Linux kernel, |main_project_name| microkernel, or LiteOS) so that appropriate OS kernels can be selected for devices with different resource limitations. The kernel abstraction layer (KAL) shields differences in kernel implementations and provides the upper layer with basic kernel capabilities, including process and thread management, memory management, file system, network management, and peripheral management.
+- Driver subsystem: Hardware Driver Foundation (HDF) lays the foundation for an open |main_project_name| hardware ecosystem. It allows unified access from peripheral devices and provides foundation for driver development and management.
+
+System Service Layer
+------------------------------
+
+This layer provides a complete set of capabilities essential for |main_project_name| to offer services for applications through the framework layer. The system service layer consists of the following parts:
+
+- Basic system capability subsystem set: Implements distributed application running, scheduling, and migration across |main_project_name| devices. This 
+  subsystem set provides the following basic capabilities: distributed virtual bus, distributed data management, distributed scheduler, utils,  
+  multimode input, graphics, security, and AI.
+- Basic software service subsystem set: Provides |main_project_name| with common and universal software services, including common event and notification, 
+  telephony, multimedia, Design For X (DFX), as well as Mobile Sensing Development Platform (MSDP) & Device Virtualization (DV).
+- Enhanced software service subsystem set: Provides |main_project_name| with differentiated and enhanced software services, including those dedicated to smart 
+  TVs, wearables, IoT devices, and more.
+- Hardware service subsystem set: Provides |main_project_name| with hardware services, including location, biometric recognition, as well as those dedicated to 
+  wearables and IoT devices.
+
+The basic software service, enhanced software service, and hardware service subsystem sets can be tailored by subsystems, and each subsystem can be tailored by functions, depending on the deployment scenario for a particular device form.
+
+Framework Layer
+---------------
+
+This layer provides what you need to develop |main_project_name| applications: application framework and ability framework, specific to multiple languages (like Java, C, C++, and JS), Java and JS UI frameworks, as well as multi-language APIs for hardware and software services. The APIs designed for different |main_project_name| devices vary according to component-based tailoring.
+
+Application Layer
+-----------------
+
+This layer consists of system applications and third-party applications. Each |main_project_name| application is powered by one or more Feature Abilities (FAs) or Particle Abilities (PAs). An FA provides a UI for user interaction. A PA has no UI and provides background task processing as well as data access. Applications developed based on FAs and PAs implement specific business characteristics and achieve cross-device scheduling and distribution, delighting users with consistent and efficient experience.
diff --git a/documentation/source/overview/system-security.rst b/documentation/source/overview/system-security.rst
index f84c443e572a6828083fe567b5773f250a1bbbdd..4aff4262118dc170212b9a5254a6036987440fb9 100644
--- a/documentation/source/overview/system-security.rst
+++ b/documentation/source/overview/system-security.rst
@@ -3,7 +3,7 @@
 System Security
 ===============
 
-HarmonyOS-powered distributed devices ensure that the right person uses the right data through the right device.
+|main_project_name|-powered distributed devices ensure that the right person uses the right data through the right device.
 
 - Ensure the right person by performing distributed collaborative identity authentication.
 - Ensure the right device by building a trusted operating environment on the distributed device.
@@ -12,9 +12,9 @@ HarmonyOS-powered distributed devices ensure that the right person uses the righ
 Right Person
 ------------
 
-In the distributed scenario, the right person refers to an authenticated user who accesses the data or uses the service. The right person is the prerequisite for preventing illegal data access or user privacy breach. HarmonyOS implements distributed collaborative identity authentication in the following ways:
+In the distributed scenario, the right person refers to an authenticated user who accesses the data or uses the service. The right person is the prerequisite for preventing illegal data access or user privacy breach. |main_project_name| implements distributed collaborative identity authentication in the following ways:
 
-- **Zero-trust model**: Implements user authentication and data access control. When a user attempts to access data across devices or perform a service operation with a high security level (for example, operating a security protection device), HarmonyOS authenticates the user to ensure that the user is authorized to perform the operation.
+- **Zero-trust model**: Implements user authentication and data access control. When a user attempts to access data across devices or perform a service operation with a high security level (for example, operating a security protection device), |main_project_name| authenticates the user to ensure that the user is authorized to perform the operation.
 
 - **Multi-factor authentication**: Associates authentication credentials that identify the same user on different devices to improve authentication accuracy.
 
@@ -24,11 +24,11 @@ Right Device
 ------------
 In the distributed scenario, the right person using the right device is the prerequisite to safeguard effective user data security on virtual devices and prevent user privacy breach.
 
-- **Secure boot** : HarmonyOS ensures from the source that the system firmware and applications running on each virtual device from the source are intact and untampered with. With secure boot, HarmonyOS protects image packages of device vendors from being replaced maliciously, thereby ensuring user data security and privacy.
+- **Secure boot** : |main_project_name| ensures from the source that the system firmware and applications running on each virtual device from the source are intact and untampered with. With secure boot, |main_project_name| protects image packages of device vendors from being replaced maliciously, thereby ensuring user data security and privacy.
 
-- **TEE** : HarmonyOS provides a hardware-based Trusted Execution Environment (TEE) to prevent data leakage of sensitive personal data when they are stored or processed. As the hardware of distributed devices varies in security capabilities, security issues may arise if sensitive personal data of users is stored and processed by devices with a low security level. To address this issue, HarmonyOS uses formal verification methods, which are an effective mathematical approach to validate system correctness, to secure the TEE microkernel. This helps the microkernel successfully achieve a CC EAL5+ certification for a commercial OS kernel.
+- **TEE** : |main_project_name| provides a hardware-based Trusted Execution Environment (TEE) to prevent data leakage of sensitive personal data when they are stored or processed. As the hardware of distributed devices varies in security capabilities, security issues may arise if sensitive personal data of users is stored and processed by devices with a low security level. To address this issue, |main_project_name| uses formal verification methods, which are an effective mathematical approach to validate system correctness, to secure the TEE microkernel. This helps the microkernel successfully achieve a CC EAL5+ certification for a commercial OS kernel.
 
-- **Device certificate authentication**: HarmonyOS preconfigures a public key infrastructure (PKI) device certificate in the TEE of a device so that the device can prove its security capabilities to other virtual devices. The device certificate ensures that the device is one that was manufactured legally. The certification is preconfigured during device production and proves that the device was manufactured legally. The private key of the certification is written and securely stored in the TEE and can only be used in the TEE. When sensitive user data (such as keys and encrypted biometrics) needs to be transmitted between devices, a secure channel is established between their TEEs only after the device security has been proven using the device certificate. The below figure shows how the device certificate is used.
+- **Device certificate authentication**: |main_project_name| preconfigures a public key infrastructure (PKI) device certificate in the TEE of a device so that the device can prove its security capabilities to other virtual devices. The device certificate ensures that the device is one that was manufactured legally. The certification is preconfigured during device production and proves that the device was manufactured legally. The private key of the certification is written and securely stored in the TEE and can only be used in the TEE. When sensitive user data (such as keys and encrypted biometrics) needs to be transmitted between devices, a secure channel is established between their TEEs only after the device security has been proven using the device certificate. The below figure shows how the device certificate is used.
 
 .. figure:: figures/system_security.jpg
    :scale: 50
@@ -39,7 +39,7 @@ In the distributed scenario, the right person using the right device is the prer
 Right Data
 ----------
 
-To ensure that the right data is used by the right person, HarmonyOS protects data security and privacy throughout the entire lifecycle, from data generation and storage to data use, transmission, and destruction. This ensures that personal data and privacy as well as confidential data (such as keys) are strictly protected against disclosure.
+To ensure that the right data is used by the right person, |main_project_name| protects data security and privacy throughout the entire lifecycle, from data generation and storage to data use, transmission, and destruction. This ensures that personal data and privacy as well as confidential data (such as keys) are strictly protected against disclosure.
 
 - **Data generation**: Data is categorized and classified in compliance with local laws and regulations, and different protection levels are configured for the data based on the classification. For data granted with a specific protection level, security protection is implemented based on the corresponding security policy throughout the entire lifecycle. The access control system of the super virtual device supports tag-based access control policies, which ensure that data can be stored, used, and transmitted only on virtual devices that are able to provide effective security protection.
 
diff --git a/documentation/source/overview/technical-features.rst b/documentation/source/overview/technical-features.rst
index b80700edf4f18f8fd0936f7fff7e4a390274691f..f2a30652db109bb0e31bc93263287c0ae534c2f3 100644
--- a/documentation/source/overview/technical-features.rst
+++ b/documentation/source/overview/technical-features.rst
@@ -46,7 +46,7 @@ Distributed task scheduling is designed based on technical features such as dist
 One-Time Development for Multi-Device Deployment
 ------------------------------------------------
 
-HarmonyOS provides the application, ability, and UI frameworks, which allow you to reuse service and UI logic during application development. This way, you can develop your applications once, and then deploy them across a broad range of devices, improving your development efficiency. Figure 5 shows the diagram of one-time development and multi-device deployment.
+|main_project_name| provides the application, ability, and UI frameworks, which allow you to reuse service and UI logic during application development. This way, you can develop your applications once, and then deploy them across a broad range of devices, improving your development efficiency. Figure 5 shows the diagram of one-time development and multi-device deployment.
 
 .. figure:: figures/muti-device.png
 
@@ -55,7 +55,7 @@ HarmonyOS provides the application, ability, and UI frameworks, which allow you
 Unified OS for Flexible Deployment
 ----------------------------------
 
-HarmonyOS leverages component-based and miniaturized-oriented designs to allow on-demand deployment for diversified devices, adapting to different hardware resources and business characteristics. Specifically, component dependencies are automatically generated based on the cross-compilation toolchain to form a tree diagram illustrating component dependencies, facilitating convenient development and making development available for various devices, regardless of their hardware capabilities.
+|main_project_name| leverages component-based and miniaturized-oriented designs to allow on-demand deployment for diversified devices, adapting to different hardware resources and business characteristics. Specifically, component dependencies are automatically generated based on the cross-compilation toolchain to form a tree diagram illustrating component dependencies, facilitating convenient development and making development available for various devices, regardless of their hardware capabilities.
 
 - **On-demand component selection**: You can select required components based on hardware forms and requirements.