!899 【OpenHarmony开源贡献者计划2022】fix: json error and brand name error in README docs

* fix: json error and brand name error in ReadME docs

sig/README-EN.md

@@ -3,7 +3,7 @@ English | [简体中文](./README.md)
 
 ## Background
 Under the guidance of the Project Management Committee (PMC), a special interest group (SIG) designs the architecture, develops open capabilities, and performs maintenance for innovative projects in a specific domain.
-This repository stores information about all the SIGs in the OpenHamony community.
+This repository stores information about all the SIGs in the OpenHarmony community.
 
 ## Applying for Creating an SIG
 1. Seek two or three developers in the community who have the same interest or objectives as you and elect a leader for this SIG. Create an SIG proposal based on the [SIG creation template](sig-template/sig_template.md), The proposal includes the following elements:
@@ -20,7 +20,7 @@ This repository stores information about all the SIGs in the OpenHamony communit
 
 ## Operating and Maintaining an SIG
 
-1. The SIG leader forks the **OpenHamony/community** release, creates a folder and names it with the SIG name in the **sig** directory, creates an SIG profile in the created folder based on the [SIG template](sig-template/), and submits pull requests (PRs) for incorporating modifications of the SIG profile into the master code of OpenHarmony.
+1. The SIG leader forks the **OpenHarmony/community** release, creates a folder and names it with the SIG name in the **sig** directory, creates an SIG profile in the created folder based on the [SIG template](sig-template/), and submits pull requests (PRs) for incorporating modifications of the SIG profile into the master code of OpenHarmony.
 
 2. SIG incubation projects are stored in the [OpenHarmony-SIG](https://gitee.com/openharmony-sig) organization. The code of incubation projects that meet graduation requirements can be incorporated into the master code of OpenHarmony.
 
@@ -34,8 +34,8 @@ This repository stores information about all the SIGs in the OpenHamony communit
 3. After the PMC approves the graduation application, you can incorporate the code of the incubation project into the master code of OpenHarmony.
 
 ### How SIG Data Is Stored and Managed
-SIG data is stored in the **sig** directory of the **OpenHamony/community** repository. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file is a template that contains the objectives and work scope of this SIG, repositories managed by the SIG and their descriptions, and SIG meetings and members. A backup of the maintainer/committer information of the SIG is stored in the **OWNER** file and can be automatically obtained by a tool. The names and directory structures of the repositories managed by each SIG are stored in the **sigs.json** file.
-1. The **sigs.json** file in the **sig** directory of the **OpenHarmony/co    mmunity** repository is used to manage all the SIGs visible to the PMC.
+SIG data is stored in the **sig** directory of the **OpenHarmony/community** repository. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file is a template that contains the objectives and work scope of this SIG, repositories managed by the SIG and their descriptions, and SIG meetings and members. A backup of the maintainer/committer information of the SIG is stored in the **OWNER** file and can be automatically obtained by a tool. The names and directory structures of the repositories managed by each SIG are stored in the **sigs.json** file.
+1. The **sigs.json** file in the **sig** directory of the **OpenHarmony/community** repository is used to manage all the SIGs visible to the PMC.
 2. The PMC modifies and maintains SIGs. Maintainers submit PRs for modifying SIGs, and the PMC reviews the PRs and incorporates the modifications into the master code of OpenHarmony.
 3. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file in the **sig** directory stores SIG data. In this file, the basic SIG information is empty and needs to be specified during SIG creation.
 4. The **OWNER** file in the **sig** directory stores information about the maintainer of the SIG.
@@ -57,8 +57,8 @@ SIG data is stored in the **sig** directory of the **OpenHamony/community** repo
          "project-path":"python/"
       },
       {
-         "sig-name ":"sig-updates",
-         "projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"]
+         "sig-name":"sig-updates",
+         "projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"],
          "project-path":["base/startup/appspawn_lite", "base/startup/bootstrap_lite"]
       },
    ]

sig/README.md

@@ -4,7 +4,7 @@
 ## 背景
  1. SIG（Special Interest Group）是指特别兴趣小组，SIG在PMC项目管理委员会指导下，负责OpenHarmony社区特定子领域及创新项目的架构设计、开源开发及项目维护等工作。
  2. 为了便于OpenHarmony开源社区工作开展和交流，默认将其划分为23个初始的SIG小组：[Maps_Sigs_Subsystem](./sigs_subsystem_list.md)。
- 3. 本目录用于存放OpenHamony社区所有 “特别兴趣小组”（Special Interest Group，以下简称 SIG）的运作信息。
+ 3. 本目录用于存放OpenHarmony社区所有 “特别兴趣小组”（Special Interest Group，以下简称 SIG）的运作信息。
 
 ## SIG职责&运作方式
  1. 领域的技术演进方向由SIG组承担，负责领域技术竞争力分析和关键技术识别及决策。
@@ -28,7 +28,7 @@
 1. 开发者可通过SIG列表查看感兴趣的SIG，通过订阅邮件列表、参与SIG会议等形式，参与对应SIG项目的技术讨论、社区维护及开源开发。
 
 ## 运营维护SIG
-1. SIG Leader Fork OpenHamony/community分支，在SIG文件夹下，以新SIG名称新建文件夹，并参考[SIG模板](sig-template/)，创建对应的SIG配置文件，提交PR合入申请。
+1. SIG Leader Fork OpenHarmony/community分支，在SIG文件夹下，以新SIG名称新建文件夹，并参考[SIG模板](sig-template/)，创建对应的SIG配置文件，提交PR合入申请。
 2. SIG孵化子项目，统一存放在[OpenHarmony SIG组织](https://gitee.com/openharmony-sig)，待孵化成熟后，可合入OpenHarmony组织代码主库。
 3. SIG Leader及Committer负责对应SIG的运营及维护，会议纪要和资料统一参考sig-template目录下的[meetings](https://gitee.com/openharmony-sig/sig-content)和[docs](https://gitee.com/openharmony-sig/sig-content)模版进行归档。
 4. SIG Leader定期在PMC项目管理委员会汇报SIG孵化项目及SIG运营进展，PMC基于SIG运作情况给出指导建议。
@@ -40,7 +40,7 @@
  4. 孵化项目毕业评审请按照[要求自检](./sig-QA/guidance_for_incubation_project_graduation_cn.md)。
 
 ## SIG数据存放和管理方式
-SIG信息记录统一归档在OpenHamony/community仓库的sig目录内：
+SIG信息记录统一归档在OpenHarmony/community仓库的sig目录内：
 1. sig_xxx.md/sig_xxx_cn.md：包括SIG组工作目标和范围、SIG管理的repository及描述、SIG组织会议、SIG成员。
 
 2. sigs.json：为了便于工具自动提取，其中SIG的maintainer/committer信息单独备份一份至OWNER文件内，每个SIG所维护的仓库名称列表/目录结构位于sigs.json文件中。
@@ -85,8 +85,8 @@ SIG信息记录统一归档在OpenHamony/community仓库的sig目录内：
          "project-path":"python/"
       },
       {
-         "sig-name ":"sig-updates",
-         "projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"]
+         "sig-name":"sig-updates",
+         "projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"],
          "project-path":["base/startup/appspawn_lite", "base/startup/bootstrap_lite"]
       },
    ]