解决合并冲突，保留中文翻译版本

Signed-off-by: cchongyang <[email protected]>

Author: cchongyang

.github/ISSUE_TEMPLATE/good-first.md

@@ -28,4 +28,4 @@ Then, the issue will be assigned to you.
 **How to ask for help**:
 
 If you need help or have questions, please feel free to ask on this issue.
-The issue author or other members of the community will guide you through the contribution process.
+The issue author or other members of the community will guide you through the contribution process.

.github/workflows/main.yml

@@ -13,7 +13,6 @@ on:
         required: true
 
 jobs:
-
   build:
     runs-on: ubuntu-22.04
     strategy:

.github/workflows/markdownlint.yml

@@ -0,0 +1,21 @@
+name: Lint Workflow
+
+on:
+  pull_request:
+    paths-ignore:
+      - "**.svg"
+      - "**.png"
+
+jobs:
+  build:
+    runs-on: ubuntu-22.04
+    strategy:
+      matrix:
+        go-version: ["1.23"]
+
+    steps:
+      - uses: actions/checkout@v3
+      - uses: DavidAnson/markdownlint-cli2-action@v20
+        with:
+          globs: "**/*.md,!docs/ctl"
+          separator: ","

.markdownlint.yml

@@ -0,0 +1,8 @@
+line-length: false
+no-inline-html: false
+first-line-heading: false
+no-alt-text: false
+ol-prefix: false
+no-duplicate-heading: false
+single-h1: false
+no-emphasis-as-heading: false

CODE_OF_CONDUCT.md

@@ -2,4 +2,4 @@
 
 Kmesh follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected].
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <[email protected]>.

CONTRIBUTING.md

