chore: format all documents

Signed-off-by: peefy <[email protected]>
kcl-lang · Nov 29, 2023 · b1796ef · b1796ef
1 parent 1ec4494
commit b1796ef
Show file tree

Hide file tree

Showing 44 changed files with 432 additions and 612 deletions.
diff --git a/docs/community/contribute/git-guideline.md b/docs/community/contribute/git-guideline.md
@@ -32,7 +32,7 @@ The branch name mainly includes two fields, which are separated by "-". Includin
 
 For example, Alice first transfers the Fork warehouse to his own account, and then creates a branch with the corresponding name 'alice: fix output fmt bug' (Alice's account is before the colon) to fix the output formatting bug.
 
-## 3. 关于 Git Commit
+## 3. About Git Commit
 
 We refer to [Commitizen](https://github.com/commitizen/cz-cli) to write a Commit Message.
 

diff --git a/docs/community/release-policy/kcl.md b/docs/community/release-policy/kcl.md
@@ -14,7 +14,7 @@ The KCL project version release strategy is as follows:
 ## Release Process and Rules
 
 - Feature Development: Main branch development, branch releases, block user issues, critical bugs, security vulnerabilities, and high-priority fixes. It is given higher priority over general feature development and should be completed within a week.
-Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months.
+- Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months.
 - Version Planning: Two weeks before the release, an alpha version is produced, followed by a beta version one week before the release. Alpha versions can still include feature merging, while beta versions only include bug fixes. The final release version is tagged as a long-term saved release branch.
 - Release Plan: A detailed release plan (Github Milestone) is created at the beginning of each release cycle, including release dates, version numbers, feature lists, and testing plans. The release plan should be followed as closely as possible to ensure timely releases.
 - Pre-release Testing: Comprehensive testing, including unit testing, integration testing, fuzz testing, stress testing, and user acceptance testing, is conducted before releasing a new version. The new version is only released when it passes all tests without any issues.