update tips to include "human reviewed code" and "trivial changes"

README.md

@@ -241,7 +241,7 @@ Asking an AI to write software for you (*often* without human review). Per [Wiki
 The term was coined by [Andrej Karpathy](https://en.wikipedia.org/wiki/Andrej_Karpathy) (co-founder of [OpenAI](https://openai.com/)) in February 2025. A **Vibecoder** is a person who uses AI prompts to generate anything, typically code or images. It would therefore be appropriate to call Andrej Karpathy a vibecoder.
 
 > [!tip]
-> Humans reviewing vibecoded code does not disqualify said code from being considered vibecoded.
+> Humans reviewing vibecoded code does not disqualify said code from being considered vibecoded. Please check out our [why_not_llms.md](./why_not_llms.md) file for more info on why that is.
 
 Sometimes people will refer to vibecoding as "agentic engineering". We will not be using that term in this repo, but that still counts for this tag's usage.
 
@@ -260,6 +260,9 @@ Evidence may be, but is not limited to:
 
 A policy, written or otherwise implied by maintainers' actions/statements, that permits the use of AI/LLMs in a way where LLM output is added into the project. Opening the door for others to use gen AI counts as a "Permissive AI Policy".
 
+> [!tip]
+> Humans reviewing AI generated code does not disqualify said code from being considered tainted for the purposes of this list. "Small" or "trivial" changes to code bases by LLMs still count as tainted for the purposes of this list. Please check out our [why_not_llms.md](./why_not_llms.md) file for more info on why that is.
+
 Evidence may be, but is not limited to:
 
 - an explicit AI policy (e.g. `AI_POLICY.md`, `CONTRIBUTING.md`, developer docs) in the repo or something in the project's contributing guidelines or in their website's documentation that says that AI/LLMs are allowed