fix typos (#2267)

* fix typos

no functional change

* fix typos

* fix typos

* fix integration test

---------

Co-authored-by: Engel Nyst <enyst@users.noreply.github.com>
Co-authored-by: Leo <ifuryst@gmail.com>
Co-authored-by: yufansong <yufan@risingwave-labs.com>

tests/integration/mock/DelegatorAgent/test_edits/prompt_001.log

@@ -34,7 +34,7 @@ Do NOT finish until you have a complete understanding of which parts of the
 codebase are relevant to the project, including particular files, functions, and classes.
 When you're done, put your summary in `outputs.summary` in the `finish` action.
 Remember, your task is to explore and study the current repository, not actually
-implement the solution. If the codebase is empty, you shoud call the `finish` action.
+implement the solution. If the codebase is empty, you should call the `finish` action.
 
 ## History
 Here is a recent history of actions you've taken in service of this plan,

tests/integration/mock/DelegatorAgent/test_edits/prompt_002.log

@@ -34,7 +34,7 @@ Do NOT finish until you have a complete understanding of which parts of the
 codebase are relevant to the project, including particular files, functions, and classes.
 When you're done, put your summary in `outputs.summary` in the `finish` action.
 Remember, your task is to explore and study the current repository, not actually
-implement the solution. If the codebase is empty, you shoud call the `finish` action.
+implement the solution. If the codebase is empty, you should call the `finish` action.
 
 ## History
 Here is a recent history of actions you've taken in service of this plan,

tests/integration/mock/DelegatorAgent/test_edits/prompt_003.log

@@ -34,7 +34,7 @@ Do NOT finish until you have a complete understanding of which parts of the
 codebase are relevant to the project, including particular files, functions, and classes.
 When you're done, put your summary in `outputs.summary` in the `finish` action.
 Remember, your task is to explore and study the current repository, not actually
-implement the solution. If the codebase is empty, you shoud call the `finish` action.
+implement the solution. If the codebase is empty, you should call the `finish` action.
 
 ## History
 Here is a recent history of actions you've taken in service of this plan,

tests/integration/mock/DelegatorAgent/test_write_simple_script/prompt_001.log

@@ -34,7 +34,7 @@ Do NOT finish until you have a complete understanding of which parts of the
 codebase are relevant to the project, including particular files, functions, and classes.
 When you're done, put your summary in `outputs.summary` in the `finish` action.
 Remember, your task is to explore and study the current repository, not actually
-implement the solution. If the codebase is empty, you shoud call the `finish` action.
+implement the solution. If the codebase is empty, you should call the `finish` action.
 
 ## History
 Here is a recent history of actions you've taken in service of this plan,

tests/integration/mock/DelegatorAgent/test_write_simple_script/prompt_002.log

@@ -34,7 +34,7 @@ Do NOT finish until you have a complete understanding of which parts of the
 codebase are relevant to the project, including particular files, functions, and classes.
 When you're done, put your summary in `outputs.summary` in the `finish` action.
 Remember, your task is to explore and study the current repository, not actually
-implement the solution. If the codebase is empty, you shoud call the `finish` action.
+implement the solution. If the codebase is empty, you should call the `finish` action.
 
 ## History
 Here is a recent history of actions you've taken in service of this plan,