@@ -17,39 +17,39 @@ Welcome to Kmesh!
   - [Code Review](#code-review)
 - [Membership](#membership)
 
-# Before you get started
+## Before you get started
 
-## Code of Conduct
+### Code of Conduct
 
 Please make sure to read and observe our [Code of Conduct](/CODE_OF_CONDUCT.md).
 
-## Community Expectations
+### Community Expectations
 
 Kmesh is a community project driven by its community which strives to promote a healthy, friendly and productive environment.
 Kmesh aims to provide turnkey automation for multi-cluster application management in multi-cloud and hybrid cloud scenarios,
 and intended to realize multi-cloud centralized management, high availability, failure recovery and traffic scheduling.
 
-# Getting started
+## Getting started
 
 - Fork the repository on GitHub.
 - Make your changes on your fork repository.
 - Submit a PR.
 
-# Your First Contribution
+## Your First Contribution
 
 We will help you to contribute in different areas like filing issues, developing features, fixing critical bugs and
 getting your work reviewed and merged.
 
 If you have questions about the development process,
 feel free to [file an issue](https://github.com/Kmesh-net/Kmesh/issues/new/choose).
 
-## Find something to work on
+### Find something to work on
 
 We are always in need of help, be it fixing documentation, reporting bugs or writing some code.
 Look at places where you feel best coding practices aren't followed, code refactoring is needed or tests are missing.
 Here is how you get started.
 
-### Find a good first topic
+#### Find a good first topic
 
 There are [multiple repositories](https://github.com/Kmesh-net/) within the Kmesh organization.
 Each repository has beginner-friendly issues that provide a good first issue.
@@ -66,7 +66,7 @@ Please see [Contributing](#contributing) below for the workflow.
 
 When you are willing to take on an issue, just reply on the issue. The maintainer will assign it to you.
 
-### File an Issue
+#### File an Issue
 
 While we encourage everyone to contribute code, it is also appreciated when someone reports an issue.
 Issues should be filed under the appropriate Kmesh sub-repository.
@@ -75,7 +75,7 @@ Issues should be filed under the appropriate Kmesh sub-repository.
 
 Please follow the prompted submission guidelines while opening an issue.
 
-# Contributor Workflow
+## Contributor Workflow
 
 Please do not ever hesitate to ask a question or send a pull request.
 
@@ -86,28 +86,28 @@ This is a rough outline of what a contributor's workflow looks like:
 - Push changes in a topic branch to a personal fork of the repository.
 - Submit a pull request to [Kmesh-net/Kmesh](https://github.com/Kmesh-net/Kmesh).
 
-## Creating Pull Requests
+### Creating Pull Requests
 
 Pull requests are often called simply "PR".
 Kmesh generally follows the standard [github pull request](https://help.github.com/articles/about-pull-requests/) process.
 To submit a proposed change, please develop the code/fix and add new test cases.
 After that, run these local verifications before submitting pull request to predict the pass or
 fail of continuous integration.
 
-* Run and pass `make gen-check`, if want to run with sudo privileges `sudo env PATH=$PATH make gen-check`
-* To compile, refer to [Compile and Build Kmesh](https://kmesh.net/en/docs/developer/build-guide/)
-* To run unit test, refer to [Run Unit Test](https://kmesh.net/en/docs/developer/run-ut/)
-* To run e2e test, refer to [Run E2E Test](https://kmesh.net/en/docs/developer/e2e-guide/)
+- Run and pass `make gen-check`, if want to run with sudo privileges `sudo env PATH=$PATH make gen-check`
+- To compile, refer to [Compile and Build Kmesh](https://kmesh.net/en/docs/developer/build-guide/)
+- To run unit test, refer to [Run Unit Test](https://kmesh.net/en/docs/developer/run-ut/)
+- To run e2e test, refer to [Run E2E Test](https://kmesh.net/en/docs/developer/e2e-guide/)
 
-## Code Review
+### Code Review
 
 To make it easier for your PR to receive reviews, consider the reviewers will need you to:
 
-* follow [good coding guidelines](https://github.com/golang/go/wiki/CodeReviewComments).
-* write [good commit messages](https://chris.beams.io/posts/git-commit/).
-* break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue.
+- follow [good coding guidelines](https://github.com/golang/go/wiki/CodeReviewComments).
+- write [good commit messages](https://chris.beams.io/posts/git-commit/).
+- break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue.
 
-# Membership
+## Membership
 
 We encourage all contributors to become members. Learn more about requirements and responsibilities of membership in our [Community Membership doc](https://kmesh.net/docs/community/membership/).
 

README-zh.md

@@ -21,31 +21,31 @@ Kmesh创新性的提出将流量治理下沉OS，在数据路径上无需经过
 
 ### Kmesh关键特性
 
-**平滑兼容**
+#### 平滑兼容
 
 - 应用透明的流量治理
 - 自动对接Istiod
 
-**高性能**
+#### 高性能
 
 - 网格转发时延**60%↓**
 - 服务启动性能**40%↑**
 
-**低开销**
+#### 低开销
 
 - 网格底座开销**70%↓**
 
-**安全隔离**
+#### 安全隔离
 
 - ebpf虚机安全
 - cgroup级编排隔离
 
-**全栈可视化**
+#### 全栈可视化
 
 - 端到端指标采集*
 - 主流观测平台对接*
 
-**开放生态**
+#### 开放生态
 
 - 支持XDS协议标准
 
@@ -55,7 +55,7 @@ Kmesh创新性的提出将流量治理下沉OS，在数据路径上无需经过
 
 - 前提条件
 
-  - Kmesh当前是对接Istio控制面，启动Kmesh前，需要提前安装好Istio的控制面软件；具体安装步骤参考：https://istio.io/latest/docs/setup/getting-started/#install
+  - Kmesh当前是对接Istio控制面，启动Kmesh前，需要提前安装好Istio的控制面软件；具体安装步骤参考：<https://istio.io/latest/docs/setup/getting-started/#install>
   - 完整的Kmesh能力依赖对OS的增强，需确认执行环境是否在Kmesh支持的[OS列表](docs/kmesh_support-zh.md)中，对于其他OS环境需要参考[Kmesh编译构建](docs/kmesh_compile-zh.md)；也可以使用[兼容模式的kmesh镜像](build/docker/README.md#兼容模式镜像)在其他OS环境中进行尝试，关于kmesh各种镜像的说明请参考[详细文档](build/docker/README.md)。
 
 - Docker镜像：
@@ -69,9 +69,7 @@ Kmesh创新性的提出将流量治理下沉OS，在数据路径上无需经过
   - 针对所有OS版本：
 
     为了兼容不同的OS版本，Kmesh提供在线编译并运行的镜像。在Kmesh被部署之后，它会基于宿主机的内核能力自动选择运行的Kmesh特性，从而满足一个镜像在不同OS环境运行的要求。
-    
-    
-    
+
     考虑到kmesh使用的通用性，我们也发布了用于kmesh编译构建的镜像。用户可以基于此镜像方便的制作出可以在当前OS版本上运行的kmesh镜像。默认命名为ghcr.io/kmesh-net/kmesh:latest，用户可自行调整，参考[Kmesh编译构建](docs/kmesh_compile-zh.md#docker image编译)
 
     ```bash
@@ -131,7 +129,7 @@ Kmesh创新性的提出将流量治理下沉OS，在数据路径上无需经过
 
   - 安装waypoint
 
-    ```
+    ```bash
     [root@ ~]# istioctl x waypoint apply --service-account default
     [root@ ~]# kubectl get pods 
     NAME                                      READY   STATUS         RESTARTS        AGE
@@ -142,8 +140,8 @@ Kmesh创新性的提出将流量治理下沉OS，在数据路径上无需经过
 
   - 用kmesh自定义的镜像替换waypoint的原生镜像
 
-    ```
-    [root@ ~]# kubectl get gateway
+    ```bash
+    kubectl get gateway
     NAME      CLASS            ADDRESS         PROGRAMMED   AGE
     default   istio-waypoint   10.96.143.232   True         5m7s
     ```

README.md

@@ -1,6 +1,6 @@
 <img src="docs/pics/logo/KMESH-horizontal-colour.png" alt="kmesh-logo" style="zoom: 100%;" />
 
-[![LICENSE](https://img.shields.io/github/license/kmesh-net/kmesh)](/LICENSE) [![codecov](https://codecov.io/gh/kmesh-net/kmesh/graph/badge.svg?token=0EGQ84FGDU)](https://codecov.io/gh/kmesh-net/kmesh) 
+[![LICENSE](https://img.shields.io/github/license/kmesh-net/kmesh)](/LICENSE) [![codecov](https://codecov.io/gh/kmesh-net/kmesh/graph/badge.svg?token=0EGQ84FGDU)](https://codecov.io/gh/kmesh-net/kmesh)
 
 ## Introduction
 
@@ -46,30 +46,30 @@ Kmesh also provide a Dual-Engine Mode, which makes use of eBPF and waypoint to p
 
 ### Key features of Kmesh
 
-**Smooth Compatibility**
+#### Smooth Compatibility
 
 - Application-transparent Traffic Management
 
-**High Performance**
+#### High Performance
 
 - Forwarding delay **60%↓**
 - Workload startup performance **40%↑**
 
-**Low Resource Overhead**
+#### Low Resource Overhead
 
 - ServiceMesh data plane overhead **70%↓**
 
-**Zero Trust**
+#### Zero Trust
 
 - Provide zero trust security with default mutual TLS
 - Policy enforcement both in eBPF and waypoints
 
-**Safety Isolation**
+#### Safety Isolation
 
 - eBPF Virtual machine security
 - Cgroup level orchestration isolation
 
-**Open Ecology**
+#### Open Ecology
 
 - Supports XDS protocol standards
 - Support [Gateway API](https://gateway-api.sigs.k8s.io/)

SECURITY.md

@@ -1 +1 @@
-For further details please see [Security Policy](https://github.com/kmesh-net/community/blob/main/security-team/SECURITY.md) for our security process and how to report vulnerabilities.
+For further details please see [Security Policy](https://github.com/kmesh-net/community/blob/main/security-team/SECURITY.md) for our security process and how to report vulnerabilities.

bpf/kmesh/README.md

@@ -1,3 +1,3 @@
 # BPF-KMESH
-## Usage Tutorial
 
+## Usage Tutorial