diff --git a/README.md b/README.md
index fd9d361e5923600f3604e91448dc43fb4e3b0d7d..bb06b90f6a7576f160ec64917b6060e9bf8ffea6 100644
--- a/README.md
+++ b/README.md
@@ -26,4 +26,4 @@ OpenHarmony 2.0 Canary. [Learn more](en/release-notes/openharmony-2-0-canary.md)
OpenHarmony_v1.x_release: OpenHarmony v1.1.2 LTS. [Learn more](en/release-notes/OpenHarmony-v1.1.2-LTS.md)
-[More versions](https://gitee.com/openharmony/docs/blob/master/en/release-notes/)
+[More versions](en/release-notes/)
diff --git a/en/OpenHarmony-Overview.md b/en/OpenHarmony-Overview.md
index 2e90b1a038c02932edf499a66363f55a594f3e91..58a358b03da84dadadb94a8600a2998c02d5defd 100644
--- a/en/OpenHarmony-Overview.md
+++ b/en/OpenHarmony-Overview.md
@@ -344,7 +344,7 @@ The following table describes the subsystems of OpenHarmony. For details about t
## Getting Started
-For details, see [https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/Readme-EN.md](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/Readme-EN.md).
+For details, see [device-dev/quick-start/Readme-EN.md](device-dev/quick-start/Readme-EN.md).
## Code Repository Addresses
diff --git a/en/contribute/Readme-EN.md b/en/contribute/Readme-EN.md
index e1cc5652e4436769cb38126b318a0d587177a3fc..8ac3b563d2274fdea813fd8eb8a4ac80917ab04f 100755
--- a/en/contribute/Readme-EN.md
+++ b/en/contribute/Readme-EN.md
@@ -4,6 +4,7 @@
- [Code of Conduct](code-of-conduct.md)
- [Code Contribution](code-contribution.md)
- [Contribution Process](contribution-process.md)
+- [Auto-Test](../readme/test_subsystem.md)
- [Documentation Contribution](documentation-contribution.md)
- [Writing Instructions](writing-instructions.md)
- [Communication in Community](communication-in-community.md)
diff --git a/en/contribute/contribution-process.md b/en/contribute/contribution-process.md
index 9fa4be4fa4e8beb8051004e43408982a084fffa9..de1dc328fe27122ddc3b5a9f977b75709c74782e 100755
--- a/en/contribute/contribution-process.md
+++ b/en/contribute/contribution-process.md
@@ -242,7 +242,7 @@ Visit [CI portal](http://ci.openharmony.cn/#/pipeLine).
## Reviewing Code
-For details, visit [https://gitee.com/help/articles/4304](https://gitee.com/help/articles/4304).
+For details, visit [https://gitee.com/help/articles/4304](https://gitee.com/help/articles/4304).
-Related topic: [FAQs](faqs.md)
+Related topic: [FAQs](faqs.md)
diff --git a/en/contribute/contribution.md b/en/contribute/contribution.md
index 0b954ea421d608e49e289329bea05441bdb8d5e2..2819f40f16c3eaa4ff1454f9d475fe372d39c874 100755
--- a/en/contribute/contribution.md
+++ b/en/contribute/contribution.md
@@ -22,6 +22,10 @@ For details about how to participate in Special Interest Group (SIG), see **SIG
For details about how to contribute to code, see [Code Contributing ](code-contribution.md).
+## Auto-Test
+
+For details about how to develop test cases based on test requirements, see [Test Subsystem](../readme/test_subsystem.md).
+
## Contributing Documents
For details, see [Documentation Contribution](documentation-contribution.md).
diff --git a/en/readme/test_subsystem.md b/en/readme/test_subsystem.md
index 41e56907b26ef35d2e06e660c57c8390fee52b49..cf40a80413f8169ff33c47a2b841bd822fa594f6 100644
--- a/en/readme/test_subsystem.md
+++ b/en/readme/test_subsystem.md
@@ -63,7 +63,7 @@ subsystem # Subsystem
### Writing Test Cases
This test framework supports test cases written in multiple programming languages and provides different templates for different languages.
-**C++ Test Case Example**
+#### C++ Test Case Example
- Naming rules for source files
@@ -243,7 +243,7 @@ Example:
|Fuzz test |FUZZ|
-**JavaScript Test Case Example**
+#### JavaScript Test Case Example
- Naming rules for source files
@@ -612,7 +612,7 @@ The following provides templates for different languages for your reference.
}
```
> **Note**: Grouping test cases by test type allows you to execute a specific type of test cases when required.
-
+
#### Configuring ohos.build
Configure the part build file to associate with specific test cases.
@@ -731,7 +731,7 @@ When the build is complete, the test cases are automatically saved in the **out/
1. On Windows, create the **Test** directory in the test framework and then create the **testcase** directory in the **Test** directory.
2. Copy **developertest** and **xdevice** from the Linux environment to the **Test** directory on Windows, and copy the test cases to the **testcase** directory.
- >**Note**: Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
+>**Note**: Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
3. Modify the **user_config.xml** file.
```