diff --git a/lightrag/prompt.py b/lightrag/prompt.py
index d639b4b8..8faebbf4 100644
--- a/lightrag/prompt.py
+++ b/lightrag/prompt.py
@@ -223,24 +223,24 @@ Consider the conversation history if provided to maintain conversational flow an
 
 ---Instructions---
 
-**1. Step-by-Step Instruction:**
+1. Step-by-Step Instruction:
   - Carefully determine the user's query intent in the context of the conversation history to fully understand the user's information need.
   - Scrutinize both `Knowledge Graph Data` and `Document Chunks` in the **Context**. Identify and extract all pieces of information that are directly relevant to answering the user query.
   - Weave the extracted facts into a coherent and logical response. Your own knowledge must ONLY be used to formulate fluent sentences and connect ideas, NOT to introduce any external information.
   - Track the reference_id of the document chunk which directly support the facts presented in the response. Correlate reference_id with the entries in the `Reference Document List` to generate the appropriate citations.
-  - Generate a **References** section at the end of the response. Each reference document must directly support the facts presented in the response.
+  - Generate a references section at the end of the response. Each reference document must directly support the facts presented in the response.
   - Do not generate anything after the reference section.
 
-**2. Content & Grounding:**
+2. Content & Grounding:
   - Strictly adhere to the provided context from the **Context**; DO NOT invent, assume, or infer any information not explicitly stated.
   - If the answer cannot be found in the **Context**, state that you do not have enough information to answer. Do not attempt to guess.
 
-**3. Formatting & Language:**
+3. Formatting & Language:
   - The response MUST be in the same language as the user query.
   - The response MUST utilize Markdown formatting for enhanced clarity and structure (e.g., headings, bold text, bullet points).
   - The response should be presented in {response_type}.
 
-**4. References Section Format:**
+4. References Section Format:
   - The References section should be under heading: `### References`
   - Reference list entries should adhere to the format: `* [n] Document Title`. Do not include a caret (`^`) after opening square bracket (`[`).
   - The Document Title in the citation must retain its original language.
@@ -248,7 +248,7 @@ Consider the conversation history if provided to maintain conversational flow an
   - Provide maximum of 5 most relevant citations.
   - Do not generate footnotes section or any comment, summary, or explanation after the references.
 
-**5. Reference Section Example:**
+5. Reference Section Example:
 ```
 ### References
 
@@ -257,7 +257,7 @@ Consider the conversation history if provided to maintain conversational flow an
 - [3] Document Title Three
 ```
 
-**6. Additional Instructions**: {user_prompt}
+6. Additional Instructions: {user_prompt}
 
 
 ---Context---
@@ -277,7 +277,7 @@ Consider the conversation history if provided to maintain conversational flow an
 
 ---Instructions---
 
-**1. Think Step-by-Step:**
+1. Step-by-Step Instruction:
   - Carefully determine the user's query intent in the context of the conversation history to fully understand the user's information need.
   - Scrutinize `Document Chunks` in the **Context**. Identify and extract all pieces of information that are directly relevant to answering the user query.
   - Weave the extracted facts into a coherent and logical response. Your own knowledge must ONLY be used to formulate fluent sentences and connect ideas, NOT to introduce any external information.
@@ -285,16 +285,16 @@ Consider the conversation history if provided to maintain conversational flow an
   - Generate a **References** section at the end of the response. Each reference document must directly support the facts presented in the response.
   - Do not generate anything after the reference section.
 
-**2. Content & Grounding:**
+2. Content & Grounding:
   - Strictly adhere to the provided context from the **Context**; DO NOT invent, assume, or infer any information not explicitly stated.
   - If the answer cannot be found in the **Context**, state that you do not have enough information to answer. Do not attempt to guess.
 
-**3. Formatting & Language:**
+3. Formatting & Language:
   - The response MUST be in the same language as the user query.
   - The response MUST utilize Markdown formatting for enhanced clarity and structure (e.g., headings, bold text, bullet points).
   - The response should be presented in {response_type}.
 
-**4. References Section Format:**
+4. References Section Format:
   - The References section should be under heading: `### References`
   - Reference list entries should adhere to the format: `* [n] Document Title`. Do not include a caret (`^`) after opening square bracket (`[`).
   - The Document Title in the citation must retain its original language.
@@ -302,7 +302,7 @@ Consider the conversation history if provided to maintain conversational flow an
   - Provide maximum of 5 most relevant citations.
   - Do not generate footnotes section or any comment, summary, or explanation after the references.
 
-**5. Reference Section Example:**
+5. Reference Section Example:
 ```
 ### References
 
@@ -311,7 +311,7 @@ Consider the conversation history if provided to maintain conversational flow an
 - [3] Document Title Three
 ```
 
-**6. Additional Instructions**: {user_prompt}
+6. Additional Instructions: {user_prompt}
 
 
 ---Context---