Apply suggestions from code review

Co-authored-by: Tobias Nießen <tniessen@tnie.de>
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
Co-authored-by: Efe <dogukankrskl@gmail.com>

Author: 5 people

CONTRIBUTING.md

@@ -52,7 +52,7 @@ dependencies, and tools contained in the `nodejs/node` repository.
 
 Node.js expects contributors to understand and take full responsibility for
 every change they propose. Pull requests consisting of AI-generated code the
-contributor has not personally understood, tested, and verified will be closed
+contributor has not personally understood, tested, and verified might be closed
 without review.
 
 See [details on our AI use policy and guidelines](./doc/contributing/ai-guidelines.md).

doc/contributing/ai-guidelines.md

@@ -12,7 +12,7 @@ never be "I'm not sure. The AI did it."
 
 Pull requests that consist of AI-generated code the contributor has not
 personally understood, tested, and verified waste collaborator time and
-will be closed without review.
+will be subject to closure without additional review.
 
 ## Using AI for code contributions
 
@@ -35,7 +35,7 @@ When using AI as a coding assistant:
   [commit message guidelines][].
 
 * **Test thoroughly.** AI-generated code must pass the full test suite and
-  any manually written tests relevant to the change. Existing Tests should not
+  any manually written tests relevant to the change. Existing tests should not
   be removed or modified without human verification. Do not rely on the LLM
   to assess correctness.
 
@@ -47,8 +47,8 @@ When using AI as a coding assistant:
 
 Node.js values concise, precise communication that respects collaborator time.
 
-* **Do not post AI-generated messages** in pull requests, issues, or the
-  project's communication channels.
+* **Do not post messages generated entirely by AI** in pull requests, issues, or the
+  project's communication channels.
 * **Verify accuracy** of any LLM-generated content before including it in a
   PR description or comment.
 * **Complete pull request templates fully** rather than replacing them with