From 02329d48caf11450525ea0e4776fbe4592cfb23f Mon Sep 17 00:00:00 2001
From: wucaiheng <11866284+wucaiheng@user.noreply.gitee.com>
Date: Tue, 21 Mar 2023 03:09:05 +0000
Subject: [PATCH] update en/SIG-Management-Guide/SIG_Regulations_Template.md.

Signed-off-by: wucaiheng <11866284+wucaiheng@user.noreply.gitee.com>
---
 en/SIG-Management-Guide/SIG_Regulations_Template.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/en/SIG-Management-Guide/SIG_Regulations_Template.md b/en/SIG-Management-Guide/SIG_Regulations_Template.md
index 7d9fa2b9..19707e71 100644
--- a/en/SIG-Management-Guide/SIG_Regulations_Template.md
+++ b/en/SIG-Management-Guide/SIG_Regulations_Template.md
@@ -1,9 +1,9 @@
-## SIG Name
-> SIG naming specification.  
-> 1. SIG name with full spelling, only one word is capitalized; each word with multiple words is capitalized and no hyphen in between, for example: Release, BootAndInstall, etc..  
-> 2. special nouns or SIG names that must be abbreviated are all capitalized, for example: RISC-V, QA, etc..  
+## SIG Group Name
+> SIG naming convention.  
+> 1. full spelling of SIG name, only one word is capitalized; multiple words are capitalized with no hyphen in between, e.g., Release, BootAndInstall, etc...
+> 2. special nouns or SIG names that must be abbreviated are all capitalized, e.g., RISC-V, QA, etc...  
 > 3. SIG naming shall not infringe on the legitimate rights and interests of any third party (including but not limited to unauthorized use of third party trademarks, trade names, logos, etc.).
-> 4. The community has the final right to review the naming of SIG.
+> 4. the community has the final right to review the naming of SIG.
 
 SIG Group Introduction