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>

Development.md

@@ -98,5 +98,5 @@ Please refer to [this README](./tests/integration/README.md) for details.
 
 ### 9. Add or update dependency
 
-1. Add your dependency in `pyproject.toml` or use `peotry add xxx`
+1. Add your dependency in `pyproject.toml` or use `poetry add xxx`
 2. Update the poetry.lock file via `poetry lock --no-update`

agenthub/browsing_agent/prompt.py

@@ -161,7 +161,7 @@ class Truncater(Shrinkable):
 
     def __init__(self, visible, shrink_speed=0.3, start_truncate_iteration=10):
         super().__init__(visible=visible)
-        self.shrink_speed = shrink_speed  # the percentage shrinked in each iteration
+        self.shrink_speed = shrink_speed  # the percentage shrunk in each iteration
         self.start_truncate_iteration = (
             start_truncate_iteration  # the iteration to start truncating
         )

agenthub/micro/study_repo_for_task/prompt.md

@@ -20,7 +20,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
 {{ instructions.history_truncated }}

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,