diff --git a/aider/coders/base_coder.py b/aider/coders/base_coder.py
index 5dbe03cf9..ebdbd7f26 100755
--- a/aider/coders/base_coder.py
+++ b/aider/coders/base_coder.py
@@ -750,7 +750,7 @@ class Coder:
                 dict(role="user", content=repo_content),
                 dict(
                     role="assistant",
-                    content="Ok, I won't try and edit those files without asking first.",
+                    content="Ok, I won't try to edit those files without asking first.",
                 ),
             ]
         return repo_messages
diff --git a/aider/coders/base_prompts.py b/aider/coders/base_prompts.py
index 36f991f1e..848e61840 100644
--- a/aider/coders/base_prompts.py
+++ b/aider/coders/base_prompts.py
@@ -31,7 +31,7 @@ Any other messages in the chat may contain outdated versions of the files' conte
 
     files_no_full_files = "I am not sharing any files that you can edit yet."
 
-    files_no_full_files_with_repo_map = """Don't try and edit any existing code without asking me to add the files to the chat!
+    files_no_full_files_with_repo_map = """Don't try to edit any existing code without asking me to add the files to the chat!
 Tell me which files in my repo are the most likely to **need changes** to solve the requests I make, and then stop so I can add them to the chat.
 Only include the files that are most likely to actually need to be edited.
 Don't include files that might contain relevant context, just files that will need to be changed.
diff --git a/aider/coders/editblock_prompts.py b/aider/coders/editblock_prompts.py
index f6baaeb5f..a93b13a4b 100644
--- a/aider/coders/editblock_prompts.py
+++ b/aider/coders/editblock_prompts.py
@@ -18,7 +18,7 @@ Once you understand the request you MUST:
 
 1. Decide if you need to propose *SEARCH/REPLACE* edits to any files that haven't been added to the chat. You can create new files without asking!
 
-But if you need to propose edits to existing files not already added to the chat, you *MUST* tell the user their full path names and ask them to *add the files to the chat*.
+But if you need to propose edits to existing files not already added to the chat, you *MUST* tell the user their full path names and ask them to *add the files to the chat* BEFORE proposing any edits.
 End your reply and wait for their approval.
 You can keep asking if you then decide you need to edit more files.
 
diff --git a/aider/coders/patch_prompts.py b/aider/coders/patch_prompts.py
index 690a08884..2ad9ce0fa 100644
--- a/aider/coders/patch_prompts.py
+++ b/aider/coders/patch_prompts.py
@@ -20,8 +20,7 @@ Always reply to the user in {language}.
 Once you understand the request you MUST:
 
 1. Decide if you need to propose edits to any files that haven't been added to the chat. You can create new files without asking!
-
-   • If you need to propose edits to existing files not already added to the chat, you *MUST* tell the user their full path names and ask them to *add the files to the chat*.
+   • If you need to propose edits to existing files not already added to the chat, you *MUST* tell the user their full path names and ask them to *add the files to the chat* BEFORE proposing any edits.
    • End your reply and wait for their approval.
    • You can keep asking if you then decide you need to edit more files.