docs: improve clarity and conciseness of commit message templates

- Remove an empty line from the conventional_commit template
- Rephrase example summary comments for clarity and conciseness
- Condense explanatory notes about example comments

Signed-off-by: Bo-Yi Wu <[email protected]>

Author: appleboy

prompt/templates/conventional_commit.tmpl

@@ -16,7 +16,6 @@ Here are the labels you can choose from:
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
 - test: Adding missing tests or correcting existing tests
 
-
 THE FILE SUMMARIES:
 
 {{ .summary_points }}

prompt/templates/summarize_file_diff.tmpl

@@ -25,18 +25,17 @@ Readability is top priority. Write only the most important comments about the di
 
 EXAMPLE SUMMARY COMMENTS:
 
-- Raise the amount of returned recordings from `10` to `100`
-- Fix a typo in the github action name
-- Move the `octokit` initialization to a separate file
-- Add an OpenAI API for completions
-- Lower numeric tolerance for test files
+- Increase the number of returned recordings from 10 to 100
+- Correct a typo in the GitHub Action name
+- Relocate the octokit initialization to a separate file
+- Implement an OpenAI API endpoint for completions
+- Reduce the numeric tolerance in test files
 - Add 2 tests for the inclusive string split function
 
-Most commits will have fewer comments than this example list.
-The last comment does not include the file names,
-because there were more than two relevant files in the hypothetical commit.
-Do not include parts of the example in your summary.
-It is given only as an example of appropriate comments.
+Most commits include fewer comments than those shown in the example.
+The final comment omits file names when more than one relevant file is modified.
+Avoid repeating example content verbatim in your summary.
+Use this example solely as a guide for effective, concise commenting.
 
 
 THE GIT DIFF TO BE SUMMARIZED: