格式check改动

mosn · Jun 28, 2024 · 1537b68 · 1537b68
1 parent 7eb7f87
commit 1537b68
Show file tree

Hide file tree

Showing 18 changed files with 25 additions and 13 deletions.
diff --git a/docs/blog/code/layotto-rpc/index.md b/docs/blog/code/layotto-rpc/index.md
@@ -936,7 +936,9 @@ func (p *parser) recvMsg(maxReceiveMessageSize int) (pf payloadFormat, msg []byt
 
 最终收到返回数据：
 ```json
+
 {"jsonrpc":"2.0","id":9527,"result":{"id":"113","name":"Moorse","age":30,"time":703394193,"sex":"MAN"}}
+
 ```
 
 ## 总结

diff --git a/docs/docs/README.md b/docs/docs/README.md
@@ -178,6 +178,6 @@ Layotto enriches the <a href="https://landscape.cncf.io/serverless">CNCF CLOUD N
 
 ## FAQ
 
-### 跟 dapr 有什么差异？
+## 跟 dapr 有什么差异？
 
 dapr 是一款优秀的 Runtime 产品，但它本身缺失了 Service Mesh 的能力，而这部分能力对于实际在生产环境落地是至关重要的，因此我们希望把 Runtime 跟 Service Mesh 两种能力结合在一起，满足更复杂的生产落地需求。
diff --git a/docs/docs/design/faas/faas-poc-design.md b/docs/docs/design/faas/faas-poc-design.md
@@ -1,5 +1,7 @@
 # FaaS设计文档
 
+## FaaS设计
+
 ### 一、架构设计
 
 ![img.png](../(/img/faas/faas-design.jpg)

diff --git a/docs/docs/design/rpc/rpc_design_document.md b/docs/docs/design/rpc/rpc_design_document.md
@@ -1,5 +1,5 @@
 # RPC 设计文档
-
+## RPC 设计
 ### API 设计
 [layotto rpc API](https://github.com/mosn/layotto/blob/f70cdc619693ad762cf809daf0579403c341def1/spec/proto/runtime/v1/runtime.proto#L19https://github.com/mosn/layotto/blob/f70cdc619693ad762cf809daf0579403c341def1/spec/proto/runtime/v1/runtime.proto#L19) 与Dapr保持一致.
 

diff --git a/docs/docs/development/component_ref/component_ref.md b/docs/docs/development/component_ref/component_ref.md
@@ -1,6 +1,6 @@
 # layotto组件引用
 
-### 背景
+## 背景
 
 组件初始化的时候，需要引用其他组件的能力，比如sequencer组件初始化的时候需要从config组件读取相关的配置，以此实现组件之间的引用。
 

diff --git a/docs/docs/start/faas/start.md b/docs/docs/start/faas/start.md
@@ -1,6 +1,6 @@
 # FaaS 快速开始
 
-### 一、功能介绍
+## 一、功能介绍
 
 Layotto支持加载并运行以 wasm 为载体的 Function，并支持Function之间互相调用以及访问基础设施，如Redis。
 

diff --git a/docs/docs/start/wasm/start.md b/docs/docs/start/wasm/start.md
@@ -1,4 +1,7 @@
 # 将业务逻辑通过WASM下沉进sidecar
+
+## sidecar
+
 ### 功能介绍
 service mesh 和 multi-runtime 的 sidecar 是全公司通用的基础设施，但实践中,业务系统也会有自己的sdk，也会有推动用户升级难、版本碎片的问题.
 

diff --git a/docs/i18n/en-US/docusaurus-plugin-content-blog/code/start_process/start_process.md b/docs/i18n/en-US/docusaurus-plugin-content-blog/code/start_process/start_process.md
@@ -94,7 +94,7 @@ func NewRuntimeGrpcServer(data json.RawMessage, opts ...grpc.ServerOption) (mgrp
 
 ### runtime analysis
 
-Look at the structure of runtime, the composition of the `runtime' at the aggregate level of the `：'
+Look at the structure of runtime, the composition of the `runtime' at the aggregate level of the`：'
 
 ```
 type MosnRuntime struct {

diff --git a/...n-US/docusaurus-plugin-content-blog/current/code/start_process/start_process.md b/...n-US/docusaurus-plugin-content-blog/current/code/start_process/start_process.md
@@ -94,7 +94,7 @@ func NewRuntimeGrpcServer(data json.RawMessage, opts ...grpc.ServerOption) (mgrp
 
 ### runtime analysis
 
-Look at the structure of runtime, the composition of the `runtime' at the aggregate level of the `：'
+Look at the structure of runtime, the composition of the `runtime' at the aggregate level of the`：'
 
 ```
 type MosnRuntime struct {

diff --git a/docs/i18n/en-US/docusaurus-plugin-content-docs/current/design/api_plugin/design.md b/docs/i18n/en-US/docusaurus-plugin-content-docs/current/design/api_plugin/design.md
@@ -283,7 +283,7 @@ Look at this example, you might ask：these callbacks, constructions and calls?
 
 The hook above is used to customize the start logic for the user extension.Layotto reverses the above life-cycle hooks and constructions during startup.Call order roughly：
 
-`Layotto initialize all components` ---> Call `NewGrpcAPI` constructor ---> `GrpcAPI.Init` ---> ``Layotto create grpc server` ---> ``GrpcAPI.Register\`\`
+`Layotto initialize all components` ---> Call `NewGrpcAPI` constructor ---> `GrpcAPI.Init` ---> ``Layotto create grpc server` --->``GrpcAPI.Register\`\`
 
 Graph below：
 

diff --git a/...18n/en-US/docusaurus-plugin-content-docs/current/design/faas/faas-poc-design.md b/...18n/en-US/docusaurus-plugin-content-docs/current/design/faas/faas-poc-design.md
@@ -1,5 +1,6 @@
 # FaaS Design Document
 
+# FaaS Design
 ### Structure design
 
 ![img.png](../(/img/faas/faas-design.jpg)

diff --git a/.../i18n/en-US/docusaurus-plugin-content-docs/current/design/rpc/rpc-design-doc.md b/.../i18n/en-US/docusaurus-plugin-content-docs/current/design/rpc/rpc-design-doc.md
@@ -1,5 +1,5 @@
 # RPC DESIGN
-
+## RPC DESIGN
 ### API
 runtime rpc API is same with Dapr.
 

diff --git a/.../en-US/docusaurus-plugin-content-docs/current/design/rpc/rpc_design_document.md b/.../en-US/docusaurus-plugin-content-docs/current/design/rpc/rpc_design_document.md
@@ -1,5 +1,7 @@
 # RPC Design Document
 
+## RPC Design
+
 ### API Design
 
 [layotto rpc API](https://github.com/mosn/layotto/blob/f70cdc6196963ad762cf809daf0579403c341def1/spec/proto/runtime/v1/runtime.proto#L19 https://github.com/mosn/layotto/blob/f70cdc619693ad762cf809daf0579403c341def1/spec/proto/runtime/v1/runtime.proto#L19) is consistent with Dapr.

diff --git a/...cusaurus-plugin-content-docs/current/development/component_ref/component_ref.md b/...cusaurus-plugin-content-docs/current/development/component_ref/component_ref.md
@@ -1,5 +1,5 @@
 # layotto component reference
-
+## layotto component
 ### Background
 
 When a component starts, it may need to use another component's skill. For example, when the `sequencer` component `A` starts, it needs to read its settings from the `config` component `B`.

diff --git a/docs/i18n/en-US/docusaurus-plugin-content-docs/current/start/faas/start.md b/docs/i18n/en-US/docusaurus-plugin-content-docs/current/start/faas/start.md
@@ -1,5 +1,5 @@
 # FaaS QuickStart
-
+## FaaS QuickStart
 ### 1. Features
 
 Layotto supports loading and running functions in the form of wasm, and supports calling each other between functions and accessing infrastructure, such as Redis.

diff --git a/...8n/en-US/docusaurus-plugin-content-docs/current/start/network_filter/tcpcopy.md b/...8n/en-US/docusaurus-plugin-content-docs/current/start/network_filter/tcpcopy.md
@@ -22,7 +22,7 @@ The meaning of this configuration is to load the tcpcopy plug-in at startup to d
 
 After enabling this configuration, when Layotto receives a request and the conditions for traffic dump are met, it will write the binary request data to the local file system.
 
-The "dumped" binary traffic data will be stored in the ` ${user's home directory}/logs/mosn` directory, or under the /home/admin/logs/mosn directory:
+The "dumped" binary traffic data will be stored in the `${user's home directory}/logs/mosn` directory, or under the /home/admin/logs/mosn directory:
 
 ![img.png](/img/tcp_dump.png)
 

diff --git a/...n-US/docusaurus-plugin-content-docs/current/start/stream_filter/flow_control.md b/...n-US/docusaurus-plugin-content-docs/current/start/stream_filter/flow_control.md
@@ -1,6 +1,8 @@
 [查看中文版本](docs/start/stream_filter/flow_control.md)
 
-## Method Level Flow Control
+# Method Level Flow Control
+
+## Flow Control
 
 ### Introduction
 

diff --git a/docs/i18n/en-US/docusaurus-plugin-content-docs/current/start/wasm/start.md b/docs/i18n/en-US/docusaurus-plugin-content-docs/current/start/wasm/start.md
@@ -1,5 +1,5 @@
 # Run business logic in Layotto using WASM
-
+## Run business logic in Layotto using WASM
 ### What is WASM on Layotto?
 The sidecar of service mesh and multi-runtime is a common infrastructure for the whole company, but in practice, the business system will also have its own SDK, and it will also have the difficulty of pushing users to upgrade the SDK and the problem of version fragmentation.
-Original file line number
+Diff line change
@@ Expand Up @@
     最终收到返回数据：
     ```json
     {"jsonrpc":"2.0","id":9527,"result":{"id":"113","name":"Moorse","age":30,"time":703394193,"sex":"MAN"}}
     ```
     ## 总结
@@ Expand Down @@