give a bit more explanation on permissive ai policy, change "can" to "may"

Hopefully this clears things up a bit more

README.md

@@ -204,7 +204,7 @@ The term was coined by [Andrej Karpathy](https://en.wikipedia.org/wiki/Andrej_Ka
 
 Sometimes people will refer to vibecoding as "agenic engineering". We will not be using that term in this repo, but that still counts for this tag's usage.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - blog post stating the project was vibecoded
 - link to readme stating that the project was vibecoded.
@@ -217,17 +217,17 @@ Evidence can be, but is not limited to:
 
 ![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)
 
-A policy that permits the use of AI/LLMs in any capacity. Opening the door for people to vibecode counts as a permissive AI policy.
+A policy, written or otherwise implied by maintainers' actions/statements, that permits the use of AI/LLMs in any capacity. Opening the door for people to vibecode counts as a "Permissive AI Policy".
 
-Evidence can be, but is not limited to:
+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
 - an LLM friendly `AGENTS.md`, `CLAUDE.md`, or other such LLM instruction files or folders.
 - core maintainers' blog or social media post about using AI/LLMs
-- LLM code being merged into the default branch of a code repository. (Must be merged to count; Open PRs do not count)
+- LLM code being merged into the default branch of a project's code repository. (Must be merged to count; Open PRs do not count)
 
 > [!Important]
-> If a core maintainer has noted that the code is entirely vibecoded, please use the ![Vibecoded](./badges/vibecoded.svg) instead. That tag is specifically meant for extreme cases only.
+> If a core maintainer has noted that the code is entirely vibecoded, please use the ![Vibecoded](./badges/vibecoded.svg) instead. The vibecoded tag is specifically meant for *extreme* cases only.
 
 ## AI Functionality
 
@@ -235,7 +235,7 @@ Evidence can be, but is not limited to:
 
 This would include the ability to enable or disable an AI feature, such as an AI assistant or AI summary feature. This would also cover the case when a project depends on an AI program or library, such as an LLM SDK.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - a link to the docs explaining the AI Functionality
 - a blog post advertising the AI Functionality
@@ -247,7 +247,7 @@ Evidence can be, but is not limited to:
 
 An AI agent/bot is used to review pull requests, which makes slop acceptance more probable and maintainability more difficult, especially when human reviews are scarce.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - a link to an AI code review requested by a maintainer.
 - an AI code review CI workflow.
@@ -262,7 +262,7 @@ Evidence can be, but is not limited to:
 
 AI "Art" is being used in a project. This is typically for banners, avatars, promotional material, and/or blog posts. This means they're using tools that steal art from visual artists.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - link to the place where the AI "art" is used
 
@@ -272,7 +272,7 @@ Evidence can be, but is not limited to:
 
 The project is sponsored directly by an AI company. An AI company is any company that advertises itself as pro-AI or develops an AI product itself. The obvious ones are Anthropic and OpenAI, however, all the big tech companies (e.g. Apple, Google, Microsoft, and Amazon) also count because they all have AI services and direct products as major offerings.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - Blog post disclosing AI funding
 - link to website that lists AI companies in sponsors list
@@ -284,7 +284,7 @@ Evidence can be, but is not limited to:
 
 The use of an AI company as a third party service for processing user data.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - Blog post talking about using AI for processing user data
 - Privacy policy listing an AI company as a third party service
@@ -295,7 +295,7 @@ Evidence can be, but is not limited to:
 
 The use of an AI bot/agent for responding to Issues, Discussions, Forums etc related to a project's issue/bug tracking.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - Link to AI in an Issue, Bug report, Discussion, etc - must be related to the project's bug/issue tracking (e.g. dosu)
 
@@ -310,7 +310,7 @@ The reason we still find this worthy of a tag is because it:
 - means that the LLM, often provided by a company with very little respect for copyright, will then save a copy of that open source repo for use in it's future outputs.
 - still encourages people to use LLMs and carves out a special situation in which they're still OK, but as this repo is against AI/LLMs for more than just "poor code quality" reasons, we still believe this is not a good course of action as it still promotes the use of inherently unethical tooling.
 
-Evidence can be, but is not limited to:
+Evidence may be, but is not limited to:
 
 - An AI or Contribution policy that carves out a space for "using LLMs to understand the code" or "finding bugs"
 - Core maintainer using or accepting the use of AI for finding bugs or security issues