diff --git a/.github/prompts/win-4-execution.prompt.md b/.github/prompts/win-4-execution.prompt.md
index 9ff81de7..a43078ba 100644
--- a/.github/prompts/win-4-execution.prompt.md
+++ b/.github/prompts/win-4-execution.prompt.md
@@ -17,7 +17,7 @@
 
 ## Step 2. Make Sure the Code Compiles but DO NOT Run Unit Test
 
-- Check out `Compile the Solution` for details about compiling the solution but DO NOT run unit test. If there is any compilation error, address all of them:
+- Check out `Compile the Solution` for details about compiling the solution but DO NOT run unit test. If there is any compilation warning or error, address all of them:
   - If there is any compile warning, only fix warnings that caused by your code change. Do no fix any other warnings.
   - If there is any compile error, you need to carefully identify, is the issue in the callee side or the caller side. Check out similar code before making a decision.
   - For every attempt of fixing the source code:
@@ -25,7 +25,7 @@
     - Explain what you need to do.
     - Explain why you think it would solve the build break.
     - Log these in `Copilot_Execution.md`, with section `## Fixing attempt No.<attempt_number>` in `# FIXING ATTEMPTS`.
-  - Go back to `Step 5. Make Sure the Code Compiles`
+  - Redo `Step 2. Make Sure the Code Compiles but DO NOT Run Unit Test`.
 - When the code compiles:
   - DO NOT run any tests, the code will be verified in future tasks.