diff --git a/documentation/source/conf.py b/documentation/source/conf.py
index 3f16dbfe1c799f6d2fedaf0ce96992c9e8a8a3a0..9a15be78f558389f1381d76e3dd5a19aaab2a70d 100644
--- a/documentation/source/conf.py
+++ b/documentation/source/conf.py
@@ -17,7 +17,7 @@
 
 # -- Project information -----------------------------------------------------
 
-project = 'Harmony-OS'
+project = 'OpenHarmony'
 copyright = '2021'
 author = 'OSTC'
 
diff --git a/documentation/source/index.rst b/documentation/source/index.rst
index e887a25c903f3cbc4662d062703cd8c30ec2478d..e15529552a011309052caeadff101d94cf0352e9 100644
--- a/documentation/source/index.rst
+++ b/documentation/source/index.rst
@@ -3,6 +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.
+
 .. toctree::
    :maxdepth: 1
       
diff --git a/documentation/source/quick-start/build-open-harmony.rst b/documentation/source/quick-start/build-open-harmony.rst
index 85446a51295f2232e4f5bfff1b2cd5190715d489..1f315ad438c9525570a6ff34754909e4f012a84a 100644
--- a/documentation/source/quick-start/build-open-harmony.rst
+++ b/documentation/source/quick-start/build-open-harmony.rst
@@ -10,6 +10,9 @@ Getting Started
 This topic provides an overview of meta-ohos architecture, tools, and source code required to build your |main_project_name| image. The meta-ohos is an umbrella meta-layer containing all layers required to build
 |main_project_name| Image on existing kernel meta-layers.
 
+.. toctree:: 
+   :depth: 2 
+
 
 **Figure 1 meta-ohos overview**
 
@@ -17,7 +20,7 @@ This topic provides an overview of meta-ohos architecture, tools, and source cod
      :align: center
      :alt: meta-ohos overview
 
-.. _tool-acquisition:
+.. _downloading-tools:
 
 Downloading Tools
 ***********************
@@ -30,7 +33,7 @@ To start with, you need to install git-repo by executing the following command.
    $ sudo apt-get update
    $ sudo apt-get install git-repo
 
-.. _source-code-acquisition:
+.. _downloading-source-code:
 
 Downloading Source Code
 ********************************
diff --git a/documentation/source/readme/Communication in Community.rst b/documentation/source/readme/Communication in Community.rst
index 76691e62de669c0207372b7bb1512eb688cfe5c5..acdd1fcee7ed4328547e03ba203557ca7c581f74 100644
--- a/documentation/source/readme/Communication in Community.rst	
+++ b/documentation/source/readme/Communication in Community.rst	
@@ -24,18 +24,5 @@ If you have never subscribed to a mail list before, follow the steps below:
 Email Address           Introduction                  Description
 ======================= ============================= ================================================================================================
 |contact_info|  Public Mailbox                Public mailbox of the OpenHarmony community. 
-                                                      You can send emails to this mailbox to sign the Contributor License Agreement (CLA).
-dev@openharmony.io      Development mail list         OpenHarmony community development discussion group. 
-                                                      Any topics related to community development  can be discussed here. Any one can `subscribe <https://lists.openatom.io/postorius/lists/dev.openharmony.io/>`_ to it. 
-cicd@openharmony.io     CI mail list                  The OpenHarmony community CI/CD builds a mail list that any developer can `subscribe <https://lists.openatom.io/postorius/lists/cicd.openharmony.io/>`_ to.
-pmc@openharmony.io      PMC mail list                 Mail list for PMC discussion. It can be `subscribed <https://lists.openatom.io/postorius/lists/pmc.openharmony.io/>`_ to by PMC members
-scy@openharmony.io      Mail list for security issues Email address for you to report OpenHarmony security issues.
-scy-priv@openharmony.io Security group mail list      The security group members can `subscribe <https://lists.openatom.io/postorius/lists/scy-priv.openharmony.io/>`_ to this email list to discuss security issues.
-======================= ============================= ================================================================================================
-
-How Do I Send Emails to a Mail List?
-************************************
 
-To send an email to a specified mail list, send your email to the address listed in the table above.
-
-In this way, all community members in this mail list will receive your email.
+======================= ============================= ================================================================================================
diff --git a/documentation/source/readme/Contributing to the Code.rst b/documentation/source/readme/Contributing to the Code.rst
index f902b5177c22e5c1687c1f9e189453006179bb24..b3a0e7d2b93d7f6229172201157a042f7ed3ac6f 100644
--- a/documentation/source/readme/Contributing to the Code.rst	
+++ b/documentation/source/readme/Contributing to the Code.rst	
@@ -20,8 +20,3 @@ Contribution Workflow
 *********************
 
 For details, see `Contribution Process <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contribution%20Process.rst>`_.
-
-Security Issue Disclosure
-*************************
-* Security handling procedure
-* Security disclosure information
diff --git a/readme.rst b/readme.rst
index 1745bc2c7498ec48387913ca3f0f56445a5fafe7..fecc6fc3646da388183954bc91e0a88fa04efd18 100644
--- a/readme.rst
+++ b/readme.rst
@@ -1,46 +1,49 @@
 Welcome to Open Harmony
 ########################
