Unify 'EventMesh Runtime'

Pil0tXia · Pil0tXia · commit ff35dc04fe55 · 2023-12-15T16:42:21.000+08:00
diff --git a/docs/design-document/03-connect/02-knative-connector.md b/docs/design-document/03-connect/02-knative-connector.md
@@ -40,7 +40,7 @@ application {
 
 ## Demo
 ### Publish an Event Message from Knative and Subscribe from EventMesh
-#### Step 1: Start an Eventmesh-Runtime Server
+#### Step 1: Start an EventMesh Runtime Server
 ```bash
 $ cd eventmesh-starter
 $ ../gradlew -PmainClass=org.apache.eventmesh.starter.StartUp run
@@ -68,7 +68,7 @@ The following message with `data` field as `Hello CloudEvents!` will be printed
 ```
 
 ### Publish an Event Message from EventMesh and Subscribe from Knative
-#### Step 1: Start an Eventmesh-Runtime Server
+#### Step 1: Start an EventMesh Runtime Server
 ```bash
 $ cd eventmesh-starter
 $ ../gradlew -PmainClass=org.apache.eventmesh.starter.StartUp run
diff --git a/docs/instruction/01-store.md b/docs/instruction/01-store.md
@@ -7,7 +7,7 @@
 64-bit JDK 1.8+;
 Gradle 7.0+, we recommend 7.0.*
 4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
+If you choose standalone mode, you could skip this file and go to the next step: Start EventMesh Runtime; if not, you could choose RocketMQ as the store layer.
 ```
 
 ## 2 Download
@@ -39,7 +39,7 @@ nohup sh bin/mqbroker -n localhost:9876 &
 tail -f ~/logs/rocketmqlogs/broker.log
 ```
 
-The deployment of eventmesh-store has finished, please go to the next step: [Start Eventmesh-Runtime](03-runtime.md)
+The deployment of eventmesh-store has finished, please go to the next step: [Start EventMesh Runtime](03-runtime.md)
 
 ## Reference
 
diff --git a/docs/instruction/02-store-with-docker.md b/docs/instruction/02-store-with-docker.md
@@ -1,6 +1,6 @@
 # EventMesh Store with Docker
 
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
+If you choose standalone mode, you could skip this file and go to the next step: Start EventMesh Runtime; if not, you could choose RocketMQ as the store layer.
 
 ## 1. Dependencies
 
@@ -70,4 +70,4 @@ sudo docker run -d -p 10911:10911 -p 10909:10909 \
 
 Please note that the **rocketmq-broker ip** is **pod ip**. If you want to modify this ip, you can set it your custom value in **broker.conf**。
 
-By now, the deployment of eventmesh-store has finished, please go to the next step: [Start Eventmesh-Runtime Using Docker](04-runtime-with-docker.md)
+By now, the deployment of eventmesh-store has finished, please go to the next step: [Start EventMesh Runtime Using Docker](04-runtime-with-docker.md)
diff --git a/docs/instruction/04-runtime-with-docker.md b/docs/instruction/04-runtime-with-docker.md
@@ -9,7 +9,7 @@ The documentation introduces the steps to install the latest release of EventMes
 64-bit JDK 1.8+;
 Gradle 7.0+, we recommend 7.0.*
 4g+ available disk to deploy eventmesh-store
-If you choose standalone mode, you could skip this file and go to the next step: Start Eventmesh-Runtime; if not, you could choose RocketMQ as the store layer.
+If you choose standalone mode, you could skip this file and go to the next step: Start EventMesh Runtime; if not, you could choose RocketMQ as the store layer.
 ```
 
 ## 2. Pull EventMesh Image
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/01-runtime-protocol.md b/i18n/zh/docusaurus-plugin-content-docs/current/design-document/01-event-handling-and-integration/01-runtime-protocol.md
@@ -55,7 +55,7 @@ public class Header {
 | REQUEST_TO_SERVER, REQUEST_TO_CLIENT, RESPONSE_TO_SERVER, RESPONSE_TO_CLIENT, ASYNC_MESSAGE_TO_SERVER, ASYNC_MESSAGE_TO_CLIENT, BROADCAST_MESSAGE_TO_SERVER, BROADCAST_MESSAGE_TO_CLIENT, ASYNC_MESSAGE_TO_CLIENT_ACK, BROADCAST_MESSAGE_TO_CLIENT_ACK, RESPONSE_TO_CLIENT_ACK, REQUEST_TO_CLIENT_ACK | OpenMessage  |
 | REDIRECT_TO_CLIENT                                           | RedirectInfo |
 
-#### 3. Client 与 Eventmesh-Runtime(Server)交互场景详解
+#### 3. Client 与 EventMesh Runtime(Server)交互场景详解
 
 ```java
 public enum Command {
