diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 14df34a4..352b7f38 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -13,11 +13,12 @@ https://github.com/Rtoax/ulpatch/blob/master/CONTRIBUTING.md
 **Describe the bug (Required)**
 A clear and concise description of what the bug is.
 
-- **Software Environment (Required)**:
+**Software Environment (Required)**:
 -- OS platform and distribution (e.g., Linux Ubuntu 16.04):
 -- GLibc Version (e.g., ldconfig (GNU libc) 2.38) :
 -- GCC/Compiler version (e.g., gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6)) :
--- You can directly use the --info parameter to view system and ULPatch related information:
+-- Or, you could use the `--info` parameter directly to display above and ULPatch information:
+   such as **ulpatch --info**
 
 **To Reproduce (Required)**
 Steps to reproduce the behavior:
diff --git a/.gitlab/issue_templates/bug_report.md b/.gitlab/issue_templates/bug_report.md
index 14df34a4..352b7f38 100644
--- a/.gitlab/issue_templates/bug_report.md
+++ b/.gitlab/issue_templates/bug_report.md
@@ -13,11 +13,12 @@ https://github.com/Rtoax/ulpatch/blob/master/CONTRIBUTING.md
 **Describe the bug (Required)**
 A clear and concise description of what the bug is.
 
-- **Software Environment (Required)**:
+**Software Environment (Required)**:
 -- OS platform and distribution (e.g., Linux Ubuntu 16.04):
 -- GLibc Version (e.g., ldconfig (GNU libc) 2.38) :
 -- GCC/Compiler version (e.g., gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6)) :
--- You can directly use the --info parameter to view system and ULPatch related information:
+-- Or, you could use the `--info` parameter directly to display above and ULPatch information:
+   such as **ulpatch --info**
 
 **To Reproduce (Required)**
 Steps to reproduce the behavior:
diff --git a/docs/developers.md b/docs/developers.md
index 3bba581e..dc43b3c9 100644
--- a/docs/developers.md
+++ b/docs/developers.md
@@ -19,7 +19,7 @@ In my opinion, if you want to develop and participate in the development of this
 You can view unfinished development tasks in [TODO-List](./TODO.md), and you need to obey the [Coding Style](./code-style.md) and [Contributing](./CONTRIBUTING.md) rules.
 
 
-### C Compile Macros
+### CMake Compile Macros
 
 #### CONFIG_CAPSTONE