-OpenHarmony is an open-source project launched by the OpenAtom Foundation and serves as an open-source, distributed operating system (OS) that is intended to address all conceivable usage scenarios. OpenHarmony 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 is able to run on a wide range of device forms, including smartphones, wearables, tablets, PCs, smart TVs, AI speakers, head units, earphones, and AR/VR glasses.
+OpenHarmony is an open-source project launched by Huawei. OpenHarmony 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, OpenHarmony 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.
 
 Motivation
-**********
-The traditional OSs are limited to a specific type of device, OpenHarmony provides distributed features that are compatible with a wide range of different devices. The first version supports devices with 128 KB to 128 MB of memory. Join us as we keep updating OpenHarmony versions. For device developers, OpenHarmony utilizes a component-based design to tailor its features to better suit specific devices, based on each device's capabilities and service characteristics. OpenHarmony can run on devices with limited resources and wearables with hundreds of KB of memory, as well as more powerful devices, such as smart home cameras and dashcams with hundreds of MB of memory.
+*************
+The traditional Operating Systems are limited to a specific type of device, whereas OpenHarmony is a device independent platform. OpenHarmony provides distributed features that are compatible with a wide range of different devices. The initial version supports devices with 128 KB to 128 MB of memory and the subsequent versions will support higher memory and advanced devices. OpenHarmony will be developed as part of **Eclipse Working Group** and we welcome you to join us in this journey of improving one of the advanced device-independent operating system platform. For device developers, OpenHarmony utilizes a component-based design to tailor its features to better suit specific devices, based on each device's capabilities and service characteristics. OpenHarmony can run on devices with limited resources and wearables with hundreds of KB of memory, as well as more powerful devices, such as smart home cameras and dashcams with hundreds of MB of memory.
 
 OpenHarmony Documentation
 ***********************************
 * `Getting Started <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/quick-start/build-open-harmony.rst>`_
-* `Supported Boards <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/quick-start/supported-boards.rst>`_
+* `Supported Boards <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/MainReadme/documentation/source/supported-boards/Readme.rst>`_
 
-For latest OpenHarmony Documentation, `Click <https://openharmony-documentation.readthedocs.io>`_.
+For the latest OpenHarmony Documentation, `Click <https://openharmony-documentation.readthedocs.io>`_.
 
-Start Contributing
-******************
-OpenHarmony is an Open Source Community and encourages everyone in the community to submit the patches directly to the project. You can either contribute to the code or documentation.
+Get Source Code and Tools
+*********************************
+The first thing to do is to get the required tools and source code for the development and contribution purpose. Here are the links to download the tools and source code. Once you finish downloading, you can refer to the Contribution Guidelines for more details on the process and style guides used.
 
-* `Contributing to the Code <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contributing%20to%20the%20Code.rst>`_
-* `Contributing to the Documentation <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contributing%20to%20the%20Documentation.rst>`_
+* `Downloading Tools <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/quick-start/build-open-harmony.rst#downloading-tools>`_
 
-For more details on Contribution, see `Contributing to the Documentation <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contributing%20to%20the%20Documentation.rst>`_.
+* `Downloading Source Code <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/quick-start/build-open-harmony.rst#downloading-source-code>`_
 
-Get Source Code and Tools
-*********************************
-To download the source code and tools required for the project, click the following links:
+Contribution Guidelines
+***************************
+We welcome you to join the project OpenHarmony and support us in building an Open Source Community and encourages everyone in the community to submit the patches directly to the project. Based on your interest and expertise, you can contribute to the code or/and documentation.
 
-* Downloading Tools
-* Downloading Source Code
+* To know the contribution workflow on how to download code and contribute your code back to the repository, please refere `Contribution Process <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/readme/Contribution%20Process.rst>`_. 
+* To contribute to documentation, please refere `Contributing to the Documentation <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contributing%20to%20the%20Documentation.rst>`_. 
+* All our documents are written in reStructuredText for easy of writing and processing to different format. You can use ReadTheDoc to publish our documents into anyformat you want, or locally generate the required format output using the Sphinx document generator. For more details, please refere `Documentation using Sphinx <https://git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/-/blob/master/documentation/source/readme/reStructuredText%20Basics.rst>`_
+* In order to maintain consistency across code base, please refere to the `coding style guide <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Contributing%20to%20the%20Code.rst>`_ before you stat contributing to the code base of OpenHarmony.
 
 Where to Turn for Help
-**********************
+**************************
 You can subscribe to the mailing list to get constant updates on new features, release road maps, and community activities. For Subscribing to the mailing list or any other support, see `Communication in Community <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Communication%20in%20Community.rst>`_.
 
 Code of Conduct
-***************
-OpenHarmony is committed to providing a welcoming and inspiring community for all. In order to maintain a collaborative environment, we recommend you to read and follow the community `Code of Conduct <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Code%20of%20Conduct.rst>`_.
+********************
+OpenHarmony is committed to provide a welcoming and inspiring community for all. In order to maintain a collaborative environment, we recommend you to read and follow the community `Code of Conduct <https://git.ostc-eu.org/docs/developer-guide/-/blob/master/documentation/source/readme/Code%20of%20Conduct.rst>`_.
 
 Contributors & Acknowledgements
-*******************************
+***************************************
 A great Open source project wouldn't exist without the hard work of its many contributors. We'd like to invite anyone from around the world to participate in this exciting journey. And we're grateful for your time, passion, and efforts!
 
 Release
-*******
+***********
 In order to provide new features and bug fixes, the community constantly updates the code and provides new releases.
+
+