docs: fix spelling errors

docs/commit_convention.CN.md

@@ -13,7 +13,7 @@
 <footer>
 ```
 
-- 标题行:  **必填** , 描述主要修改类型和内容，scope增强描述提交作用范围，例如我们cherry的core层、Edior、Previewer等
+- 标题行:  **必填** , 描述主要修改类型和内容，scope增强描述提交作用范围，例如我们cherry的core层、Editor、Previewer等
 - 主题内容: 描述为什么修改, 做了什么样的修改, 以及开发的思路； **这里直接引用tapd源码关键字，若没有则不填**
 - 页脚注释: 放 Breaking Changes 或 Closed Issues
 

docs/commit_convention.md

@@ -13,7 +13,7 @@ As a formal open-source project team, our submission specifications are consiste
 <footer>
 ```
 
-- Title line:  **must be filled** , describe your main modification type and content, scope enhance the description submission scope, such as the Cherry core layer, Edior, Previewer, etc.
+- Title line:  **must be filled** , describe your main modification type and content, scope enhance the description submission scope, such as the Cherry core layer, Editor, Previewer, etc.
 - Subject content: describe why you changed, what you had changed and development ideas  **here directly cites to the tapd source code keyword. Don't fill in if you don't have it
 - Footer notes:  for Breaking Changes or Closed Issues
 

docs/configuration.md

@@ -48,7 +48,7 @@ editor: {
 
 ### Toolbar Config
 
-Cherry Markdown Editor contains three configurable toolbars，Including toolbar (fixed toolbar above)、bubble( appears toolbar when select the text) and float (appears at the beginning of a new liner), in which you can customize and add the required functions.
+Cherry Markdown Editor contains three configurable toolbars,Including toolbar (fixed toolbar above)、bubble( appears toolbar when select the text) and float (appears at the beginning of a new liner), in which you can customize and add the required functions.
 
 ```js
 toolbars:{                                                                                                     
@@ -183,8 +183,8 @@ engine: {
         // 'SyntaxClass': {             <[String]> hook name
         //    syntax: SyntaxClass,      <[SyntaxBase]> hook Constructor
         //    force: true,              <[Boolean]> whether force overwrite the same name hook
-        //    before: 'HOOK_NAME',      <[String]> hookName，execute before this hook
-        //    after: 'HOOK_NAME'        <[String]> hookName，execute before this hook
+        //    before: 'HOOK_NAME',      <[String]> hookName,execute before this hook
+        //    after: 'HOOK_NAME'        <[String]> hookName,execute before this hook
         // }
     }
 }

docs/extensions.md

@@ -28,8 +28,8 @@ engine: {
   - SyntaxClass   `<[String]> hook name`
     - syntax    `<[SyntaxBase]> hook constructor`
     - force     `<[Boolean]> whether overwrite hook with the same name`
-    - before    `<[String]> hookName，execute before this hook`
-    - after     `<[String]> hookName，execute after this hook`
+    - before    `<[String]> hookName,execute before this hook`
+    - after     `<[String]> hookName,execute after this hook`
 
 ## Custom Syntax